Your writing is personal. This policy explains, in plain English, what Arbento collects, why we use it, and which service providers process it.
Most important: we do not sell your personal data or your writing.
Arbento's story-intelligence features use cloud AI. When you request continuity and Codex checks, structure or beat analysis, story-health and pacing analysis, editorial feedback, voice analysis, or an inline suggestion or rewrite, Arbento securely sends the text and context needed for that request to our backend on Google Firebase. The backend sends it to Anthropic through the Claude API and returns the result to the app. Under Anthropic's current Commercial Terms, the contracting entity for EEA customers is Anthropic Ireland, Limited. These features cannot work without this processing.
Depending on the feature, the request may contain a selected passage, the current scene, excerpts from nearby scenes, project notes, Codex entries, a writing sample, or text and structural information from multiple scenes. Arbento does not send your manuscript to Anthropic merely because you type or edit it.
Under Anthropic's Commercial Terms, Anthropic may not train models on customer inputs or outputs. Anthropic's commercial-product privacy guidance likewise states that API inputs and outputs are not used for model training by default unless the customer explicitly opts in. We have not opted in. Under Anthropic's standard API retention policy, inputs and outputs are normally deleted from its systems within 30 days. Anthropic may keep them longer where required by law or to enforce its usage rules. We do not sell your writing.
Google and Anthropic may process data outside the European Economic Area, including in the United States. For restricted transfers, we rely on applicable safeguards including the European Commission's Standard Contractual Clauses (SCCs) incorporated into the providers' data-processing terms, including Anthropic's Data Processing Addendum.
Your projects, scenes, notes, Codex entries, and related story data. We store this content to provide the app and device sync. We send the relevant content to our AI subprocessors when you use an AI feature, as described above. AI results such as analyses or voice profiles may be saved with your project.
Your account identifier, sign-in details, account settings, subscription status, and purchase information needed to authenticate you and provide paid features. Apple handles App Store payments; we do not receive your full payment-card details.
Feature interactions, screen views, device and app information, attribution data, and technical errors used to understand reliability, measure product performance, and improve Arbento. We do not intentionally include manuscript text in analytics events.
Information you send us when you ask a question or report a problem.
Our legal bases under the GDPR depend on the purpose:
We may update this list when our providers change. Material changes will be reflected on this page.
We keep account and project data while your account or project remains active and as needed to provide the service. You can delete projects in the app or ask us to delete your account data. Some records may remain for a limited period in backups, security logs, or where law requires us to keep them. Provider-specific AI retention is described in “AI Features and Cloud Processing.”
Our website may use essential cookies, preference storage, and analytics technologies. The app uses Google Firebase Analytics and Amplitude to measure feature use and reliability. Where the law requires consent, optional analytics are based on your consent. Browser cookie controls do not control analytics inside the app.
Encryption in transit using HTTPS/TLS
Encryption and security measures for data stored by our cloud providers
Authentication, access controls, App Check, monitoring, and security updates
No system can guarantee absolute security, but we use technical and organizational measures appropriate to the risk.
Subject to the GDPR's conditions and exceptions, you may:
For privacy questions or to exercise your rights, contact:
Last updated: June 23, 2026
Your writing is personal. This policy explains in plain terms what data Arbento processes, why we use it, and which service providers are involved.
Most important: we do not sell your personal data or your writing.
Arbento's story-intelligence features use cloud AI. When you request continuity and Codex checks, structure or beat analysis, story-health and pacing analysis, editorial feedback, voice analysis, or an inline suggestion or rewrite, Arbento securely sends the text and context data needed for that request to our backend at Google Firebase. The backend forwards it to Anthropic via the Claude API and returns the result to the app. Under Anthropic's current commercial terms of use, the contracting partner for customers in the EEA is Anthropic Ireland, Limited. Without this processing, these features do not work.
Depending on the feature, the request may contain a selected passage, the current scene, excerpts from neighboring scenes, project notes, Codex entries, a writing sample, or text and structural data from multiple scenes. Arbento does not send your manuscript to Anthropic merely because you are writing in it or editing it.
Under Anthropic's Commercial Terms, Anthropic may not train models on customer inputs or outputs. Anthropic's commercial-product privacy guidance likewise confirms that API inputs and outputs are not used for model training by default unless the customer explicitly opts in. We have not opted in. Under Anthropic's standard API retention policy, inputs and outputs are normally deleted from its systems within 30 days. Anthropic may retain them longer where required by law or to enforce its usage rules. We do not sell your writing.
Google and Anthropic may process data outside the European Economic Area, including in the United States. For restricted transfers, we rely on appropriate safeguards, in particular the European Commission's Standard Contractual Clauses (SCCs) incorporated into the providers' data-processing terms, including Anthropic's Data Processing Addendum.
Your projects, scenes, notes, Codex entries, and related story data. We store this content to provide the app and synchronization. When you use an AI feature, we send the relevant content as described above. AI results such as analyses or voice profiles may be stored with your project.
Account identifier, sign-in details, settings, subscription status, and purchase information needed for sign-in and paid features. App Store payments are processed by Apple; we do not receive full payment-card details.
Feature interactions, screen views, device and app information, attribution data, and technical errors. We use these for reliability, product measurement, and improvements. We do not intentionally include manuscript text in analytics events.
Information you send us when you have questions or report problems.
We update this list when our providers change. Material changes will be published on this page.
We keep account and project data for as long as your account or project is active and as needed for the service. You can delete projects in the app or request deletion of your account data. Some data may remain for a limited time in backups, security logs, or due to legal obligations. Anthropic's retention period is described above.
Our website may use necessary cookies, preference storage, and analytics technologies. The app uses Google Firebase Analytics and Amplitude to measure feature use and reliability. Where consent is legally required, optional analytics rely on it. Browser cookie settings do not control analytics within the app.
Encryption in transit using HTTPS/TLS
Encryption and security measures for data stored with cloud providers
Authentication, access controls, App Check, monitoring, and security updates
No system can guarantee absolute security. We employ technical and organizational measures appropriate to the risk.
Subject to the conditions and exceptions of the GDPR, you can:
For privacy questions or to exercise your rights:
Last updated: June 23, 2026