Privacy policy

A business plan is a personal document. It usually contains your turnover, what you pay your staff, what your household needs to live on and where you live. This page says what happens to it, in the detail that deserves.

The controller is Tele UK Ltd, registered in England and Wales under company number 10519543, at 45 Ben Jonson Road, London E1 4SA, United Kingdom. For anything on this page, write to [email protected] or telephone +44 7440 453631.

1. You can use this without giving us anything

Without an account, the whole product runs in your browser. Your plan is written to that browser’s local storage and is never sent to us. We do not know you were here: there is no analytics script, no advertising pixel, no session recorder and no telemetry, on the website or in the app.

The trade is yours to make and it goes both ways — nothing leaves, and nothing is backed up. If you clear your browser data, the plan goes with it.

2. What we hold when you do make an account

We do not ask for your date of birth, your phone number or your address as account fields. If you type an address into your business plan — many people put the trading address, and sole traders often put their home — it is part of the plan and treated like the rest of it.

We do not knowingly hold special category data (health, beliefs, biometrics and the rest). Please do not put it in a plan.

3. Why we are allowed to hold it

• Performance of a contract (UK/EU GDPR Art. 6(1)(b)) — your account, your plans and the sessions that let you reach them. Without these there is no service.
• Legitimate interests (Art. 6(1)(f)) — keeping the service secure and working: lockouts after failed sign-ins, activity records, server logs. Our interest is in running a service that is not broken into; the processing is limited to what that needs.
• Legal obligation (Art. 6(1)(c)) — records we have to keep, including of administrative access to personal data, and anything a court or regulator lawfully requires.

We do not rely on consent for any of this, which is why there is no consent banner. We also do not use your data for marketing unless you ask us to, and we never sell it.

4. The AI writing, and your own API key

AI drafting is optional and switched off until you turn it on. It uses an API key from your account with an AI provider. That key is stored in your browser’s local storage and is never sent to our server — we cannot read it, use it, lose it or be made to hand it over.

When you ask for a draft, your browser sends that provider the material the draft needs: your worksheet answers for the section, your interview answers, and a fact sheet of figures the engine has already computed. That request goes from your browser to them directly, under their terms and their privacy policy, not ours. If you have configured a gateway or a self-hosted endpoint, it goes there instead.

We are not a party to that exchange and do not keep a copy of it. If you would rather no part of your plan ever reached an AI provider, do not turn the feature on: every section can be written by the offline composer instead.

5. Who else touches it

We keep this list short on purpose, and it is the complete list.

Where a provider is outside the UK or EEA, transfers rely on adequacy regulations or standard contractual clauses with appropriate safeguards.

We will disclose data to a court, regulator or law enforcement where we are lawfully required to. Where we are permitted to tell you, we will.

6. When a human here can see your plan

Rarely, deliberately, and never silently. Ordinary administration screens show accounts, workspaces and how many plans exist — not what is inside them. That is enforced by the database rather than by a rule somebody has to remember.

Reading the content of a plan is a separate action available only to the highest level of administrator, and it requires a written reason. The record — who, their standing at that moment, the plan, and the reason — is written before the access happens, so an attempt that fails halfway is recorded too. That log is append-only: through the application there is no way to read, change or delete it.

The reasons this exists at all are the ones the law requires: answering your own request for a copy of your data, performing an erasure, investigating abuse, or responding to a court or regulator. A platform where nobody can ever reach the data cannot meet those duties.

7. Your rights, and how to use them

Under UK and EU GDPR — and, in substance, under the California privacy laws and most other modern regimes — you can ask for:

• A copy of everything we hold about you (Art. 15).
• Correction of anything wrong (Art. 16).
• Erasure of your account and its plans (Art. 17).
• A portable copy in a machine-readable format (Art. 20).
• Restriction or objection to processing (Arts. 18 and 21).

You do not need to ask us for a portable copy: every plan exports itself as PDF, CSV and JSON from inside the app, at any time, on every tier including the free one.

For the rest, write to [email protected]. We will respond within one month. There is no charge unless a request is manifestly unfounded or excessive.

If you are unhappy with how we have handled it, you can complain to the UK Information Commissioner’s Office at ico.org.uk, or to your own supervisory authority in the EEA. We would rather you told us first.

8. What erasure actually removes

It destroys the account, the workspaces it owns, and the plans in them. That is the substance of what we hold about you and it is genuinely deleted, not flagged as hidden.

The administrative access records are kept. They exist to show that people’s data was handled properly — including the record of your erasure being carried out — and deleting them would destroy the evidence that the erasure happened correctly. They identify actions and account identifiers, not the contents of your plan.

Backups are overwritten on their own cycle rather than edited, so a copy may persist in a backup for a short period after deletion. It is not restored into the live service except in a disaster, and the deletion is reapplied if it is.

9. How it is protected

In summary: plans are isolated by the database itself rather than by application code; passwords are hashed with bcrypt and compared inside the database, so no hash ever reaches the application; session tokens are stored only as a hash and can be revoked; and administrative access is logged before it happens.

The detail, including an honest list of what is not done yet, is on the security page.

If a breach puts your rights at risk, we will tell the ICO within 72 hours as required, and tell you without undue delay where the risk to you is high.

10. Children

This is a tool for running a business and is not directed at children. We do not knowingly hold data about anyone under 16. If you believe we have, write to us and it will be removed.

11. Changes to this policy

When it changes, the date at the top changes with it. If a change materially affects your rights or what we do with your data, we will email account holders rather than relying on you noticing.