Your data, and how we look after it
Last updated: 8 November 2026
Fox Office holds your team’s tasks, documents, conversations and the business tools you connect. This page answers what buyers ask us before they sign, including the parts that are not finished. If anything here matters to your decision, ask us to show you the evidence: hello@cleverfox-ai.com.
Where your data lives
Who can see it
- Only the people you invite to your workspace can see it.
- Every company's records carry the company they belong to, and two separate layers keep them apart: the app checks who you are and which company you are in on every request, and the database's own rules refuse another company's records even if the app got it wrong.
- We tested the database layer live with a simulated outside account on 19 August 2026, and it saw nothing. A full test of every endpoint by an attacker's method is the remaining step.
- An automated check fails our build if a new endpoint ships without an access check.
- A small number of named people at Cleverfox hold administrator access, for support. Every administrative action and data export is written to an audit log that its own administrators cannot edit.
- Two-step sign-in for administrators is being rolled out. It is not in force yet, and we will say so here when it is.
AI and your data
- We do not train AI models on your data, and we do not use it for profiling or for anything beyond running your service.
- Anthropic, our main AI provider, may not train models on customer content under its commercial terms. We read those terms and confirmed this on 2 November 2026.
- OpenAI's published position is that API content is not used for training by default. We have not finished checking its current terms, so we list it as being verified.
- For OpenRouter, Deepgram, TypeSafe and ElevenLabs we are still verifying each provider's training and retention position. Until a row says confirmed, treat it as unconfirmed.
- AI features only send what the feature needs, and only when you use them. Every call our servers make to an AI provider writes a log row: which provider, which workspace, what happened. It never keeps what was said.
- Outside content that reaches a prompt, such as a transcript or an uploaded document, is marked as evidence, not instructions. Extending that to every fox is in progress.
- AI output can be wrong. Treat it as a draft.
Sub-processors
Every company that can receive customer data, what it receives, where, and whether we have finished checking its terms. “Being verified” means exactly that: until a row says confirmed, do not treat it as confirmed. Integrations under “only when your workspace connects them” receive nothing unless you connect them.
| Provider | What it receives | Where | Our check of its terms |
|---|---|---|---|
| Running the service | |||
| Supabase | All workspace data: records, accounts and uploaded files | London, UK | Being verified Region confirmed (London, eu-west-2), 20 October 2026. DPA: being verified. |
| Vercel | Request traffic and server logs | London, UK (measured and pinned to London, 9 November 2026) | Being verified |
| Backblaze | A full copy of the database, encrypted at rest, each copy locked against deletion for 30 days | Amsterdam, Netherlands (EU) | Being verified |
| AI providers | |||
| Anthropic | What you send to a fox, including documents you share with it | Not yet confirmed | Being verified No training on customer content: confirmed from Anthropic's commercial terms, 2 November 2026. Retention period and DPA: being verified. |
| OpenRouter | Chat input sent to a routed model | Not yet confirmed | Being verified |
| Deepgram | Voice-note audio | Not yet confirmed | Being verified |
| OpenAI | Voice-note audio, when the main transcriber is unavailable | Not yet confirmed | Being verified |
| TypeSafe | Email, chat and lead text to be labelled | Not yet confirmed | Being verified |
| ElevenLabs | Your voice during a voice conversation, and the text spoken back | Not yet confirmed | Being verified |
| Email, payments and messages | |||
| Resend | Recipient address and the email's content | Not yet confirmed | Being verified |
| Stripe | Your company name and monthly price; card details are entered on Stripe's own page | Not yet confirmed | Being verified |
| Smartlead | For Cleverfox's own outreach only, never your workspace's content | Not yet confirmed | Being verified |
| Meta (WhatsApp) and Telegram | The brief's text and the recipient's number or chat id | Not yet confirmed | Being verified |
| GitHub | Build cards, briefs and code; not your workspace's content | Not yet confirmed | Confirmed |
| Only when your workspace connects them | |||
| We read and write the linked account through Google's own APIs | Not yet confirmed | Confirmed | |
| Microsoft | The linked person's own mailbox and Teams messages | Not yet confirmed | Confirmed |
| HubSpot | Contacts, deals, notes and activities | Not yet confirmed | Being verified |
| Xero | Ledger data, supplier bills and contacts | Not yet confirmed | Being verified |
| Slack, Fireflies and Calendly | Nothing new from us: we read what those tools already hold | Not yet confirmed | Confirmed |
| ScreenshotOne | The address of the web page to picture; the picture comes back to us | Not yet confirmed | Being verified |
| Apollo | Search criteria such as industry, job title and location; a person's name and work email come back | Not yet confirmed | Being verified |
| Companies House | Company names and numbers we look up | UK | Confirmed |
| DataForSEO | Keywords and website addresses; no personal data | Not yet confirmed | Being verified |
| Our public website only | |||
| Google, Meta, TikTok, LinkedIn and Microsoft Advertising | A visitor's page events on the public site, in line with their cookie choice | Not yet confirmed | Being verified |
List last updated 12 November 2026. We will email workspace administrators at least 30 days before a new sub-processor starts receiving customer data, so you have time to object. The same list is in our Privacy Policy.
Data Processing Addendum
Under UK GDPR, when Fox Office holds personal data for you, we are your processor and you are the controller. Our Data Processing Addendum sets out the Article 28 terms: what we process and why, our obligations, sub-processors and notice, international transfers, breach notification, and deletion at the end. It is a template under review by our solicitor, and it says so at the top. For a countersigned copy, email hello@cleverfox-ai.com.
Security questionnaire answers
The questions a security questionnaire asks, answered in public: 23 yes, 10 in progress, 5 no, each “no” with what is planned. Read the answers. If your organisation has its own questionnaire, send it to us and we will fill it in from the same answers.
Certifications, and what is in progress
| Security certification | Not yet | We do not hold one yet. We say that plainly rather than show a badge we have not earned. |
| Cyber Essentials | Planned | The UK government-backed scheme. It is the next certification on our roadmap. |
| ISO 27001 | Planned | On the roadmap after Cyber Essentials. |
| Two-step sign-in for administrators | In progress | Being rolled out. Not yet in force. |
| A tested restore from backup | In progress | Backups run every night. The restore-test procedure is written and the first dated test is scheduled. |
| AI providers' data terms | In progress | Anthropic confirmed. The others are being verified. |
| Signed DPAs with our own providers | In progress | Being located, accepted and filed for each provider. |
| Independent penetration test | Not yet | None has been carried out yet. If you need one before you sign, ask us and we will tell you where it stands. |
| Published security fact sheet | In place | Forty checks, each marked in place, in progress or not yet applicable, at /security. |
Reporting a vulnerability
- Email hello@cleverfox-ai.com with SECURITY in the subject line.
- A person replies within 2 business days, and a confirmed finding gets a fix or a plan within 14 days.
- Please give us a reasonable chance to fix it before you tell anyone else, and do not access, change or delete other people's data while you test. We will not take action against anyone who reports in good faith and follows these rules.
- Our security.txt, the standard file security researchers look for, is at /.well-known/security.txt.
Service status
We do not have a status page of our own yet. Until we do, these are the status pages of the two providers Fox Office cannot run without:
- Vercel status (hosting)
- Supabase status (database and sign-in)
More detail
The 40-point security fact sheet for your IT person, how we keep your data safe in plain English, our Privacy Policy and our Terms of Service.