1. Who we are
BlueWhiteNile AI operates the API and console at bluewhitenile.com and is the controller of the personal data described here. Contact: [email protected].
2. What we collect when you sign in
When you sign in with Google, Google sends us a signed token containing its account identifier, your email address, and whether that address is verified. When you continue with WhatsApp, Twilio Verify receives the telephone number and one-time code and tells us whether the verification was approved.
New account entry stores an BlueWhiteNile AI user ID, a provider-scoped keyed login binding, and verification dates. The provider-neutral account directory does not store the raw Google identifier, email address, WhatsApp number, one-time code, or Twilio verification reference. Older Google account records created before this directory may retain the identifier and email until the controlled identity migration and applicable retention period are complete.
We never receive your Google or WhatsApp password. A WhatsApp one-time code is checked by Twilio Verify and is not written to our account directory, logs, analytics, URLs, or browser storage.
3. What we record when you register
At registration we record the versions of these documents you accepted and the instant you accepted them. We do not ask for or infer your country to decide whether you may create an account. The consent record is kept 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 see the content of requests routed to them. Google processes Google sign-in data, and Twilio Verify processes WhatsApp verification numbers and codes. Our cloud infrastructure provider hosts the service. Each processes data on our instructions or under its own published terms where it acts independently.
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 [email protected] 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
Hetzner hosts our application servers in Helsinki, Finland. Google Cloud hosts retained records and configuration. Cloudflare handles traffic delivery and security. Model providers receive requests routed to them; Google and Twilio process their respective sign-in verification data under their published terms. The console names the model provider for each inference request.
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.