1. Scope and who we are
This Privacy Policy explains how Revise, referred to as "Revise", "we", "us", or "our", collects, uses, shares, and protects personal data when you use our websites, web application, Chrome extension, iPhone application, custom keyboard extension, share extension and Shortcuts actions, APIs, account and document sync, shared document links, About you and Personal Voice features, customer support, and related services together called the "Services".
Revise operates from the United Kingdom and is the controller of personal data described in this policy, except where a provider acts as an independent controller under its own terms. Privacy questions and rights requests can be sent to [email protected].
2. The short version
- Revise processes your writing when you deliberately use a writing feature or choose to synchronise, save, share, or export that text.
- About you holds the answers you give Revise about your work and who you write to, plus short notes Revise derives from your requests. It shapes suggestions and AI requests. You can see it, edit it, and clear it in Account.
- 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 that names the AI providers. 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.
- xAI transcribes voice notes you choose to share with or add to Revise. Revise does not store or log the recording, and xAI's API does not use API content to train its models without permission.
- 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.
When a web free trial is started with a payment card, Stripe gives Revise a card fingerprint, which is an identifier for the card and not the card number. Revise keeps it to stop the same card being used for repeated free trials. If you redeem a referral code, Revise records the code, the referring account, your account, and the status of any bonus.
Revise records how an account first arrived, such as the sign-up platform and channel, and on the web any campaign parameters in the link, the referring page, and the first Revise page visited.
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.
The Revise share extension accepts text, a link, a single image, or a single voice note that you send to Revise from another app. Text in an image is recognised on your iPhone. For a link, the extension reads the linked page from your iPhone. When the card opens, it checks your account with Revise so it can show what you can do; that check carries none of the shared content.
When you tap a suggestion or write a request on the card, the extension sends the shared item and your request to Revise over your signed-in session, and Revise processes it as described above. The request and its reply are kept as a chat in your account, which you can see, continue, or delete in Revise. A voice note is sent for transcription as soon as you share it, so the card can show its words, as described under Voice notes below.
If you choose Open in Revise, the extension places the item, and anything you typed, in storage shared with the Revise app, together with the identifier of the app you shared from, which Revise uses only to label where the item came from. The extension may ask for permission to show a notification that takes you to the item or chat in Revise. You can turn Revise notifications off in iOS Settings.
Voice notes
When you share a voice note to Revise or add an audio file to a chat, the recording is sent to Revise's servers and on to xAI, which transcribes it with its Grok speech-to-text model. Names you have already given Revise may be sent with it to help spell them correctly. Revise does not store or log the recording or the transcript at this step; the transcript is returned to your device and is kept only if you send it in a chat, where it is stored like any other source. Free accounts have a daily limit on voice note length.
Revise provides Shortcuts and Siri actions. The Rewrite Clipboard action reads the text on your clipboard when you run it and sends that text to Revise for rewriting. Revise does not otherwise read your clipboard in the background. Revise may schedule notifications on your device if you allow them. It does not use remote push notifications.
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.
To improve autocorrect and suggestions, the keyboard keeps a personal vocabulary of words you type, with counts and the last day each was used. It is stored only inside the keyboard on your device, is not shared with the Revise app, and is never sent to Revise. Deleting Revise from your iPhone deletes it.
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.
Shared links
If you publish a link to a draft, Revise stores a copy of that draft's title and text and shows it to anyone who has the link. The copy stays until you revoke the link or delete your account. A revoked link stops working and is never reused.
Google Drive
If you connect Google Drive, Revise stores your Google account email, the permissions you granted, and an encrypted token that lets Revise save documents to your Drive as Google Docs. When you export, the document is sent to Google. You can disconnect at any time, and the connection is deleted with your account.
6. About you and Personal Voice
About you
When you first use the iPhone app, and later in Account, Revise asks a few short questions: your field or role, what you write, who you write to, and the situations that come up most. You can add short free-text details and a note. Revise also records your device region so that suggestions and spelling fit where you are. These answers are stored with your Revise account as part of providing the service. Answering is optional and you can skip the questions.
Revise also builds a short record from how you use it. It keeps your recent requests, each shortened to about 200 characters and including the audience you named, for up to 30 days and no more than 20 at a time. From your requests, the drafts you keep, and text you paste, Revise derives short notes about your work and the people you write to. Each note is shown in About you with where it came from.
Revise uses About you to choose the starting points it suggests and, when you run a cloud AI action, includes relevant parts of it in the request sent to OpenAI or Anthropic so the writing fits your situation. If you confirm or correct a detail Revise assumed in a draft, such as the audience, purpose, tone, or a fact, that correction is sent with your follow-up requests in the same exchange.
In Account you can view and change your answers, remove any individual note, clear your answers, and forget your recent requests. Revise stops using a removed item at once. Please do not put sensitive information about yourself or other people into these fields.
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. The profile can also include short facts Revise has learned about you and your work from what you keep, each recorded with where it came from. Revise shows you these facts when it learns them and you can remove them individually. 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, or clipboard contents, and they do not record the addresses or domains of pages where you use the Chrome extension or keyboard. Events from the Revise web app include the Revise page path and the page that referred you to Revise.
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.
The iPhone app uses Meta App Events to measure app installs, sessions, free-trial starts and paid subscriptions, and to understand the results of Revise's advertising. Meta receives app activity and subscription event details, including the subscription product and, for paid events, the price and currency, together with SDK-generated installation or device identifiers and app/device metadata. Revise does not send writing, prompts, documents, email addresses, account identifiers, receipts or transaction identifiers to Meta. Advertiser ID (IDFA) collection and automatic event logging are disabled, and event-data use is restricted to analytics and conversion measurement. This integration does not request permission for cross-app tracking.
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.
Our website and the Revise web app use the Meta Pixel, and our servers use Meta's Conversions API, to measure the results of Revise's advertising: page views, clicks on the buttons that lead to the App Store, the Chrome Web Store or the web app, account creation, and the start of a free trial. Meta receives these events with Meta's cookie identifiers, the page address, browser and device data and IP address, and, for account creation and trial starts, a hashed (SHA-256) copy of your email address and account number. Revise does not send writing, prompts, documents or payment details to Meta.
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.
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.
Revise uses xAI's commercial API only to transcribe voice notes. Under xAI's API terms, API inputs and outputs are not used to train its models without permission, and API traffic is retained for up to 30 days for abuse monitoring and then deleted.
Provider retention is separate from Revise's own product-data retention and may continue briefly after you delete data from Revise.
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.
- About you answers and derived notes remain until you change, remove, or clear them, or delete your account. Recent requests are kept for up to 30 days and no more than 20 at a time.
- A shared link and its copy of the draft remain until you revoke the link or delete your account.
- Detailed content-free Draft, Rewrite, and outcome events are generally retained for up to 90 days, after which they are aggregated or deleted. Other content-free product events and usage counters may be kept for longer while they are needed to operate, secure, and measure the Services.
- 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, About you, Personal Voice, documents, shared links, 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.
15. Account deletion
You can initiate deletion using Revise account settings. Deletion removes the account and associated documents, shared links, About you answers, notes and recent requests, Personal Voice examples and evidence, derived voice records, preferences, identities, any Google Drive connection, and active authentication records from Revise's primary systems. Limited content-free transaction, deletion, security, legal, or fraud-prevention records may remain where necessary, including App Store and Stripe transaction records and a trial card fingerprint that is no longer linked to your account.
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].
Questions
Questions about your data, your subscription, or these terms? Email us and we will get back to you.
[email protected]