1. Who we are
Redactron operates the API and console at redactron.ai and is the controller of the personal data described here. Contact: privacy@redactron.ai.
2. What we collect when you sign in
When you sign in with Google we receive, from Google, a signed token containing your Google account identifier, your email address, and whether Google has verified that address. We store the identifier and the email.
We store the identifier because it is stable and the email is not: an email can be reassigned, and binding your account to the identifier is what stops a later owner of the same address reaching your data.
We never receive your Google password, and we do not ask for one.
3. What we record when you register
At registration we record the country you select, the version of these documents you accepted, and the instant you accepted them. That record is the evidence that consent was given, and we keep it for as long as the account exists and for six years afterwards.
4. What we collect when you use the API
For every request we record a request identifier, the workspace and API key that made it, the model and route chosen, token counts, the amount charged, timings, and the outcome.
We do not store your prompts or the model's completions as part of normal operation. Where a feature you switch on requires retaining content, the console says so on the screen that switches it on, and it is off by default.
Providers we route to receive the content of your request. Which provider received which request is visible to you in the console activity view.
5. Why we are allowed to do this
Signing you in, routing your requests, and billing you are necessary to perform the contract you entered by accepting the Terms of Service.
Keeping accounting records is a legal obligation. Preventing abuse of the API rests on our legitimate interest in keeping the service usable for everyone.
Consent is the basis for anything the console asks you to switch on explicitly. You can withdraw it by switching it off, and doing so does not affect what happened before.
6. Who else sees it
Model providers, for the content of the request you send them. Google, for sign-in. Our cloud infrastructure provider, which hosts the service. Each processes data on our instructions or, for the providers, under their own published terms.
We do not sell personal data and we do not use your requests to train models.
7. How long we keep it
Account and consent records: while the account exists, then six years. Request activity and billing records: six years, because they are accounting records. Sign-in logs: ninety days.
When a retention period ends the record is deleted, not archived.
8. Your rights
You can ask us for a copy of your personal data, ask us to correct it, ask us to delete it, or object to a use of it. Write to privacy@redactron.ai and we will answer within thirty days.
Deletion does not extend to records we are legally required to keep, and we will tell you which ones those are rather than silently keeping them.
If you think we have handled your data badly, you may complain to your national data protection authority.
9. Where the data is
The service runs in Google Cloud's europe-west1 region. Model providers may process your request content outside that region; the console names the provider for every request so you can see where a request went.
10. Changes
We will publish a new version with a new date rather than editing an old one in place, so the version you accepted stays readable.