Revise Privacy Policy

Effective date: November 18, 2026

1. Introduction

This Privacy Policy explains how Migraine, Inc. ("Migraine," "we," "us," or "our") collects, uses, and shares information about you when you use Revise, including our document editor, hosted API for document processing and conversion, API console, AI features, MCP connector, and any related websites, applications, and services that link to this Privacy Policy (collectively, the "Service").

By using the Service, you agree to the collection and use of information in accordance with this Privacy Policy. If you do not agree with this Privacy Policy, you must not use the Service.

2. Information We Collect

We collect information in three main ways: (a) information you provide directly to us, (b) information collected automatically when you use the Service, and (c) information we receive from third parties.

2.1 Information You Provide. We collect information you provide when you use the Service, including:

  • Account information: Email address, password, and any profile details you choose to provide.
  • Content and documents: Documents, prompts, text, comments, customer-supplied metadata, uploaded files, and other content you submit to the Service, together with the outputs generated for you ("User Content").
  • Billing information: If you subscribe to a paid plan or purchase API credit, our payment processor (such as Stripe) collects certain billing information, such as your payment method details and billing address. We generally do not store your full payment card number.
  • Communications: Information you provide when you contact us for support or otherwise communicate with us, including by email.

2.2 Information Collected Automatically. When you access or use the Service, we automatically collect certain information, such as:

  • Usage data: Information about your interactions with the Service, such as the features you use, the type of content you work with, and the time and duration of your activities.
  • Device and log data: IP address, browser type and version, device type, operating system, referring and exit pages, and timestamps.
  • Approximate region data: For signed-in accounts, our hosting provider may derive a country and first-level administrative region (such as a state, province, or comparable area) from a request. For this account-region feature, we store the country and region with the date first observed, but not the source IP address, city, postal code, precise coordinates, or internet service provider. We may associate this coarse region with an AI conversation and use it in privacy-filtered, anonymized activity displays.
  • Cookies and similar technologies: We may use cookies and similar technologies to remember your preferences, authenticate you, and understand how you use the Service.

2.3 Information from Third Parties. We may receive information about you from third parties, such as:

  • Authentication providers: If you sign up or log in using a third-party authentication provider (such as Google), we receive basic account information from that provider, including your email address, name, and profile picture.
  • Payment processors: Our payment processor (such as Stripe) may provide us with limited information related to your subscription status, billing, and payments.

2.4 API Information. For API customers, we collect account and key identifiers, file names and attributes, request and retry identifiers, job status and timing, model selections, token and processing usage, error information, and charges. We also collect configuration you provide, such as provider credentials, output-encryption public keys, webhook URLs and subscriptions, and recharge settings. These records support processing, authentication, billing, delivery, and troubleshooting. Avoid placing personal or confidential information in filenames, metadata, or identifiers unless it is needed for your use of the Service.

3. How We Use Information

We use the information we collect for the following purposes:

  • To provide and maintain the Service: including operating the editor, collaboration features, AI features, API jobs and conversions, webhook delivery, and account management.
  • To process transactions: including managing subscriptions, API credit, usage charges, automatic recharge, billing, and payments.
  • To communicate with you: including sending service-related messages (such as account notices, security alerts, and subscription updates) and responding to your requests and support inquiries.
  • To send you product email: including tips for getting started with Revise and occasional news about features and updates. You choose whether to receive these when you create an account. Where the law requires your consent, we send them only if you agree. Every such email has an unsubscribe link, and you can opt out at any time. Opting out does not stop service-related messages.
  • To improve and develop the Service: including analyzing how the Service is used, troubleshooting, and developing new features and offerings.
  • To ensure security and prevent abuse: including detecting, preventing, and responding to fraud, abuse, security risks, and technical issues.
  • To comply with legal obligations: including recordkeeping, accounting, and responding to lawful requests from authorities where required by law.

4. AI Features, API Processing, and Connected Tools

4.1 Sending Content to AI Providers. When you use AI-powered features in the Service, portions of your User Content, prompts, and related metadata are transmitted to third-party large language model (LLM) providers, including OpenAI, Anthropic, Google (Gemini), and xAI (collectively, "AI Providers"), via their APIs so they can generate outputs. This includes AI-assisted PDF and image conversion. Web search may send queries derived from your content.

We share only the information reasonably necessary to generate the requested outputs and to monitor and improve the reliability of our AI features. For internal quality monitoring and bug detection, we use TypeSafe AI (Jev) to assess limited excerpts from saved conversations, including historical conversations, along with tool names, results, and errors. We exclude document bodies returned by tools, tool arguments, and attachments; conversation excerpts may still contain text you included in chat. This information is processed subject to the providers’ terms and privacy policies.

4.2 Model Training and Provider Data Use. Migraine does not use your User Content to train general-purpose machine learning models. When using our own AI Provider accounts, we do not authorize providers to train their models on your User Content. Providers may retain or review content for service delivery, security, or abuse prevention under their terms. If you supply your own provider key or use a connected third-party application, that provider’s terms and your account settings govern its data use, including any training permissions.

4.3 AI Output and Responsibility. AI-generated outputs may be inaccurate, incomplete, or inappropriate. You are responsible for reviewing, editing, and validating any AI-generated content before relying on it. You remain responsible for how you use AI-generated content and for ensuring that its use complies with applicable laws and with our Terms of Service.

4.4 Connecting Third-Party AI Agents and Applications. Revise lets you connect third-party AI agents, assistants, and applications — including AI assistants such as Claude — to your editor account through integrations such as our Model Context Protocol (MCP) connector. You authorize these connections using an API key or an OAuth authorization that you grant. Once connected and authorized, such a tool can access, read, create, edit, export, and (where you grant permission) share documents in your account on your behalf, according to the scopes you approve (for example, read-only access versus read-and-write access). You may also create a document without an account. Before it is claimed, that document is private but accessible to anyone holding its claim link or edit token. Claiming the document disables the claim link, but the creating agent's edit token may continue to provide access until you separately revoke the agent's access.

4.5 Information Shared with Connected Tools. When a connected agent or application accesses your account, the document content, document metadata, and related information it requests are transmitted to that third party and to the AI platform that operates it (for example, Anthropic for Claude). That information is then handled under the connected provider's own terms and privacy policy, which we do not control. You should review those policies before connecting a tool. For Claude, see Anthropic's Privacy Policy. You control which tools are connected and the scopes they receive, and you can review or revoke their access at any time in your account settings; revoking access prevents further access going forward but does not retrieve information already shared.

4.6 MCP Export and Conversion Links. When you use an MCP-connected tool to export a document or convert a file into a downloadable format, we may temporarily store the resulting file with our cloud storage provider and return an unguessable public download link. Anyone who has that link can access the file while it remains available. These temporary files and links normally expire after approximately 24 hours. You should share download links only with people you intend to give access to the exported or converted file.

4.7 Hosted API Processing. The Revise API processes the inputs sent by your application to perform the requested document work or conversion. Revise and, when inference is used, the selected AI Provider process plaintext content. If you configure your own provider key, we use it to authenticate requests to that provider. Its terms and your account settings govern its data use and retention. Paid and unpaid services can have different data-use terms, as described, for example, in Google’s Gemini API terms. Review the applicable terms and settings before submitting content. Revise’s retention periods do not control copies held by AI Providers or your applications.

4.8 API Webhooks. If you register a webhook, we send notifications to the URL you provide for matching jobs across your API account. Notifications contain job and event identifiers, status, timestamps, and retention information, rather than document contents or full results. Your receiver may retrieve results separately using your API key. We retain notification payloads and delivery status to support retries and troubleshooting. Deleting a webhook stops future deliveries, subject to requests already in progress; it does not retrieve information already sent.

4.9 API Download Links. API artifact downloads require account authentication and may redirect to a signed cloud-storage URL valid for five minutes. Anyone holding that signed URL can download the file while the URL and file remain available. The URL’s lifetime is separate from the content retention period described in Section 7. Treat download URLs as confidential and share them only with intended recipients.

5. Cookies and Similar Technologies

We may use cookies and similar technologies (such as local storage) to help operate and improve the Service. These technologies may be used to:

  • Keep you signed in and maintain your session.
  • Remember your preferences and settings.
  • Understand how the Service is used so we can improve it.

You may be able to set your browser to refuse cookies or to indicate when a cookie is being sent, but some parts of the Service may not function properly without cookies.

6. How We Share Information

We may share information about you as follows:

  • Service providers: With third-party vendors and service providers who perform services on our behalf, such as hosting, cloud storage, analytics, email delivery, customer support, and payment processing (including Stripe).
  • AI Providers: With AI Providers as described in Section 4 when you use AI-powered features.
  • Connected AI agents and applications: With agents and applications you authorize through editor integrations or API keys, and with webhook endpoints you configure, as described in Section 4. API keys grant access to resources across the API account; MCP authorizations use the scopes you approve.
  • Legal and safety: With law enforcement, regulators, or other third parties if we believe disclosure is reasonably necessary to comply with applicable law, regulation, legal process, or governmental request; to protect the security or integrity of the Service; or to protect Migraine, our users, or the public from harm or illegal activities.
  • Business transfers: In connection with a merger, acquisition, financing, reorganization, sale of assets, or similar transaction, or in the event of insolvency, bankruptcy, or receivership, your information may be transferred to a successor or affiliate as part of that transaction, subject to this Privacy Policy.

We do not sell your personal information in the traditional sense of selling data in exchange for money.

7. Data Retention

We retain your information for as long as necessary to fulfill the purposes described in this Privacy Policy, including providing the Service, complying with legal obligations, resolving disputes, and enforcing our agreements. The actual retention period may vary depending on the type of information and the context of your interactions with the Service. To diagnose failures in our MCP tools, we automatically store encrypted failure records that may include tool arguments, error details, relevant document state, and preceding read context. These records are available only to authorized administrators and expire from the application database after 72 hours; expired records are removed by a periodic cleanup process. Successful MCP calls are not stored as a separate diagnostic log. Database backups follow their separate retention lifecycle.

You may delete certain User Content at any time through the Service, subject to any technical or legal limitations. We may retain backup copies of data for a limited period of time, as well as records that are reasonably necessary for business or legal purposes.

API Uploads. Ephemeral uploads are the default. An unused ephemeral upload expires 24 hours after upload. Once claimed by a job, it is retained while that job is active, deleted on success, or retained for 24 hours after failure or cancellation unless deleted earlier. Persistent uploads remain until explicitly deleted and are not removed when a job’s content expires. Deletion may be deferred while content is needed by active work.

API Job Content. Prompt and conversion content, including inputs, results, document state, customer metadata, and output artifacts, expires 24 hours after the job succeeds, fails, or is cancelled. This period begins at the terminal state, not at submission; queued, running, and paused jobs still require their content. You can request earlier deletion after a job finishes. If you enable deletion after a designated completion webhook, a successful acknowledgement triggers deletion, so retrieve and store needed results first. Expiry and deletion remove content from API access; storage cleanup runs asynchronously.

API Records and Other Copies. Content deletion preserves billing receipts, job and account identifiers, status, and operational records needed for billing, security, and support. Webhook notification and delivery history is retained for 30 days and removed by periodic cleanup. Backup copies follow their separate retention lifecycle. Deleting API content does not remove copies already sent to providers, webhook receivers, or other recipients, or copies your application has downloaded.

8. Data Security

We use reasonable technical and organizational measures to protect your information against accidental or unlawful destruction, loss, alteration, unauthorized disclosure, or access. However, no method of transmission over the internet or method of electronic storage is completely secure, and we cannot guarantee absolute security.

API Credentials. Revise API keys are stored as hashes for authentication. Provider keys are stored encrypted and decrypted when needed to authenticate provider requests. Webhook signing secrets are also stored encrypted. Deleting or replacing a provider key revokes it in Revise and removes its stored secret from the active application database; backup copies follow their separate retention lifecycle.

Optional Output Encryption. When requested, we encrypt exported artifact bytes using the public key you provide. You retain the private key; do not send it to Revise. This protection applies to exported files, not uploaded inputs, plaintext processing, or text and metadata returned in API responses. It does not make processing end-to-end encrypted or prevent the selected AI Provider from receiving content needed for the request.

9. Sensitive and Regulated Data

The Service is not designed to store or process highly sensitive or regulated data. You must not use the Service to store, process, or transmit:

  • Protected Health Information (PHI) or other health information regulated under HIPAA or similar laws.
  • Payment card numbers, bank account numbers, or other financial account credentials.
  • Government-issued identification numbers or similar highly sensitive identifiers.
  • Classified or confidential government information, or any information you are not authorized to store or share.

If you choose to upload such information in violation of this Policy, you do so at your own risk and we disclaim any responsibility or liability arising from such use.

10. International Data Transfers

The Service is operated from the United States. If you access or use the Service from outside the United States, your information may be transferred to, stored, and processed in the United States or other countries that may have data protection laws that are different from those in your jurisdiction. By using the Service, you consent to the transfer of your information to the United States and other countries as described in this Privacy Policy.

11. Your Rights and Choices

Depending on your location and applicable law, you may have certain rights regarding your personal information, such as the right to:

  • Access the personal information we hold about you.
  • Request correction of inaccurate or incomplete information.
  • Request deletion of your personal information, subject to certain exceptions.
  • Object to or restrict certain processing of your information.
  • Withdraw consent where processing is based on your consent.

To exercise any of these rights, you can contact us at support@revise.io. We may need to verify your identity before responding to your request, and certain rights may be limited or not available depending on your jurisdiction.

If an organization submits your information through the Revise API, you can also direct privacy requests to that organization. It controls its application, the content it submits, and copies it retains. We will assist with requests as required by applicable law.

12. Children's Privacy

The Service is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If we learn that we have collected personal information from a child under 13, we will take reasonable steps to delete it. If you believe that a child under 13 has provided us with personal information, please contact us at support@revise.io.

13. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we make material changes, we will provide notice by, for example, posting the updated Privacy Policy at /privacy and updating the effective date at the top, and/or sending you an email or in-app notification. Your continued use of the Service after the updated Privacy Policy becomes effective constitutes your acceptance of the revised Privacy Policy.

14. Contact Us

If you have any questions or concerns about this Privacy Policy or our privacy practices, please contact us at support@revise.io.

AI Agent