Privacy notice
Last updated November 15, 2026
On This Page
AI-assisted text. Not reviewed by a lawyer.
Version 2026-11-15-r4. Effective date: the Last updated date shown on this page. CoFabri LLC, legal@cofabri.com. Maven X is a brand used by CoFabri LLC for MavenOS. This notice covers MavenOS, its installed app, client portal and API. It does not describe the separate Maven X agency website. The central CoFabri account service must also provide an accurate notice for its own processing.
MavenOS is provided by CoFabri LLC using the Maven X brand.
1. Our roles
For records a business puts into its workspace, that business determines purposes and instructions and normally acts as controller; it may instead be a processor for its clients. We process that information on its behalf under the DPA. For our own account administration, billing, fraud prevention, and minimized operational security records, we determine the necessary purposes. A workspace audit record containing customer content remains subject to the appropriate customer-data protections; calling it a security record does not remove those protections.
2. Information and sources
We receive information from account holders and workspace users, the business that invites you, its contacts and portal users, services that it authorizes to connect, and devices and infrastructure used to operate MavenOS. Account information includes name, email, sign-in method, optional photo, security settings and session records. MavenOS does not itself hold the central account password. Billing includes plan, payment status, billing contact and processor transaction references; card entry occurs through the payment processor.
Workspace content may include customer and lead details; projects, tasks, time entries, notes, files and imported meeting summaries; staff and contractor contact and employment details, compensation, performance reviews, emergency contacts and leave administration; invoices, bank transactions, receipts and accounting data; agreements, signatures and signed records; support emails and attachments; knowledge articles, media, messages, comments and approvals. These records can be sensitive. Government identifiers and W-9 tax forms are prohibited unless a designated restricted tax-file workflow has expressly been enabled. If enabled, the uploaded file contains and stores the identifier even if there is no separate tax-number field. Clinical and other prohibited health records must not be uploaded.
Connected services provide the records and permissions authorized by the connecting person and may provide access or refresh tokens, which we protect with encryption and restricted access. Device and operational information includes IP address, browser and operating system, sign-in time, security events and usage counts. Optional AI receives the relevant prompt and permitted records needed for the requested feature. We do not intentionally collect precise location, biometric identification templates or advertising profiles for MavenOS.
3. Purposes
We use information to create and authenticate accounts; host, organize, retrieve and export workspace content; deliver messages and authorized integrations; provide optional AI features; administer subscriptions, taxes and payment issues; support customers; investigate fraud and security problems; enforce lawful terms; comply with legal duties and establish or defend claims. We use deidentified or aggregate operational statistics to improve performance and capacity with safeguards against reidentification. We do not sell personal information, share it for cross-context behavioral advertising, use Customer Data for targeted advertising, or train general-purpose AI models on it. The actual vendor contracts and configuration must support those statements before publication.
4. Access and disclosures
Customer administrators assign roles and permissions. Workplace communications are business records. Owners and authorized administrators may review or export communications and records within their granted responsibilities, including contractor work messages; they are not a private consumer messaging service. Sensitive HR and pay content is subject to narrower permissions. The role screen and relevant feature notices describe the actual access available. A user’s own-record access path may differ from an administrator’s access. Message bodies and designated HR, pay, Legal and contract content are excluded from cross-workspace Assistant retrieval as configured, but users must not paste excluded material into AI prompts or drafts.
Ordinary support access uses owner-approved, scoped, time-limited grants. Restricted personnel may also access information when necessary for infrastructure administration, service recovery, incident response or legal obligations under the safeguards in the Terms and DPA. Account and billing administration is available to limited authorized staff. We share necessary data with hosting, storage, email, signing, push, AI and other service providers identified in the vendor register, subject to appropriate contracts. Providers may have their own subprocessors. Some payment and customer-connected providers also act independently for their own stated purposes; the register distinguishes those activities.
AI may send prompts, permitted workspace extracts, content instructions or meeting summaries through a gateway to model providers. We do not intentionally save Assistant question-and-answer conversation history. Saved content drafts, extracted tasks and meetings remain workspace records; optional feedback may include the text a person enters. Operational or security logs and gateway or model-provider retention may also apply. The feature notice and vendor register must identify the verified provider treatment; no zero-retention assurance is made. We may disclose information in response to lawful process, to protect rights and security, or in a business transfer with appropriate confidentiality and continuing data protections. We notify customers of legal demands where lawful and reasonably practicable.
5. Retention and deletion
Active workspace content is retained while the workspace operates, subject to customer deletion settings and lawful holds. Customers keep, and are responsible for, their own business records and should export what they need before deleting a workspace. After a workspace is deleted we keep only our own records: our billing and payment record with the customer, proof of acceptance of the terms, and the deletion record. Employment or contractor departure does not automatically erase the business’s records. Customers set their own lawful employment and contractor retention requirements; there is no universal seven-year rule for all records. Our default workspace lifecycle is the following, subject to applicable legal deadlines and verified implementation.
Ordinary subscription or trial end: 30 days read-only, then hidden; owner export remains available through supported or assisted delivery. We intend to retain data for at least 90 days from access ending, with at least 14 days’ final notice, and aim to complete active-system deletion within about 120 days. Owner-requested deletion: normally begins after 14 days to withdraw the request, and we aim to complete it in active systems within the next 30 days. Account deletion is separate because an account may belong to several workspaces. Necessary legal duties may override a routine schedule but do not justify unrelated use.
Our database provider keeps daily database backups, currently for about seven days on our plan, so deleted records may remain in a backup until it is replaced. Backups are isolated from ordinary use; if restored for recovery, the applicable deletions must be reapplied. Under the current product design, uploaded stored files are not included in database backups. Do not rely on MavenOS as the only copy of important files. Export downloads expire after seven days. We aim to delete import staging files after a successful import or about 30 days of inactivity, to keep optional AI feedback for no more than about 90 days, and to keep AI usage counts for no more than about 13 months. Meeting summaries follow the owner’s configured limit or workspace lifecycle, whichever requires earlier routine deletion.
A workspace’s audit trail is kept while the workspace exists. When a workspace is deleted we aim to strip its audit lines of before-and-after content, names and message bodies within about a day, leaving only ids, action codes and times; those, our staff-access audit log and finished support-access grants are deleted after 24 months, unless a documented lawful need requires longer. Our own records (our billing and payment record with the customer, proof of acceptance of the terms, and the deletion record) may be retained for seven years; proof of acceptance is kept minimized: the accepting person’s name and email, the text version and its hash, and the UTC time after closure or contract end, or a different period required by law, using only records needed for that purpose and restricted access. These categories do not authorize keeping all workspace contracts or content for seven years. A minimal deletion receipt may retain a workspace identifier, request date, completion date and necessary requestor evidence; minimize names and other identifiers. Documented holds are reviewed and deleted when their purpose ends.
Besides our billing and payment record, our record that you accepted the terms and our record that a workspace was deleted, we keep four kinds of our own operational records, which hold ids, action codes, counts and limited details, not the content you store: (1) the minimized audit lines of a deleted workspace (who did what and when, as ids and action codes only, with names and values removed) and (2) our platform audit log of what our staff did, each for at most 24 months; (3) sign-up abuse-prevention events (the account id, the kind of action, the workspace id and the time), which we aim to remove after about two days, with daily counts of refused attempts that hold no names or emails; and (4) the audit log of our account and API service, which records the action, the application, the record it concerns and limited details such as a staff email address or a signer’s name, is kept while the service runs, and is readable only by authorized staff.
6. Privacy requests
Depending on applicable law and your relationship to the information, you may have rights to access or obtain a portable copy, correct, delete, limit sensitive processing, withdraw consent, or opt out of sale, sharing, targeted advertising or certain significant profiling. We do not currently engage in those sale, advertising or significant-decision profiling activities for MavenOS. Rights and exemptions differ, including for employment records. We do not discriminate for exercising applicable rights.
Contact legal@cofabri.com. Workspace owners can also export their workspace data and request workspace deletion in Settings. We may verify identity and an authorized agent’s permission using information proportionate to the request; do not email a Social Security number or ID document unless we arrange a secure necessary process. We answer within the period applicable law requires and explain any permitted extension or denial. If we deny a request for which applicable law gives an appeal, reply with “Privacy appeal”; we provide the legally required response and regulator-contact information. You may also contact your state attorney general or relevant privacy regulator. Requests about a business’s workspace normally go to that business; we assist it as its processor and handle any independent obligations ourselves. We do not promise that every person has every listed right in every state. Additional required intake methods and state notices must be supplied where applicable.
7. Cookies and browser storage
We use session, portal, sign-in, integration-state and support-grant cookies, a workspace-choice cookie lasting up to one year, and view-preference cookies. Local storage remembers interface preferences. Browser controls can remove storage but may affect functionality. MavenOS does not currently load advertising or third-party analytics tracking scripts. Before adding it, we will update this notice and implement required choices. Essential storage still requires appropriate notice; foreign requirements need separate review. Connected services and hosted payment pages use storage under their own notices.
8. Children
Accounts and portals are for adults 18 or older in business use. We do not knowingly offer child-directed services or collect directly from child users under 13. Customers must not invite children or operate child-directed services here. They remain responsible for lawful, minimized incidental records about dependents or other children. Report suspected child-user information to legal@cofabri.com for investigation and appropriate action.
9. Security and incidents
We use reasonable technical and organizational safeguards appropriate to the data and risk; no system is perfectly secure. We coordinate notice of personal data breaches with affected customers under the DPA and applicable law and provide legally required direct notices where our own duties apply.
10. Processing locations
Launch customers are US businesses. Primary workspace database and file storage are hosted in the United States (Supabase, US East, Northern Virginia); hosting, logs, email, AI, support and other providers may process data in the countries identified in the verified vendor register. US sales do not mean all processing stays in the US or all data subjects are American. We do not authorize restricted international transfers without the required arrangements.
11. Notice changes
The date and version identify this notice. We give appropriate notice of material changes, including email to workspace owners, and obtain consent where law requires it before a new incompatible use. A notice update does not retroactively authorize a new use or reduce DPA protection.
12. Contact
CoFabri LLC. legal@cofabri.com.

