Privacy Policy
In force from 3 November 2026
This policy explains what personal data we collect when you use OneHot, why we use it, how long we keep it, who else handles it, and the rights you have. It covers the console at console.sqwish.ai, the API at api.sqwish.ai, the SDKs, the MCP server, the playground and the documentation.
1. Who we are
OneHot is run by Sqwish Ltd, trading as Sqwish Labs ("we" or "us"), a company registered in England and Wales with number 16078346, whose registered office is 20 Station Road, Cambridge, England, CB1 2JD. We are the controller of the personal data this policy describes.
Write to [email protected] (or [email protected]) with any question about this policy or your data. If you are in the European Union, you can also contact our representative there at [email protected].
2. What we collect and why
Below is what we collect in each situation, why, and the legal basis we rely on under UK and EU data protection law. "Contract" means we need the data to provide what you asked for. "Legitimate interests" means we use it for a reasonable purpose of ours that doesn't override your interests, and you can object to it (see your rights).
- Signing inYour email address and an account identifier from our sign-in provider. If you are an administrator, your authenticator. We don't keep sign-in codes ourselves. Our sign-in provider holds each one, in hashed form, until it is used or expires.
- Why
- To create your account and sign you in (contract), and to keep accounts secure (legitimate interests).
- Joining the waitlistYour place in line, and anything you write when you apply for early access.
- Why
- To admit people fairly and understand what they want to build (legitimate interests).
- ReferralsYour referral code, who referred you and whom you referred.
- Why
- To run the referral programme (contract) and to stop people referring themselves (legitimate interests).
- Buying creditYour purchases, credit, invoices and receipts, the email address used for payment, your billing name and address and any VAT or tax number you give, which we need to work out tax and make invoices, and your saved card's brand, last four digits and expiry date. Our payment provider holds your billing details and full card details, not us.
- Why
- To take payments and run your credit (contract), and to keep accounting records (legal obligation).
- Using the API and consoleA record of each request: its identifiers, time, endpoint, models, tokens, charge, timings and outcome or error, and the country it came from, derived from its IP address. The record doesn't keep the address. It contains no prompts and no answers. API keys are kept only as fingerprints.
- Why
- To bill you and show your usage (contract), and to keep the service secure, reliable and improving, such as running servers near where requests come from (legitimate interests).
- Keeping OneHot secureIP addresses in rate limits, blocks, security records and server logs. Cloudflare's check, when you first open OneHot, that you're a person and not a bot. A hashed form of your email inbox address (a pseudonym, which is still personal data), so that starter benefits are given once per inbox.
- Why
- To protect OneHot and its users from abuse and fraud (legitimate interests).
- Trying the playground without an accountWhat you type, to return an answer. We don't keep it after we return the answer. We keep your IP address (for IPv6, only its network part), the country and network it comes from, and how many requests you made each day and in which hours, to apply limits, prevent abuse and understand how the playground is used, for up to 90 days.
- Why
- To give you the result you asked for, and to prevent abuse (legitimate interests).
- Using "Try it" in the documentationThe request you send, including any API key you enter, which passes through the documentation host's proxy.
- Why
- To run the request you made (legitimate interests).
- Contacting usYour messages and the details in them.
- Why
- To answer you (contract or legitimate interests).
- When something failsTechnical error reports. We configure error reporting to leave out request content and to remove personal data before reports leave our servers.
- Why
- To find and fix faults (legitimate interests).
We also use personal data where we need to meet a legal obligation, or to establish, exercise or defend legal claims.
3. Content you send as a customer
When you use OneHot, the content you send, such as contexts, questions, decisions and datasets, may include personal data about other people. We process that content for you, on your instructions, as your processor under our Data Processing Addendum. You decide what it contains and are responsible for telling the people concerned. If your data is in a customer's content, please contact that customer.
We don't use content you send to train models we offer to anyone else, and we don't sell it. We use it to serve you, and to train models that only your account can use.
4. Automated checks
We don't make decisions about you based solely on automated processing that have legal or similarly significant effects on you. Some checks are automatic, such as rate limits, blocking addresses that send abusive traffic, and deciding whether an email inbox has already had starter benefits. If you think one of these got it wrong, write to us and a person will review it.
5. Who else handles it
We don't sell personal data, and we don't share it for advertising. We share it only with:
- the providers that run parts of OneHot for us under contract, which our Subprocessors page lists;
- Stripe, which processes payments and also uses payment data for its own fraud prevention and legal compliance, under its own privacy policy;
- professional advisers, such as lawyers and accountants, under a duty of confidentiality;
- authorities, courts or others where the law requires it, or where we need to protect people's rights, safety or property;
- a buyer or successor if our business, or part of it, is sold or reorganised, who must then protect it as this policy describes.
If you were referred, the person who referred you sees how many people joined through their link and how many rewards they earned, but not who those people are.
6. Transfers outside the UK
We are based in the United Kingdom. Some providers handle personal data elsewhere, as the Subprocessors page shows. Where the UK has decided that a country protects personal data adequately, as it has for the European Economic Area and Switzerland, we rely on that. For organisations in the United States, we rely on the UK Extension to the EU-US Data Privacy Framework where they are certified under it, and otherwise on the UK's International Data Transfer Agreement or Addendum to the EU's standard contractual clauses. Personal data that comes to us from the EU relies on the EU's adequacy decision for the United Kingdom. You can ask us for a copy of the safeguards we use.
7. How long we keep it
| What | How long |
|---|---|
| The content of a decision | Discarded once the answer is returned. For a request sent with an idempotency key, an encrypted copy of the answer is kept for 24 hours, so a retried request with the same key returns the same answer without running or charging twice. A request sent without a key keeps no copy. Nor does a request of an organisation with zero data retention, once it has taken effect. |
| Datasets and labels | Until you delete them or your account closes, then for up to 90 days. |
| Fine-tuned models | Until you delete them. A deleted model's trained files are deleted within 90 days, and its record within 90 days of your account closing, apart from what our payment records need. A model that fails its gate is kept, with its files, until your account closes. So is a model that a rollback of its family discards, unless you delete the family, which deletes every model of it. Deleting a dataset doesn't delete the models trained on it. |
| Evaluations and prompt-tuning jobs | Until your account closes, then for up to 90 days, apart from what our payment records need. |
| Copies of a fine-tuned model on the GPUs that serve it | While the machine has room, and no later than 90 days after your account closes. The copies used least recently are deleted first. |
| Working files on the GPUs that train a model | Up to 7 days after training ends. |
| Account details, early-access answers and settings | While your account is open, then deleted or anonymised within 90 days of it closing, apart from the records below. |
| Inactive accounts | If an account has had no sign-in and no API use for 24 months, we email you. If you don't sign in or use the API within 30 days, we close it and delete its data as above. |
| Waitlist applications | If we haven't admitted you within 12 months of applying, we tell you and remove your application, unless your account holds credit that hasn't expired. We remove it sooner if you ask. |
| The hashed form of your inbox address | 12 months after your account closes, then deleted. |
| Payment, credit and invoice records | 6 years after the end of the financial year they belong to, as UK tax and accounting law requires. Records of sales we declare under the EU's VAT One Stop Shop, which covers customers in the EU without a VAT number, are kept for 10 years after the end of the year of the sale, as EU VAT law requires. |
| Usage records: the request log, which has no prompts or answers | 24 months after the request, so we can resolve billing questions and disputes. The console shows the last 90 days. After that, the billing details of a paid request are kept as payment records. |
| IP addresses in rate limits and blocks | Rate limits keep them for up to 65 minutes. A block lasts from 15 minutes to 24 hours, and we keep its record for 30 days after it ends, so a repeat block lasts longer. |
| Security records and server logs | Up to 90 days, or longer only while we investigate a specific incident. |
| The audit log of administrative actions, policy changes and blocks, which can include IP addresses | 6 years. |
| Error reports | Up to 90 days. |
| Sign-in events held by our sign-in provider | Up to 90 days. |
| What our providers keep | Our providers may keep what we send them for a short time under their own terms. For example, Microsoft may keep the prompts and responses of prompt tuning for a limited time to detect abuse. |
| Messages you send us | Up to 24 months after your request is resolved. |
| Backups | Encrypted, and used only to recover the service: hourly copies for 2 days, daily copies for 30 days and monthly copies for 12 months. Deleted data can stay in a backup until it expires. If we ever restore one, we delete again what had been deleted. |
8. Security
We protect personal data with measures that suit the risk: encryption in transit, encrypted storage of the answers kept for retries and of backups, keys and session tokens stored only as fingerprints, an authenticator for administrators, access limited to those who need it, and records of administrative actions. The Data Processing Addendum describes these measures in more detail. No system is perfectly secure, and if a breach puts you at high risk, we will tell you.
9. Your rights
You can ask us to give you a copy of your personal data, correct it, delete it, limit how we use it, or send it to you or someone else in a portable form. You can object to our use of it where we rely on legitimate interests, and you can withdraw any consent you gave. Some rights have limits, for example where we must keep records by law.
You can download a copy of your data, and delete your account, yourself in the console's Account settings. To use a right, write to [email protected]. We may need to confirm who you are. We reply within one month, or tell you within that month if we need longer for a complex request. There is normally no charge.
If you're unhappy with how we handle your data, please tell us first at [email protected]. We acknowledge every complaint within 30 days and look into it without undue delay. You can also complain to the UK's data protection regulator, the ICO, at ico.org.uk, or, if you are in the EU, to the data protection authority where you live or work.
10. If you live in the United States
Some US state laws give you rights over your personal information. In the last 12 months we have collected the categories this policy describes: identifiers such as your email address and IP address, commercial information such as purchases, internet activity such as how you use OneHot, and approximate location derived from your IP address. We use them only for the purposes in section 2. We don't sell your personal information or share it for cross-context behavioural advertising, and we don't use sensitive personal information to infer characteristics about you. Where those laws apply, you can ask to know, correct or delete your personal information, and to appeal if we refuse. We won't treat you differently for using these rights. Write to [email protected], or ask someone you authorise to write for you.
11. Cookies and browser storage
We use only what OneHot needs to work, to stay secure and to remember your choices. These are strictly necessary for the service you use, so we don't ask for consent to them. We use no advertising cookies.
| Name | What it does | How long |
|---|---|---|
__Host-onehot_session, __Host-onehot_access, __Host-onehot_refresh | Keep you signed in. HTTP-only cookies that your browser's scripts can't read. | Up to 30 days |
__Host-onehot_csrf | Protects your browser's requests from being forged by other sites. | Up to 30 days |
sqwish-theme, onehot-sidebar and onehot-menu-pins | Remember your light or dark theme, whether the sidebar is collapsed and the pages you pinned in it. Local storage. | Until you clear your browser's storage |
onehot:pending-checkout | Remembers a purchase you started, so you can come back to it. Session storage. | Until you close the tab |
cf_clearance | Set by Cloudflare when your browser passes its check that you're a person, not a bot, so it doesn't ask again. | Up to a year |
Our documentation is hosted by Mintlify, with its visitor analytics turned off.
12. Emails
We email you about your account, your credit and your work, such as sign-in codes, your admission from the waitlist, low or expiring credit, a paused automatic top-up, and changes to your access, kept-warm models or datasets. We or our payment provider email your receipts. You can switch off reminders of low or expiring credit, and updates on models that pass their gate, on your Account page or with the unsubscribe link at the foot of each such email, but not the other emails while your account is open. We send news and offers only if you agree to them, and every such email lets you unsubscribe.
13. Children
OneHot isn't for anyone under 18, and we don't knowingly collect their personal data. If you think a child has given us personal data, write to us and we will delete it.
14. Changes to this policy
We update this policy when what we do changes. We'll email account holders before a change that affects them materially. The date at the top shows when this version took effect.