This policy explains what Redactron collects, why, and who else sees it. It
covers the API gateway at api.redactron.ai, the console at
app.redactron.ai, and this website.
Account information. When you sign in with Google we receive your email address, name and profile picture from Google, and we store the identifier Google issues for you. We do not receive or store your Google password.
Request records. For every API request we record the time it arrived, the workspace and key that made it, the model requested, token counts reported by the provider, the amount charged and the price version it was charged at, and the outcome — completed, refused, or failed, and why. This is what the console shows you and what your balance is drawn against.
Prompts and outputs. Your request body is transmitted to the selected provider and its response is returned to you. By default this content is not stored: serving the request is the only thing it is used for, and it is not part of the request record described above.
Content is only ever captured where a retention policy on your workspace explicitly permits it. When that applies, the capture carries a redaction profile and its own deletion deadline, and the request record names the policy version that allowed it — so what was kept, under which rule, and until when are all answerable. Nothing is retained silently, and retained content is never used to train models.
Technical data. Standard server information — IP address, user agent, timestamps — collected when you use the website, console or API, and used for security, abuse prevention and debugging.
We do not sell your data, and we do not share it with advertisers.
We process account and request data to perform our contract with you — you cannot be billed accurately without it. We process technical data on the basis of our legitimate interest in keeping the Service secure and available. Where the law requires consent, we ask for it.
API keys are stored as hashes — we cannot read your key, which is why a secret is shown once and never again. Traffic is encrypted in transit. Access to production data is restricted to people who need it to operate the Service. No system is perfectly secure, and we will tell affected users promptly if we discover a breach of their data.
Depending on where you live, you may have the right to access, correct, export or delete your personal data, to object to or restrict processing, and to complain to a supervisory authority. Write to support@redactron.ai and we will act within the time the applicable law allows.
The console sets a session cookie to keep you signed in. It is strictly necessary — sign-in does not work without it. We do not use advertising or cross-site tracking cookies.
Our infrastructure and our providers operate in several countries, so your data may be processed outside the one you are in. Where the law requires a transfer mechanism, we rely on one.
The Service is not for anyone under 16, and we do not knowingly collect their data. If you believe a child has given us data, tell us and we will delete it.
If we change this policy materially we will give reasonable notice before it takes effect. The date at the top always reflects the current version.