Data processing agreement
Last updated November 15, 2026
On This Page
AI-assisted text. Not reviewed by a lawyer.
Version 2026-11-15-r4. This DPA forms part of the MavenOS Terms between CoFabri LLC and the Customer identified in the acceptance record. It applies to personal data processed on Customer’s behalf and prevails over conflicting Service terms on that subject. Authorized acceptance of the Terms and this DPA may occur electronically with a retained record of the exact versions and customer identity.
1. Definitions
Customer Personal Data means personal information contained in Customer Data processed on Customer’s behalf. Applicable Data Protection Law means privacy, security and data protection laws applicable to that processing. A Subprocessor processes Customer Personal Data for CoFabri in delivering the Service. A Personal Data Breach is a security breach resulting in accidental or unlawful destruction, loss, alteration, unauthorized disclosure of or access to Customer Personal Data. Unsuccessful attempts without compromise are not, by themselves, a Personal Data Breach.
2. Roles and responsibilities
Customer is controller, or processor acting under a controller’s lawful authority; CoFabri is processor or subprocessor respectively. Customer is responsible for lawful collection, required notices, permissions and instructions. CoFabri remains responsible for its own compliance and this DPA. Independent-controller account, billing and minimized operational-security processing is described in the Privacy Notice, but unnecessary workspace content cannot be reclassified to escape this DPA. If Customer acts for a controller, it must have authority for this appointment and convey necessary instructions and notices.
3. Processing schedule
Subject matter and frequency: continuous and on-demand operation of the MavenOS workspace and the optional functions Customer enables. Duration: the subscription and the limited return, deletion, backup and lawful retention periods stated here and in the Terms.
Data subjects: Customer’s staff, contractors, users, customers, contacts, leads, portal users and other individuals lawfully included in permitted records. Data categories: identity and contact information; business correspondence; project, task and time records; employment administration and compensation; invoices, payment references, permitted bank and accounting data; contract and signature records; support communications; documents, media, comments, approvals and imported meeting notes. Special or sensitive data may include compensation and financial information; designated tax files only if expressly supported. Prohibited health, biometric, card-authentication and general government-identifier uploads are not authorized. Ordinary administration must not include prohibited medical records.
Specified purposes: host and retrieve business records; apply user and workspace permissions; transmit customer-directed notifications; synchronize authorized integrations; generate customer-requested AI answers, drafts or meeting action items using approved providers; generate signatures at Customer’s direction; produce exports and execute deletion; provide support; and detect, investigate and mitigate service security incidents. No sale, advertising use or general-purpose model training is authorized by this schedule.
4. Instructions and US service provider restrictions
The agreement, configured settings, permitted user actions and documented support requests are Customer’s instructions. We process only on those instructions unless law requires otherwise, in which case we notify Customer before processing unless prohibited. We notify Customer if an instruction appears unlawful and may suspend that instruction pending resolution.
Where applicable California law applies, CoFabri acts as service provider or contractor for the limited specified purposes in section 3, not as a buyer of personal information. We will not sell or share Customer Personal Data; retain, use or disclose it outside those purposes or the direct business relationship; or combine it with data from other sources except as law permits. We will provide the legally required level of privacy protection, notify Customer if we can no longer meet our obligations, and permit reasonable steps to verify compliance and stop and remediate unauthorized use. We certify our understanding of and compliance with these contractual restrictions. These terms also supplement other applicable US processor-contract duties without asserting that every state privacy statute applies to every customer.
5. Personnel and access
Personnel authorized to process Customer Personal Data owe confidentiality duties and receive access limited to their responsibilities. Ordinary support access uses the owner-grant process. Necessary infrastructure administration, service restoration, security and legal access may occur under the restricted exceptional-access safeguards in the Terms. We do not use that exception for routine unrestricted access. Appropriate access records are retained under the agreed finite schedule.
6. Minimum security measures
CoFabri will maintain safeguards appropriate to the nature and risk of the processing. The minimum baseline for this version is: authenticated account access; workspace and role-based authorization; administrative and support access limited by role; encrypted transport; encryption of retained integration tokens; private storage and access restrictions for sensitive HR files; logging of relevant administrative and security events with sensitive payload minimization; the deletion processes described in the Terms and Privacy Notice; and provider-managed daily database backups, currently kept for about seven days on our plan. Uploaded-file backup is not included unless expressly agreed.
The Security Page explains the implementation but does not silently increase this baseline whenever edited. We may evolve controls without materially reducing overall protection. We will provide reasonable information about material security changes. Customer controls permissions, content, connection authority and its own independent records. Those responsibilities do not excuse our breach.
7. Subprocessors and customer connections
Customer generally authorizes the verified processors and downstream processing chain disclosed in our vendor register, which we aim to keep current and provide on request. Before use, we bind Subprocessors to written obligations appropriate to their processing and no less protective as required by Applicable Data Protection Law, including confidentiality and security. We remain responsible for their performance of our delegated processing obligations, subject to the agreement’s lawful allocation of liability.
We aim to email owners and update the register at least 30 days before a new Subprocessor begins processing. Customer may object within that period on reasonable documented data-protection grounds. We work in good faith to provide an alternative or resolve the concern. If unresolved, Customer may terminate the affected service before that provider’s processing begins and receive unused affected prepaid fees; if the remainder cannot reasonably operate, the remedy extends to the affected subscription. Necessary urgent replacements for security or legal reasons receive as much prior notice as reasonably possible, prompt subsequent notice, and the same objection and termination remedy. Customer may request suspension of the affected optional function while the objection is addressed.
An outside provider can be Customer’s direct service provider, our Subprocessor for a particular activity, an independent controller, or more than one of those for different activities. Classification follows the actual agreement and data flow, not whose button enabled it. Our vendor register aims to record these distinctions. Customer authorizes the requested data exchange and must meet its direct-provider duties. Our use of shared platform keys does not eliminate our processing obligations.
8. Assistance and individual rights
Taking account of the processing and information available, we assist Customer with rights requests, security and breach duties, assessments and regulator consultations required by law. We forward requests received for Customer’s workspace to its designated contact promptly and do not act contrary to Customer’s lawful instructions unless independently required by law. We identify recipients to which relevant correction or deletion instructions must be passed and cooperate in implementing them.
Ordinary self-service and reasonable compliance information are included. Extraordinary custom assistance may incur a reasonable fee agreed in advance, except where caused by our breach or where law requires assistance without such charge. Fees, resource limits and self-service gaps must not obstruct applicable rights or deadlines. We provide secure assisted delivery of material Customer Personal Data omitted from routine export where needed to meet this agreement or law.
9. Personal Data Breach
We notify Customer’s owner and designated security contact without undue delay and no later than 48 hours after becoming aware of a Personal Data Breach affecting its data, or sooner when Applicable Data Protection Law requires. We do not wait for a completed investigation. As information becomes available, notice describes the nature and relevant dates, affected categories and approximate numbers of individuals and records, likely consequences, containment and remediation, actions recommended for Customer, and a contact for updates. We preserve relevant evidence, take reasonable mitigation and remediation measures, cooperate with Customer and provide further facts without undue delay. Notification is not an admission of liability.
Customer normally controls notices about its processing; we do not notify its individuals in its name without authorization unless law requires it. Each party remains responsible for its own mandatory notices. A lawful authority may require a permitted notice delay, which we document and limit as law allows. Do not interpret the 48-hour contractual ceiling as permission to delay a notice otherwise required sooner.
10. International processing
US-only customer eligibility is not an exemption from transfer law. Customer must identify processing requiring an EEA, UK, Swiss or other restricted-transfer mechanism before enabling it. CoFabri will not knowingly carry out a restricted transfer without an appropriate lawful arrangement. This draft does not attach SCCs or approve a particular transfer mechanism. Before such processing begins, the parties must complete the applicable role and transfer analysis, executed clauses or other valid mechanism, country and subprocessor schedules, and required assessments and safeguards. If necessary arrangements cannot be established, the affected processing must remain disabled; contractual prohibitions do not cure an actual unlawful transfer.
11. Return deletion and residual records
Customer may export supported data while the workspace exists and during the post-term retention window, using reasonable secure assistance for material omissions. Customer may choose return and deletion through the designated owner workflow or a verified request; CoFabri assists where law requires another method. Routine expired workspaces follow the Terms’ day 104 earliest deletion and day 120 latest active-system completion, subject to lawful holds. Owner-requested deletion follows the 14-day withdrawal window and then completion within 30 days, unless an applicable legal deadline requires faster action. Those schedules must be implemented before this draft is offered.
Backups are isolated from ordinary processing and, on our current provider plan, are replaced on a rolling basis after about seven days. Restores reapply outstanding deletions. The Privacy Notice’s finite minimized security-metadata and retention of our own records applies; unnecessary content and identifiers must not be retained as audit snapshots after deletion. Legal holds identify the purpose, scope, access restriction and review date and end when no longer necessary. Residual data stays confidential and protected and is not used for another business purpose. Upon reasonable request, we confirm completion and describe lawful residual categories and backup timing; we do not certify that all possible copies everywhere disappeared when that is untrue.
12. Verification and audits
We provide information reasonably needed to demonstrate compliance, including relevant control descriptions, vendor information, available independent reports and written answers. Customer may take reasonable verification, testing and remediation steps required by applicable law. Ordinarily documentary review comes first, followed if needed by a qualified independent audit no more than annually, on 30 days’ notice, during business hours, under confidentiality and without exposing other customers’ data or security secrets unnecessarily. Additional or faster review is available when legally required, after a relevant material incident, or on reasonable evidence of noncompliance. Regulators retain their lawful rights. An alternate independent assessment may be used where law permits and it supplies the required assurance.
Customer bears its audit costs unless the audit establishes our material noncompliance, in which case we bear reasonable costs attributable to verifying and correcting that noncompliance. No production penetration testing is authorized without a written scope; that restriction does not defeat mandatory inspection rights. Parties coordinate safeguards and practical scope in good faith.
13. Liability
The Terms’ Base Cap and Enhanced Cap apply as expressly stated there, across the Terms and this DPA together, with no stacking or double recovery. They do not limit a regulator’s authority or mandatory rights of individuals. This DPA creates no independent unlimited indemnity.
14. Order amendments and contact
The DPA prevails for conflicts about Customer Personal Data. Material changes follow the Terms’ prospective notice and assent process and do not reduce existing data protection without lawful agreement. The parties cooperate on amendments required by law and suspend an affected processing activity if it cannot lawfully continue. Florida law and the agreed Broward County or Southern District of Florida forum apply subject to mandatory law. Notices legal@cofabri.com; Customer contact as recorded in its workspace, with a separate security contact if supplied.

