Privacy policy

2. The short version

• Revise processes text only when you deliberately use a writing feature or choose to synchronise or save that text.
• The iPhone keyboard is designed to transmit only text you select and submit for a Revise action, not every keystroke you type.
• Cloud AI actions require a clear Revise consent. Personal Voice is a separate opt-in, and each kind of learning it does can be turned off on its own.
• OpenAI and Anthropic process submitted text for generation, safety, analysis, or embeddings. Their commercial APIs do not use API content to train general models by default.
• Revise does not put prompts, selected text, document contents, or generated prose into general product analytics.
• You can withdraw optional consents and can delete Personal Voice data, documents, or your account using the available controls.
• Revise does not sell personal data and does not use text submitted for rewriting to target third-party advertising.

3. Account, authentication, and subscription data

When you create or use an account, we may process your name, email address, account identifier, verification status, subscription status, usage allowance, settings, sign-in records, and support communications. If you use Apple or Google sign-in, we receive the identifier and profile information that provider makes available with your permission.

Authentication credentials are stored using platform security controls such as Keychain on iPhone and protected browser storage in Chrome. Revise stores access and refresh-token records needed to maintain sessions, secure accounts, and revoke access.

Apple or Stripe processes subscription payments. Revise receives transaction identifiers, product, subscription status, renewal or expiry information, and limited billing metadata needed to provide paid access, prevent duplicate ownership, and support account management. Revise does not receive your complete payment-card number.

4. Writing and AI processing

Draft, Rewrite, Adjust, and related actions

When you ask Revise to generate, rewrite, adjust, proofread, or analyse text, we process the text and instructions you submit, relevant feature settings, the generated response, and technical metadata needed to deliver and secure the request. Depending on the feature and plan, Revise sends the request to OpenAI or Anthropic.

We may send text to automated safety systems before or during generation. We may also create embeddings, which are numerical representations of text, when an opted-in Personal Voice feature needs them. Revise does not use submitted writing to train a general-purpose Revise model.

Chrome extension

The Chrome extension processes text that you deliberately select, enter, or submit to a Revise action. Extension permissions allow Revise to interact with supported text fields and pages. Revise is not designed to collect a general history of pages you visit, clipboard contents you do not submit, or unrelated page content.

iPhone app

The iPhone app processes documents, selected passages, instructions, settings, and generated responses when you use its writing features. Local drafts and preferences may remain on the device. If account sync is enabled, the document data described below is also stored by Revise.

iPhone keyboard

The Revise keyboard remains available for ordinary typing without Full Access. When you enable Full Access, sign in, grant the required Revise consent, select text, and deliberately request a cloud rewrite, the keyboard sends that selected text and your chosen instructions to Revise. It is designed not to transmit every keystroke, unrelated surrounding content, secure-field entries, or text that you do not submit to a Revise action.

Apple controls the Full Access setting. You can withdraw that access or remove the keyboard in iOS Settings. Withdrawing Full Access stops network rewriting from the keyboard but does not delete account or Personal Voice data already stored by Revise.

5. Documents and account sync

When document sync is enabled, Revise stores the document identifier, title, body, version and modification information, and deletion state needed to keep your Revise account consistent across supported devices and platforms. Deleted-document markers may remain for as long as needed to make deletion converge across signed-in devices.

Synced documents remain until you delete them or delete your account, subject to limited backup and legal retention. Signing out removes access from that device but does not delete synced documents from your account.

6. Personal Voice

Personal Voice is optional and inactive until you opt in. It is designed to personalise Revise to writing choices you actually make. Turning it on is a single choice covering the uses available to your account and shown before you consent. Available uses vary by plan; where Revise provides individual learning controls, you can narrow them afterwards.

Your writing profile

You can ask Revise to build your writing profile directly from samples you submit. Revise processes those samples to derive the profile and does not store the samples themselves; it retains only the resulting profile and a content-free record of how many samples were used. The profile is visible to you, can be updated from new samples, and can be deleted.

Saved Examples

Saved Examples is available on eligible plans. While accepted-rewrite learning is on, Revise may store the source text and the rewrite you chose to keep, an embedding, categorical information about the writing action, and the date of the example. Revise verifies that the example came from a completed generation and an action you applied before storing it.

Learning from final edits

While final-edit learning is on, Revise may store the source, the generated or applied rewrite, the final text you kept after editing, edit-distance and timing signals, and related categorical metadata. Revise can also learn from eligible text you author within a supported Revise rewriting flow. Server checks are designed to prevent Revise-generated text from being misclassified as your independent writing.

Derived voice data

Revise uses eligible examples and evidence to derive a writing profile, preferences, learned adjustments, and confidence or quality measurements. These derived records may influence future requests only while the relevant Personal Voice permissions and feature controls allow it.

Your controls

You can turn Personal Voice off entirely, pause application of your voice, turn off an individual kind of learning, delete your writing profile, delete learning evidence, delete Saved Examples where the product provides that control, reset learned voice data, or delete your account. Turning something off stops the relevant future collection and use but does not by itself delete data already retained. Use the separate deletion controls when you want existing data removed.

7. Analytics, diagnostics, and service security

Revise records content-free product events such as the feature or surface used, action outcome, duration, plan, model route, quota use, and an account or random per-install identifier where applicable. These records help us operate the service, understand whether features work, prevent abuse, and improve product decisions. They do not contain prompts, selected text, generated prose, document bodies, clipboard contents, page URLs, or page domains.

Our servers may process IP address, request time, device or browser information, authentication activity, rate-limit information, and error details for security, reliability, fraud prevention, and troubleshooting. Diagnostic logs may be linked to an account when needed to investigate an account-specific problem.

Our public websites use Google Analytics and Microsoft Clarity to understand visits and interactions. These services may process cookie or similar identifiers, device and browser data, approximate location derived from IP address, pages viewed, clicks, scrolling, and interaction recordings. These services operate on public web pages outside the authenticated writing-request pipeline, but they may observe interactions with public demonstrations. Do not enter sensitive information into a public demonstration field.

8. Why we use personal data

Depending on the data and context, Revise uses personal data to:

• provide requested writing, account, sync, keyboard, and subscription features under our contract with you;
• process cloud AI actions and Personal Voice where you have given the required consent;
• secure accounts, enforce limits, prevent fraud and abuse, diagnose failures, and maintain the Services based on our legitimate interests and legal duties;
• send transactional messages, respond to support, and administer subscriptions under our contract with you;
• measure and improve the Services based on consent where required and otherwise our legitimate interests, balanced against your rights; and
• comply with law, resolve disputes, and enforce our agreements.

Where processing relies on consent, you may withdraw it at any time. Withdrawal does not make earlier lawful processing unlawful. Features that require the withdrawn permission will stop, while unrelated local or account functions can remain available.

9. Who receives data

Revise shares data only as needed for the purposes in this policy. Recipients may include:

• OpenAI and Anthropic for AI generation, moderation, analysis, and embeddings;
• Apple and Google for application distribution, authentication, platform functions, and subscription verification;
• Stripe for web subscription billing and customer billing management;
• Cloudflare and hosting, database, storage, networking, and security providers used to operate Revise;
• Resend or another configured email provider for transactional email;
• Google Analytics and Microsoft Clarity for public-site analytics;
• professional advisers, auditors, insurers, and authorities where reasonably necessary or legally required; and
• a buyer or successor if Revise is involved in a merger, financing, acquisition, restructuring, or sale, subject to appropriate confidentiality and notice.

Service providers may process data only for contracted purposes and must apply appropriate protection. Some providers also act as independent controllers for their own account, payment, fraud, or legal obligations.

10. AI provider practices

Revise uses commercial OpenAI and Anthropic APIs. Under their standard business and API terms, API inputs and outputs are not used to train their general models by default. Their standard abuse-monitoring or safety systems may retain API inputs and outputs for up to 30 days. Longer retention may apply where content is flagged for policy enforcement or where law requires it. Revise does not currently represent that every request receives zero-data-retention treatment.

Provider retention is separate from Revise's own product-data retention and may continue briefly after you delete data from Revise.

• OpenAI business data privacy
• Anthropic commercial data retention

11. Retention

Revise keeps personal data only for as long as needed for the purpose described, including service delivery, security, dispute resolution, and legal obligations. Current product limits include:

• Synced documents remain until you delete them or delete your account. Deletion markers may remain while needed to synchronise deletion.
• Saved Personal Voice examples are retained for up to 365 days and are capped at 500 examples per user, unless the product displays a different current limit before you opt in.
• Final-edit learning evidence is retained for up to 180 days and is capped at 1,000 records per user, unless the product displays a different current limit before you opt in.
• Derived Personal Voice profiles and learned adjustments remain until reset, deleted, made obsolete, or removed with the account. Revocation stops their future application but does not itself delete retained data.
• Detailed content-free Draft, Rewrite, and outcome events are generally retained for up to 90 days, after which they are aggregated or deleted.
• Authentication, subscription, transaction, security, support, and legal records remain for the life of the account and for a limited period afterwards where needed for fraud prevention, accounting, dispute resolution, or law.
• AI providers may retain submitted inputs and outputs for up to 30 days under their standard practices, subject to the exceptions described above.

Automated deletion jobs may require a short processing period after a retention limit expires. Encrypted or access-restricted backup copies can remain until the applicable backup is rotated and are not restored for ordinary product use after a valid deletion request.

12. Security

Revise uses safeguards designed to protect data, including encrypted network transport, access controls, rate limits, account and token protections, platform credential storage, environment separation, provider authentication, data minimisation, bounded retention, and deletion controls.

No internet service is completely secure. Revise does not claim that writing submitted for cloud processing is end-to-end encrypted because our service and selected AI provider must process it to return a result. Please do not submit highly sensitive personal, medical, financial, legal, classified, or confidential information unless you have assessed that cloud processing is appropriate and authorised.

13. International transfers

Revise operates from the United Kingdom and uses providers that process data in the United Kingdom, United States, European Economic Area, and other locations. Where required, we rely on adequacy regulations, contractual safeguards such as approved standard contractual clauses or the UK international data transfer addendum, and supplementary security measures.

14. Your rights and choices

Depending on where you live, you may have rights to access, correct, export, delete, restrict, or object to processing of your personal data, and to withdraw consent. You may also have the right to complain to a data-protection authority.

• Use Revise settings to control AI actions, Personal Voice, documents, sessions, and account deletion.
• Use browser settings to remove the Chrome extension or its permissions.
• Use iOS Settings to disable Full Access or remove the Revise keyboard.
• Use Apple or Stripe account tools to manage the subscription sold by that provider.
• Email [email protected] for a privacy request or if an in-product control is unavailable.

We may need to verify your identity before completing a request. We may retain limited information where required by law or where a narrow exemption applies. UK users may complain to the Information Commissioner's Office.

• UK Information Commissioner's Office

15. Account deletion

You can initiate deletion using Revise account settings. Deletion removes the account and associated documents, Personal Voice examples and evidence, derived voice records, preferences, identities, and active authentication records from Revise's primary systems. Limited content-free transaction, deletion, security, legal, or fraud-prevention records may remain where necessary.

Provider security copies and Revise backups may remain for their limited retention periods. Deleting a Revise account does not automatically cancel an Apple App Store subscription, which must be managed through Apple.

16. Children

The Services are not directed to children under 13. Users must also meet any higher minimum age that applies where they live. A user under 18 must have permission from a parent or legal guardian. If you believe a child has provided personal data contrary to these rules, contact us so we can investigate and delete it where appropriate.

17. Sale, advertising, and tracking

Revise does not sell personal data. Revise does not use writing submitted for AI processing or Personal Voice to build third-party advertising profiles. Public-site analytics providers may use cookies or similar technologies as described above. Revise treats any consent required for non-essential website analytics separately from consent to process writing or provide Personal Voice.

18. Changes to this policy

We may update this policy as the Services, providers, or law change. We will post the revised policy with a new date and give additional notice through the Services or by email when a change materially affects your rights or an existing consent. Where required, we will ask for consent again before applying a materially expanded optional use of personal data.

19. Contact

For privacy questions, complaints, or rights requests, contact Revise at [email protected].