No-Logs Policy
Last updated: 18 October 2026
unrestricted.sh does not save or log what you send to the models or what they send back. This page says exactly what that covers, what we do keep, and the law that holds us to it.
The promise
- We never write your prompts, the model's replies, or the tool calls and results inside them to disk or to a log.
- That holds at every step a request takes: our app servers and the GPU servers that run the models.
- We never use prompts or replies to train models, and we never sell or share them. We do not have them.
What happens to a request
- Your request reaches our app in Frankfurt through Cloudflare's network. The app checks your API key and balance, counts the tokens, and passes the request on to a GPU server.
- The GPU server generates the reply and streams it back through the app to you. Nothing is written to disk on the way.
- To answer follow-up requests faster, the GPU server keeps recent context in its memory until newer requests replace it or the server shuts down. It is never written to disk and is not linked to your account.
- When the reply is finished, the app writes one usage record, described below. The prompt and the reply are gone.
The playground chat works the same way. If you turn chat history on, your conversations are stored in your browser, encrypted with a key tied to your account. They are never sent to our servers.
What we do keep
Each request leaves one usage record, so we can bill you and show you your usage:
| Field | What it holds |
|---|---|
| Model | Which model answered |
| Tokens | How many input, cached and output tokens |
| Cost | What the request cost |
| Time | When it happened and how long it took |
| Result | The status code, such as 200 |
| API key | Which of your keys was used, never the key itself |
| Prompt | Not stored |
| Reply | Not stored |
When something goes wrong, such as a GPU error or a retry, our servers write a short operational log line. It holds your account id, the API key id, the request path, status codes, token counts and timings. It never holds prompt or reply text.
Our hosting and network providers keep technical logs, such as IP addresses and request paths, for a short period to operate and secure the service.
Outside of requests, we keep what we need to run your account and bill you: your email address, sign-in records and payments. The Privacy Policy lists all of it, why we keep it, and for how long.
What our team can see
Our administrators can see account details, balances, payments and usage records, to give support and stop abuse. They cannot see your prompts, the replies or your chat history, because we do not have them. Every administrative action is logged.
If someone asks for your data
We can only hand over what we have: account, billing and usage records. We do so only when Danish or EU law requires it. Prompts and replies cannot be handed over, because they are never stored.
Who we are
unrestricted.sh is run by a Danish company. The Privacy Policy names the company responsible for your data and how to reach it.
Your data is protected by EU privacy law: the General Data Protection Regulation (GDPR) and the Danish Data Protection Act. Because we are established in the EU, the GDPR covers everything we do with your data, wherever you live.
The app runs in Frankfurt and the database in Germany. The models run on GPUs in Slovenia, Iceland, Norway and Sweden. Some of our providers are US companies. The Privacy Policy names every provider and how each transfer is protected.
Changes to this policy
We will post any change here and update the date at the top. If a change ever weakens this policy, we will email you before it takes effect.
Questions about this policy: support@unrestricted.sh.