Privacy notice

Last updated 12 November 2026

What personal data nclave holds, why, who else is involved, and your rights over it. If anything here is unclear, email us at hello@nclave.co.uk.

Who we are

nclave is run by The Swing Suite Ltd, which is the controller of the personal data described here.

Run by
The Swing Suite Ltd
Registered office
74 Elmfield Way, Sanderstead, Surrey, CR2 0EF, United Kingdom
Company number
12218989 (registered in England and Wales)
ICO registration
ZC263484
Email
hello@nclave.co.uk

The short version

  • Your assistant runs on its own, in a separate container on our server in the UK, and never shares memory, files or connections with anyone else's.
  • We use your data to run your assistant and your account. We do not sell it, use it for advertising, or use it to train AI models.
  • The AI model your assistant uses sees what it needs to answer you. On the Own AI key plan that is your own provider, under your account with them; on the AI included plan it is OpenRouter and the model's maker, working for us.
  • To sort your email quickly and cheaply, your assistant also asks a small decision model about short extracts (who a message is from, its subject and first lines). That model is run for us by TypeSafe AI and Cloudflare, possibly outside the UK, and neither keeps what it is sent.
  • When your assistant searches the web or reads a web page for you, the search or the page's address goes to Firecrawl, in the United States, which runs it for us.
  • When you cancel, everything is kept for 30 days in case you come back, then deleted.

What we hold, and why

Your account. Your email address, the name you give at checkout, your plan and the state of your subscription: to run your account and bill you (our contract with you). Your card details are collected and held by Stripe; we never see them. We may also email you short notes about new features of the service, and send them as a Telegram message from your assistant's bot if you use Telegram; you can turn these off on your What's new page.

What you set up. On the Own AI key plan, your AI provider key; on the AI included plan, the key we create for your assistant. If you add Telegram, your Telegram bot's token and name, and your Telegram user and chat IDs, so that your assistant talks to you and only you there. Keys, tokens and passwords are stored encrypted. If you fill in the optional "About you" questions when building your assistant, we keep your answers and put them in your assistant's memory so it knows you from the first chat (contract).

Creating your bot in Telegram. If you add Telegram with one tap, our nclave bot sees your Telegram name and user ID and creates your bot on your behalf. You own that bot, and our nclave bot can fetch or replace its token: we do that only to connect the bot to your assistant and to keep it working if the token changes. Your conversations go to your assistant, not to our nclave bot (contract).

Keys you give your assistant. If you add an API key or token for another service, through the secure form your assistant offers (a card in the app, or a button in Telegram) or on your dashboard, it goes straight into your assistant's own private settings and is never shown in your chat. We keep only its name and when you added it, so you can see and remove your keys. It is deleted with your assistant (contract).

Accounts you connect. If you connect Google, Microsoft or another mailbox: that account's address and the access it grants (tokens, or the mailbox password), stored encrypted. Your assistant uses them to read, draft and act on your email, calendar, contacts and files when you ask it to. You can disconnect any of them at any time (contract).

FreeAgent, if you connect it. The name of your company in FreeAgent, your FreeAgent access level and the access FreeAgent grants (tokens), stored encrypted. Your assistant reads your invoices, bills, bank transactions and reports to answer your questions, can check for invoices that have been paid so it can tell you, and creates a draft invoice or adds a new client only when you approve it. What it reads becomes part of your conversation with it, which it keeps as described below. Where we have switched on sending invoices from the nclave app for you, we hold your FreeAgent access instead of your assistant: what it reads passes through our server on its way to your assistant and is not kept there, and an invoice is emailed only when you tap Send on a card in the nclave app. For each such email we keep who it went to, its subject and message, the invoice's number and total, and when and from which of your devices you sent it, for 90 days. FreeAgent gives a connected app the same access as your own FreeAgent login, so the limits on what your assistant does with it are ours. You can disconnect at any time (contract).

What your assistant keeps. Your conversations with it, what it remembers about you and the way you work, its notes, files you send it or ask it to fetch, and, if you use it for shopping, a log of what it suggested and what you ordered (shop, price, order reference, delivery and return dates), all held in your assistant's own storage on our server (contract). You pay shops yourself, so your assistant never handles your payment details, and its shopping log does not keep your address.

The nclave app. The devices you link to your assistant (the name you give each one, when it was linked and last seen, and whether it can still be used) and any add-on requests you send us with our replies, to run the app and answer you (contract). What you write, and the photos, documents and locations you send in the app, are encrypted on your device and can be read only by your assistant's app connection on our server, which keeps your app conversations in your assistant's own storage. The relay that carries the app's traffic, and anyone watching the network, cannot read it. Each device keeps its own key, which never leaves it, and a copy of your conversations, until you remove the app from it.

Your address book. Details of other people that you give your assistant or import from Google or Microsoft (names, email addresses, phone numbers, addresses, birthdays and any notes you ask it to keep), held in your assistant's address book so it can reach the right person. You can ask your assistant to export or delete them at any time.

Running the service. Health and error logs for your assistant, a record of changes to your account (such as a plan change or a new connection), and technical data such as IP addresses in our web server's logs: to keep the service working and secure (our legitimate interests).

Billing records. Invoices and payment records, which the law requires us to keep (legal obligation).

Your assistant and AI models

To answer you, your assistant sends the text it is working on to an AI model: your message, and whatever it has looked up for it, such as an email or a calendar entry. The model sends back a reply.

  • Own AI key. The model is run by the provider you chose (OpenRouter, Anthropic or OpenAI) under your own account with them. Their terms and privacy policy govern that account.
  • AI included. We send it through OpenRouter, Inc. (United States) to the companies that run the model for us: currently OpenAI, Microsoft or Amazon for GPT-6 Luna. They act for us, under contract. Our OpenRouter account only uses providers that do not train models on what they are sent, and none based in China.

Quick decisions. On both plans, when your assistant sorts or watches your email it sends a short extract of each message (sender, subject and first lines, never attachments) to Jev, a decision model made by TypeSafe AI, Inc. (United States) and run on Cloudflare's network, which may process it outside the UK. Jev does not write anything: it returns labels and scores, such as how urgent a message looks, and your assistant uses them to decide what to show you first and whether to tell you about a new email. Neither company keeps the extracts or uses them to train models.

Web search. On both plans, when your assistant searches the web or reads a web page for you, it sends the search words or the page's address, through our Cloudflare service, to Firecrawl (SideGuide Technologies, Inc., United States). Firecrawl runs the search or fetches the page and sends back the results. It never receives your messages, only what your assistant looks up.

In the nclave app, your messages to and from your assistant are encrypted between your device and your assistant. If you add Telegram, your messages there travel through Telegram, which you use under your own Telegram account and Telegram's privacy policy. The app's notifications reach you through your device's own push service (Apple, Google, Mozilla or Microsoft), encrypted so that the service cannot read them. Voice notes you send in the app are turned into text by your assistant on its own server in the UK, and the recording goes to no one else. If you dictate with your keyboard's microphone key instead, your phone's maker may process the audio, as in any app. When you tap Read aloud, your assistant turns that reply into speech on the same server, or your device reads it with its own voice, and the text goes to no one else. When you tap Share location in the app, your device's location at that moment goes to your assistant with that message, and from there to the AI model like the message's text; it stays in your conversation history. The app never reads your location at any other time or in the background. We make no automated decisions about you that have legal or similarly significant effects.

When you read a QR code or barcode in the app, it is read on your device, and goes to your assistant only if you tap Send to assistant; then, like the message's text, it goes to the AI model and stays in your conversation history. Photos, scanned pages and documents you send go to the AI model with your message. On Android, the app's document and code scanners are Google's, running in Google Play services on your phone. Google receives information about how the scanners perform and are used, under its own terms, but not the pages or codes themselves.

Who else is involved

These companies process personal data for us, under contract, and only to provide their part of the service:

  • Hostinger: hosts our server, in the UK (Manchester).
  • Stripe: payments and invoices (Ireland and the United States).
  • Resend: sends sign-in links and service emails (United States).
  • Cloudflare: our domain's DNS; storage for our backups, which are encrypted before they leave our server so Cloudflare cannot read them, and are kept in the EU; and running the quick decisions model and passing web searches to Firecrawl (United States, with processing wherever its network runs the request).
  • TypeSafe AI: the quick decisions model, on both plans (United States).
  • Firecrawl: web search and reading web pages for your assistant, on both plans (United States).
  • OpenRouter and the model's maker, on the AI included plan only (United States).

Google, Microsoft, FreeAgent, your email provider, Telegram if you add it and, on the Own AI key plan, your AI provider are services you use under your own accounts; each is responsible for its own handling of your data. We never sell your data. We will disclose it where the law requires us to.

Transfers outside the UK

Your assistant and its data are stored in the UK, and our encrypted backups of them in the EU, which the UK recognises as giving adequate protection. Some of the companies above are in the United States. When personal data goes to them we rely on the UK's adequacy regulations (the UK Extension to the EU-US Data Privacy Framework, for companies certified under it) or on the International Data Transfer Agreement or Addendum issued by the Information Commissioner.

Google user data

nclave's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

  • We use Google data only to provide the assistant features you ask for.
  • We do not use it for advertising, and we do not sell it.
  • We do not use it to develop, improve or train AI models.
  • Nobody at nclave reads it, unless you ask us to for support, it is needed for security, or the law requires it.

How long we keep it

  • For as long as you subscribe.
  • After you cancel, for 30 days, so you can come back and pick up where you left off. Then your assistant and all of its storage are deleted, and so are our copies of your keys, tokens and connection details.
  • Backups are encrypted and deleted after 30 days, so a copy can outlast a deletion by up to 30 days.
  • Your email address, plan and subscription history and your invoices are kept for six years, for tax and accounting.
  • Disconnecting an account removes its access from your assistant and from our records straight away.

Security

  • Keys, tokens and passwords are encrypted at rest.
  • Each assistant runs in its own container with no ports open to the internet, and cannot reach any other customer's assistant.
  • Our server can only be administered over a private network, and every connection to the site uses HTTPS.

No system is perfectly secure. If a breach affects your data we will tell you, and the Information Commissioner, as the law requires.

Your rights

You can ask for a copy of your data, have it corrected or deleted, restrict or object to how we use it, and have it given to you in a portable form. You can disconnect any account you have connected at any time. Email hello@nclave.co.uk; we will reply within one month.

You can also complain to the Information Commissioner's Office (ico.org.uk/make-a-complaint, 0303 123 1113), though we would appreciate the chance to put things right first.

Cookies

We use only the cookies needed to keep you signed in and to protect signing in against forgery: no analytics, no advertising, no tracking. Stripe sets its own cookies on its checkout pages.

Children

nclave is for adults. We do not knowingly provide it to anyone under 18.

Changes to this notice

If we change this notice in a way that matters, we will email subscribers before the change takes effect. The date at the top shows the current version. See also our terms.