What we collect, and who sees it.
Last updated 23 September 2026. Written to describe what the platform actually does rather than to cover every eventuality — if something here does not match your experience of the product, that is a bug and we want to hear about it.
This document is awaiting legal review
It is an accurate description of the platform’s data handling, written from the system itself. It has not yet been reviewed by a lawyer and it is not a substitute for one. If you are evaluating Supero under a compliance obligation, write to [email protected] and we will tell you exactly where we are.
Who we are
Supero operates this platform. Our registered entity details are being finalised and will be published here. Until then, the fastest route to a named human is [email protected].
Data we hold about you
These are the fields the platform actually stores on an account. There is no longer list held elsewhere.
- ✓ Identity: username, email, full name, job title, department
- ✓ Credentials: a password hash (never the password), password-change timestamps, whether a change is required
- ✓ Contact: phone number, email-verification state and timestamp
- ✓ Preferences: timezone, language
- ✓ Access: role, permissions, whether the account is enabled, the domain it was registered in
- ✓ Security events: last login time, last login IP address, failed login attempts, lock-until time
- ✓ Invitations: who invited the account, when, and when the invitation was accepted
We run no advertising trackers, no profiling and no cross-site tracking, and we neither sell personal data nor share it for anyone else’s marketing. The marketing site counts page views with Cloudflare Web Analytics, which is cookieless: it sets nothing on your device, cannot follow you to another site, and records page views only. It does not run on this page, or on the DPA or the terms, and it is not used inside the applications you build.
Data inside the applications you build
Applications you create hold whatever data you put into them. For that data you are the controller and we are the processor: we hold it to run the service, we do not use it for our own purposes, and we do not use it to train models. The Data Processing Addendum is the document that governs this, and it is the one your legal team will want.
Content you send to the AI builder
When you describe an application, that description — with the schema context needed to act on it — is sent to a third-party model provider to generate the result. Treat a generation prompt the way you would treat a chat window: if you would not paste something into one, do not paste it into the other.
Connecting Supero to an AI client (MCP)
Supero publishes an MCP server, so you can connect your Supero domain to Claude or another MCP client and have it read and change your data directly. This section describes that path specifically, because it moves data somewhere the rest of this policy does not cover.
The server is reachable at api.supero.dev/mcp/v1/messages and you authenticate to it with a Supero API key or a session token. What the connection can reach is scoped to the domain that credential belongs to.
The connection exposes tools that both read and write: searching and reading your records, creating, updating and deleting them, managing schemas and connectors, and building and deploying applications. Treat a connected client as being able to do what you can do in that domain, and grant it a credential scoped to only what you want it to touch.
What leaves Supero. When a tool returns data, that data goes to whichever client you connected — and, in the normal case, into the conversation that client is having with its model provider. If you ask Claude to search your customer records, those records are sent to Anthropic as part of that conversation. That client is your tool rather than ours: we do not control, and cannot see, how it stores or retains what it receives. Separately, the application-building tools on this connection make their own calls to a model provider from our side, the same ones described under “Content you send to the AI builder” above.
Turning it off. Deleting the API key in your Supero dashboard stops it authenticating. Disabling a key rather than deleting it can take longer to take effect, because validated keys are cached — if you need access cut off now, delete the key. A session token is separate from any API key, so revoking one does not end a connection made with the other. Anything the connection already created — applications, live URLs, connectors, bound data sources — keeps running until you remove it.
Who else processes your data
Every third party that receives data, and what they receive. This list is maintained from the running system, not from memory.
Anthropic
AI model provider. Application descriptions, prompts and schema context you submit to the AI builder are sent to the model provider to generate your application.
This is the one most people want to know about. If you would not paste it into a chat window, do not paste it into a generation prompt.
OpenAI
AI model provider (alternative route). The same generation content, where a deployment is configured to route to OpenAI models instead.
Google Cloud Platform
Hosting and application deployment. Applications you deploy run on Google Cloud Run. Application data at rest and in transit sits in that environment.
MongoDB Atlas
Managed database. Primary data store for platform and application records.
Amazon Web Services
Object storage. Files and attachments uploaded to the platform, and generated application bundles, are stored in S3.
Cloudflare
CDN, edge network and website analytics. Requests to our domains pass through Cloudflare, which processes connection metadata including IP address. Cloudflare Web Analytics also counts page views on the marketing site: it is cookieless, sets nothing on your device, cannot follow you to other sites, and does not run on the legal pages. It is not used inside applications you build.
Stripe
Payments. Billing identifiers and subscription state. Card details go directly to Stripe and are never stored by us.
SendGrid
Transactional email. Email address and message content for verification codes, invitations and notifications.
Google Fonts
Web fonts on this website. Loading supero.dev requests fonts from Google, which receives the visiting IP address.
How long we keep it
Account and application data is held for as long as the account exists. When you delete a project or an account, the records are removed from the live system; backups age out on their own cycle rather than being edited. Security event logs — logins, failed attempts, IP addresses — are kept because they are what lets us investigate an incident.
If you need a specific retention commitment in writing, ask. We would rather agree one we can keep than publish a number we cannot.
Your rights
Depending on where you live you may have the right to access, correct, export or delete your personal data, to object to processing, and to complain to a regulator. To use any of them, write to [email protected]. We do not require a particular form of words, and we will not make you fight for it.
Security
What we do and — just as importantly — what we do not do yet is on the security page. It names our gaps rather than hiding them. If you have found a vulnerability, that page tells you how to report it.
Changes
If this policy changes in a way that affects you, we will say so rather than quietly moving the date at the top.