Privacy Policy

Last updated: 10 November 2026

This policy describes how Cloakray ("Cloakray", "we", "us") handles data when you use our website, console, and API (together, the "Service"). Read it together with our Terms of Service.

In short

We do not store your prompts or responses, and we never train on your data. A request is passed to the model provider that serves it and is not saved to our storage. We keep only the metadata needed to bill you and show you your usage: when the request was made, which model and project it used, how many tokens it consumed, how long it took, and what it cost.

We collect as little as we can. We do not sell personal information, we run no advertising or analytics trackers on the Service, and the only party that sees your prompts and responses is the provider serving the request.

What we collect

Account data. Your email address and, if you give one, your name. If you sign in with GitHub or Google, the basic profile details that provider shares with us. We also record the organizations and projects you belong to, your role in each, and the invitations you send or accept.

Usage metadata. For each API request: the time, the model, the project and API key used, the request path, the HTTP status, the duration, the token counts the provider reports, and the cost. We do not record the prompt, the response, the system prompt, tool definitions, attachments, or any other request or response content. None of it is written to our database.

Payment data. Your credit balance and top-up history. Crypto payments are handled by our payment processor. For each payment we keep the processor's payment identifier, the coin and network, the amount, its US-dollar value, and its status. Depending on the processor and the coin, this can include the transaction hash and the sending or receiving wallet address. Keep in mind that most blockchains are public: anyone can look up a transaction and the addresses involved, independently of us.

Session data. A session cookie that keeps you signed in, and cookies that remember which organization and project you have open. The console does not work without them.

Support correspondence. Anything you email us, kept for as long as we need it to help you.

How we use it

We use your data to run the Service: to sign you in, route your requests, enforce your balance and rate limits, and show you your usage. We use it to credit your payments and keep the accounting records we are required to keep, to protect the Service and its users by investigating abuse, fraud, and attacks, and to reply when you contact us and send service notices, for example about a material change to our terms. If we ever send marketing email, it will be opt-in, and you can unsubscribe at any time.

We do not use your prompts, responses, or usage metadata to train, fine-tune, or evaluate any model, whether ours or anyone else's.

Legal bases

Where data protection law asks for a legal basis, we rely on contract, to provide the Service, serve your requests, and charge for them; on legitimate interests, to secure the Service and your account, prevent fraud and abuse, and improve the Service, without overriding your rights; and on legal obligation, to keep accounting records and answer lawful requests. Where we ask for your consent, for example for marketing email, you can withdraw it at any time.

Model providers

To serve a request, we send it to the provider that runs the model you picked. That provider necessarily receives your prompt and produces the response, and it handles them under its own privacy policy and retention practices, which we do not control. Picking a model means picking its provider. If your data has special handling requirements, check the provider's policy first.

Service providers

Only the service providers we need see your data, and only for that purpose:

• Payments: our crypto payment processor, to create payment addresses, confirm payments on the blockchain, and keep the payment records described above.
• Hosting and database: our hosting and database provider, to run the Service and store the account, project, payment, and usage metadata described above.
• Model providers: the companies running the models we offer. Each receives the prompts and returns the responses for the requests it serves.
• Sign-in: GitHub and Google, only if you choose to sign in with them, to confirm your identity and share the basic profile details described above.

We may also disclose data when the law requires it, or when it is needed to establish or defend a legal claim, and we push back on requests we believe are overbroad or unlawful. If the Service is transferred to a new owner, your data may move with it, still subject to this policy.

How long we keep it

Account, organization, and project records exist for as long as your account does. Individual request-metadata rows are deleted 90 days after the request, once their usage has been billed. Hourly usage totals per project, model, and key are kept longer so your usage history stays available, and contain no request content. Payment records are kept for as long as accounting law requires, which can outlast the deletion of your account.

Security

API keys are stored hashed, in a form nobody, including us, can read back. Traffic to and from the Service is encrypted in transit, and only the people who need it can access production data. If a key leaks, rotating it in the console is the quickest way to limit the damage. No system is perfectly secure, and we do not claim ours is.

Your rights

You can view and correct your account details and usage in the console, and you can ask us to close your account at any time. Depending on where you live, in particular in the EU, UK, or California, you may also have the right to get a copy of your personal data, to have it corrected or deleted, to object to or restrict certain uses of it, and to complain to your data protection authority. Email us and we will handle your request free of charge and without treating you any differently.

Some data cannot be deleted: payment records we must keep by law stay until that obligation ends, and blockchain records cannot be erased by anyone. We will tell you about anything we keep when we handle your request. Everything else is removed.

International transfers

The Service runs on infrastructure in several countries, so your data may be processed outside the country you are in, including in the United States. When we transfer personal data out of the EU or UK, we use appropriate safeguards for the transfer, such as the European Commission's Standard Contractual Clauses.

Children

The Service is not intended for anyone under 18, and we do not knowingly collect their data. If you believe a child has given us personal data, let us know and we will delete it.

Changes

We may update this policy. The date at the top shows the current version, and we will notify you through the Service or by email before a material change takes effect.

Contact

Privacy questions or requests about your data: support@cloakray.com.