Privacy notice

Your figures are yours. Here's exactly what happens to them.

This covers the website, the software, and any consultancy work. It is written to be read once and understood, rather than to be long enough to look thorough.

Last updated 12 September 2026.

The short version

Five things I commit to, plainly.

These are referenced elsewhere on this site, so here they are in full, and they are binding on me rather than aspirational.

Your data is never pooled with anyone else's.

Your invoices, prices, margins and sales sit against your account and are used to run your account. They are not combined with other businesses' figures to build benchmarks, industry averages, market reports or a training set. Nobody else's numbers are in your account, and yours are not in theirs.

One thing that is shared, so it isn't a surprise later: a library of national merchant patterns — that TESCO PFS is a fuel forecourt and not a supermarket — grows as I work. It contains no names, no amounts, no volumes and nothing identifying about any shop, and the importer refuses any entry that carries them. Your figures are not in it and cannot get into it.
It is never sold. To anyone. For anything.

Not to suppliers, not to delivery platforms, not to data brokers, not to anyone building a market picture of what takeaways pay for chicken. There is no arrangement under which your figures become someone else's product, and there will not be one.
It is never shown to anyone as an example — not even anonymised.

Not in a demo, not in a screenshot, not on this website, not in a pitch, not on social media, and not in a talk. “We'll take the name off it” is not an exception I make: in a trade this small, a menu and a set of margins identifies a shop even without a name on it. Every screenshot on this site uses invented demo data. The only way your figures appear in front of another person is if you have asked me, in writing, to show them.
You can export everything, whenever you want.

All of it, in a format you can actually open and use elsewhere — your ingredients, your costs, your recipes, your margins. You do not need a reason and you do not need to be leaving. Ask at [email protected].
You can have all of it deleted.

Ask and it goes — the invoice images, the extracted lines, the recipes, the figures. Within one month of asking, normally within a few days. The only thing that survives is what the law requires me to keep, which is explained below, and I will tell you exactly what that is at the time rather than leaving you to guess.

Who is responsible for your data

TELVO LTD is the data controller — meaning the company decides what is collected and why, and is accountable for it. It is registered in England and Wales, company number 17447926, registered office 34 Hanafey Way, Northampton, Northamptonshire, NN5 7FX.

It is registered with the Information Commissioner’s Office under registration number ZC243587.

In practice that means me. I'm Mehmet, I run the company, and I am the only person who handles your data — there is no support team and nobody else has access to it.

If a security breach affects your data, you’ll hear from me within 72 hours of my knowing — what happened, and what I’ve done about it.

For anything on this page — a question, an export, a deletion, or a complaint — write to [email protected]. It reaches me directly. There is no ticket queue.

What I collect, and why

If you just read the website

Nothing that identifies you, unless you accept the cookie banner. The site sets no analytics of its own. If you accept, the Meta pixel loads and reports a page view to Meta so I can tell which adverts bring people here; if you reject or ignore it, that never runs. Your choice is stored in your own browser, not on any server of mine. More in the cookie notice.

If you book a call

Bookings run through Calendly, which collects your name, email and whatever you tell me about your business in the booking form, and holds it under its own privacy policy. I use it to prepare for the call and to follow up afterwards. If you would rather not use Calendly, email me and I’ll arrange it directly.

If you use the software

The account itself: your name, email, business name, and billing details. Then the working data — photographs of supplier invoices, the lines read off them, ingredient prices, your recipes and portions, your menu and its prices, your sales and platform figures, your compliance checklists, and the margins calculated from all of it.

And your bank statements, which include payee names — some of those are your staff and your suppliers. They are used only to categorise your costs. No person outside Telvo is shown your figures; the companies whose systems process them are listed below.

This is used to do the three jobs you are paying for: cost the menu, produce the P&L, and run the checks. It is not used for anything else, and the five commitments at the top of this page apply to every part of it.

If your staff use the software

The compliance module holds a record for each of your team: their name, the email or PIN they sign in with, which checks they completed and the time the server recorded it, and the photographs they take of your kitchen for checks that ask for one. Once clock-in ships, it will hold clock-in and clock-out times too.

You are the controller of that data, not me. It is your staff, your kitchen and your records; I process it on your instructions. That also means telling your team it is being collected is your job rather than mine — and it is worth doing properly, because a photograph of a fridge at 10:40 with a name against it is a record about a person.

Photos are kept for twelve months, then deleted. If a member turns on alerts, the app stores that device’s notification token — nothing else about the device — and deletes it when you remove the member from the account.

If I do consultancy work with you

Whatever you send me to do the job — bank statements, platform statements, supplier invoices, sales reports, rotas — plus my own notes from the day on site and the action plan written from them.

Notes taken on site are about how the operation runs. Where they touch individual staff it is about roles, workload and process, not about people's personal lives, and the written plan does not name staff.

The legal bit: why I'm allowed to hold it

UK GDPR requires a lawful basis for each use. Mine are:

Performing our contract: Your account, your working data and your consultancy documents. I cannot cost your menu without your invoices; holding them is how the service exists.
Consent: The Meta pixel. It is something you opt into, and you can withdraw at any time — change your cookie choice. Withdrawing has to be as easy as agreeing was, so it is one click on that page.
Legitimate interests: Replying to you when you get in touch, keeping the service secure, and keeping enough record of who I have worked with to run a business. Nothing here overrides your interests, and if you think it does, say so and I will look at it properly.
Legal obligation: Invoices and payment records I am required to retain for tax. That is the one category I cannot delete on request, and it is my billing records for you — not your operational data.

Who else's systems touch it

“Never shown to anyone” means no person is shown your figures. It does not mean no company's software touches them — the site has to be hosted somewhere and an invoice photograph has to be read by something. Pretending otherwise would make the promise above worth less, not more, so here is the list.

Every one of these is a processor: they act on my instructions, may only use the data to provide their service to me, and may not use it for their own purposes.

Cloudflare: Hosts this website and the software, and runs the database behind it, the storage that holds invoice photographs and compliance photographs, and the login gate. Also sees the standard request information any web server sees.
Anthropic: Reads the lines off photographs of your supplier invoices. Engaged on terms that forbid using your data to train models.
Stripe: Handles subscription billing. Card details go to them and never to me — I see that a payment succeeded, not your card number.
Resend: Sends the email the software has to send: password resets, invitations to your team, and alerts. Hosted in Ireland.
Google Workspace: The mailbox behind [email protected], so anything you write to me sits there.
Calendly: Handles call bookings and holds what you enter in the booking form.
Meta: Receives a page view if — and only if — you accept the cookie banner. Meta uses that for advertising measurement under its own terms, which is exactly why it is behind a consent gate rather than switched on by default.

Some of these are outside the UK. Where that happens, the transfer is covered by the safeguards UK data protection law requires — the UK adequacy regulations, or the UK International Data Transfer Agreement or Addendum.

How long I keep it

Your account and working data: For as long as you are a customer, because it is what the service runs on. If you close your account it is deleted — you do not have to ask separately, though you can ask for it sooner at any point.
Consultancy documents: The statements and invoices you send for a job are deleted once the work is finished and the plan is delivered, unless you ask me to hold them for follow-on work. I keep my own copy of the action plan, because it is my work product and you may come back to it.
Backups: Backups lag behind the live service by design, because a backup you can amend on request is not a backup. If you ask for deletion, it leaves the live records straight away and is gone from backups within 30 days.
Billing records: Kept as long as tax law requires, which is currently six years. This is the invoice I raised to you — it is not your operational data, and it is the only thing a deletion request cannot reach.

What you can make me do

Under UK data protection law you have the right to ask for a copy of what I hold, to have it corrected, to have it deleted, to restrict or object to how it is used, to take it elsewhere in a portable format, and to withdraw consent where consent is the basis.

Email [email protected]. There is no form to fill in and no charge. The law gives me a month; it does not normally take anywhere near that. If I need to check you are who you say you are before handing over data, I will ask for the minimum that settles it.

If you are not happy with how I have handled it, you can complain to the Information Commissioner's Office at ico.org.uk. I would rather you came to me first so I can fix it, but that route is yours regardless and I am not going to pretend otherwise.

If this changes

The date at the top moves and the current version always lives here. If a change actually affects how your data is used — rather than fixing a typo — customers get told directly by email. You will not find out that something material changed by re-reading this page and spotting a different date.

Questions about any of it: [email protected].