Draft, pending legal review. This page isn't in effect yet. Bracketed items are placeholders to fill in before it's published.
Privacy notice
Draft of 2 November 2026
This notice explains what [Inverse legal entity name] collects, why, who it goes to, how long we keep it, and your rights. It covers people who use Inverse directly. If you use an app built on Inverse, that app's developer decides what is collected about you, and Inverse processes it for them under the data processing agreement.
What we collect
- Account: your name and email from sign-in, and whether you signed in with GitHub.
- What you build: app source you upload, builds, settings, environment variables (encrypted), keys (stored only as hashes), domains.
- Rooms: what people add to a room (notes, boards, reactions) and, with each person's consent, what they say as text and what they do in the app.
- Activity: when you last signed in, when an app or key was last used. We use this only to decide what's unused (see retention below) and to keep Inverse working.
- Payments: handled by Stripe. We keep amounts, dates and payment ids, never card numbers.
- Analytics: anonymous counts of how the Inverse site is used. Never what you write.
- Network: IP addresses for rate limits and daily caps, stored only as a keyed hash and for at most a day.
Why
To run the service you asked for (contract), to keep it secure and stop abuse (legitimate interest), to bill you and keep records the law requires (legal obligation), and for anything else only with your consent, which you can withdraw.
Who we share it with
We don't sell personal information or share it for advertising. These providers process data for us:
- 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]).
Speech-to-text in rooms is done by your own browser (in Chrome, that means Google's speech service); Inverse receives only the text. If a developer stores their own model key, their chosen model provider processes the session under the developer's account.
How long we 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. |
Your rights
You can ask to see, correct, export or delete your personal information, or object to how we use it. In California you also have the right to know what we collect and to not be discriminated against for using your rights. Write to [contact email]; we answer within 30 days. You can also complain to your local data protection authority.
Transfers
Our providers are mostly in the United States. [Transfer mechanism, e.g. Standard Contractual Clauses: to be confirmed with legal review.]
Contact
[Inverse legal entity name], [address]. [contact email].
See also: Terms · Privacy · Data processing agreement