Draft, pending legal review. This page isn't in effect yet. Bracketed items are placeholders to fill in before it's published.
Data processing agreement
Draft of 2 November 2026
This agreement is part of the terms. It applies when your app uses Inverse Interface, rooms or hosting to handle personal data about your users. For that data, you are the controller and [Inverse legal entity name] is the processor.
1. What Inverse processes
- Who: the people who use your app, as aliases (“Speaker A”) to your coding agent.
- What: consented session events (pages, clicks, form submits without their values, errors), text people choose to say, reactions, room content, and intent packages built from them.
- Why: only to provide the service you configure: capture, building intent, rooms, delivery to your agent.
2. Your instructions
Inverse processes this data only as you instruct through the product and the API, and tells you if an instruction would break the law.
3. Security
- Consent before recording; typed values and password and payment fields are never recorded; redaction in the browser and again on the server.
- Encryption in transit; environment variables and model keys encrypted at rest; API keys stored only as hashes.
- [Staff access and confidentiality commitments: confirm before publishing.]
4. Subprocessors
You authorize these subprocessors. We'll email you 30 days before adding or replacing one, and you can object.
- Vercel: Hosting the Inverse site and API, and building and serving hosted apps (United States).
- Cloudflare: Live rooms and the registry of apps, accounts and Interface data (Durable Objects) (Global edge network).
- WorkOS: Sign-in and account identity (United States).
- Stripe: Payments, subscriptions and payouts (United States).
- Resend: Email (beta invites and account notices) (United States).
- PostHog: Anonymous product analytics about how the Inverse site is used ([United States or European Union: confirm region]).
5. Helping you
Inverse helps you answer your users' requests to see, export or delete their data, and with impact assessments where the law requires them. You can delete sessions and packages through the API at any time.
6. Breaches
Inverse tells you without undue delay, and within 72 hours of becoming aware, of a breach affecting your users' data, with what we know and what we're doing about it.
7. Retention and deletion
Inverse keeps your users' data only as long as below, and deletes it when you delete the project or your account, except where the law requires us to keep it.
| What | How long we keep it |
|---|---|
| Hosted app on the Free plan | Paused after 90 days with no visits, rooms, deploys or dashboard visits, after emails 14 and 3 days before. Deleted 90 days after pausing unless resumed. (planned) |
| Hosted app on a paid plan, or with buyers | Kept while the subscription or any buyer's access lasts. |
| Old deployments of an app | The newest 3 plus the live one. |
| An app whose first build never succeeded | Removed 7 days after the failed build. (planned) |
| Custom domain that was never verified | Removed 14 days after it was added. (planned) |
| Room notes and boards | Deleted after 90 days with no one in the room on Free, 12 months on paid plans, after emails 14 and 3 days before with an export link. (planned) |
| Interface session events (what people did in an app) | Deleted 30 days after the session's last activity. |
| Interface intent packages | Deleted 12 months after the session's last activity. |
| Interface secret keys | Revoked after 180 days unused (test keys after 90), after notice. (planned) |
| Beta sign-up emails | Deleted 12 months after the list's last activity, after notice to the list owner. (planned) |
| Free account | Deleted after 24 months without signing in, after emails 30 and 7 days before. Never for accounts with paid history. (planned) |
| Purchased credit | Doesn't expire. |
| Billing and payout records | Kept as long as tax and dispute rules require, even after an account is deleted: amounts, dates and payment ids only. |
| Request logs | 7 days. |
| Sign-in tokens for the CLI | Expire after 90 days. |
8. Audits and transfers
[Audit rights and international transfer terms, e.g. Standard Contractual Clauses: to be written with legal review.]
See also: Terms · Privacy · Data processing agreement