Does Rewrait use my text to train AI models?
No. Text you submit is processed to return the rewrite and is not used to train Rewrait's models or any third-party model. On Team plans this is contractual: a written no-training guarantee plus a DPA. Rewrait limits when text is received and retained. It receives text only when a user selects text or dictates a draft and triggers a shortcut. It does not continuously collect your company's writing. Rewrite history is off by default, meaning even your own past rewrites are not retained unless you opt in, and feedback events never store text. The AI subprocessors that perform rewrites (OpenAI and Google Gemini) see only the text of the specific request, plus whatever approved source context the shortcut is configured to read.
What happens to my text after a rewrite?
It comes back to you and, by default, that is the end of it. Your selected text and the shortcut's approved context go to the AI provider. The provider returns the rewrite, and Rewrait replaces the selected text in your app. Rewrait does not store the text unless you have turned on rewrite history, which is off by default. If you enable history, every item can be deleted individually, and turning history off again stops new items from being saved. Thumbs-up and thumbs-down feedback is recorded as an event without the underlying text. Voice dictation works the same way: audio is transcribed by Deepgram at the moment you dictate, and the transcript follows the same rules as typed text.
Can Rewrait edit or delete files in Notion, Confluence, or Google Docs?
No. All three integrations request read-only OAuth scopes, so Rewrait is technically unable to write, move, or delete anything in your docs. The permission is never granted, not merely unused. The workspace owner approves a whitelist of specific sources, and shortcuts can read only pages on that list. Each source is fetched read-only, cached to limit repeat fetches, and capped at 12,000 characters. Rewrait does not sync the full knowledge base. OAuth tokens for these connections are stored AES-encrypted, and the owner can disconnect an integration at any time, which severs access immediately. If your security review needs the exact scope strings we request from each provider, email [email protected] and we will send them.
Is Rewrait SOC 2 certified?
Not yet. SOC 2 certification is on our roadmap. Today, Rewrait offers the commitments documented on this page: on-demand processing, no training on your text, history off by default, and read-only integrations with encrypted OAuth tokens. Team plans include a DPA and written no-training guarantee. Rewrait is a small company and does not yet have SOC 2 certification, but a founder responds directly to security questionnaires. If your procurement process requires a SOC 2 report before purchase, email [email protected]. We will tell you whether our certification timeline fits yours.
What data does Rewrait store about our company?
Rewrait stores account data, workspace configuration, and limited content under the conditions below. Account data: names, emails, credentials or OAuth identities, workspace membership, and billing records. Card details live with Stripe, never with us. Configuration: your styles, shortcuts, workflows, the approved source whitelist, and AES-encrypted OAuth tokens for connected integrations. Rewrite content: none by default. Rewrite history is opt-in per user and deletable item by item; feedback events store no text; cached copies of approved sources are capped at 12,000 characters and fetched read-only. The application and its Postgres database run on Fly.io, and the workspace owner can disconnect any integration at any time, which cuts off source access immediately. If your review needs this as a formal data inventory, or you have a questionnaire in your own format, email [email protected]. A founder fills it in directly.