Privacy
This site keeps very little about you.
Last checked 18 October 2026
Getting in touch does, because it has to. This page says what arrives, who else can see it, how long it is kept and what you can make us do with it.
01 Who holds it
Teialoom is Daniel Leite, a sole trader in the United Kingdom, working from Liverpool. There is no company behind the name yet, so there is no company number to quote here. When that changes, this page changes with it. Everything below is held by that one person, who is the data controller for it, and the way to reach him about any of it is daniel.leite@teialoom.com.
02 What the site itself does
Very little. No page of teialoom's own sets a cookie, only the client brief stores anything in your browser, the answers you have not sent yet, for 30 minutes at most, and the fonts and the images are served from this domain rather than borrowed, so loading a page tells no third party anything for advertising. Umami counts the visit and notes which of our contact links you press, such as email, WhatsApp or booking a call, without anything that names you. The free site review sends what you typed, and nothing is sent until you press the button. The demo sites under /demo/ show other businesses' designs; some load fonts from Google, and one, the airport demo, has a chat whose messages are answered by Anthropic's AI. The cookie notice says the same thing at more length.
03 What arrives when you get in touch
Six routes in, and no others. The site review form takes your name, your email address and your website address. The client brief, which we send only to people building a site with us, takes whatever you write in it about you and your business. Booking a call opens Calendly, which takes your name, your email address, the slot you picked and anything you type into the box, and the call itself is a video call on the service named in the booking. Email, WhatsApp and phone calls carry whatever you choose to say and the address or number you use. Nothing is inferred, bought or added from anywhere else. What we hold is what you sent.
04 Who else can see it
The client brief goes to Formspree, a company in the United States, which keeps it and emails it to us, so everything you write in the brief leaves the UK; how long we keep it: [to decide]. When you send the brief, Google reCAPTCHA, from a company in the United States, checks that you are a person, which tells Google your internet address and how you use the page. Brevo, a French company, sends the emails that a website review produces, and that mail stays inside the EU. When you ask for a website review, Formspree, a company in the United States, also receives a copy of what you type into the form (your name, email and website address), so that copy leaves the UK. Umami counts visits: the page you looked at, the site that sent you, roughly where you are and which of our contact links you pressed, with no cookie and nothing stored in your browser. Calendly holds every booking, and Calendly is a company in the United States, so a booking leaves the UK the moment it is made; the video call runs on the service the booking names. Anthropic, a US company, answers the chat on the airport demo, and sees what you type there and nothing else. WhatsApp messages sit with WhatsApp, which is Meta. Email sits with the company that runs our mail. Cloudflare serves this site and sees the request that fetched it, which is a server log rather than anything handed to us. Each is a separate company with its own policy, and none of them is sent anything for advertising.
05 If you edit your own site
Clients who change their own site do it in Teialoom CMS, which runs on a server we rent from IONOS in the United Kingdom. Signing in keeps your name and your email address there, and for each sign-in the time, your IP address and the browser you used. The sign-in codes and invitations it emails are sent by Brevo. What you save goes into your site's own files, which are kept on GitHub, a US company, so your text and photographs go to the United States when you save them. Your account is deleted when we stop running your site.
06 Why we are allowed to hold it
An enquiry is held to answer it, which is the step before a contract you asked for. A client’s details are held to build and run their site, which is the contract itself. Invoices and the records behind them are held because tax law requires it. Nothing here rests on consent, which means there is no consent to withdraw, and nothing is used for marketing, so there is no list to come off.
07 How long it is kept
An enquiry that goes nowhere is deleted after twelve months. A client’s working files and correspondence are kept for as long as we run the site, and for a year after it ends in case something is needed back. Invoices and accounting records are kept for six years, which is what HMRC asks of a sole trader and is not ours to shorten.
08 What you can ask for
A copy of everything held about you, a correction, a deletion, or a copy in a form you can take elsewhere. Ask at daniel.leite@teialoom.com and the answer comes inside a month, free. If the answer is unsatisfactory the Information Commissioner’s Office is the UK regulator to complain to; if you are in Portugal you can go to the CNPD instead, and going to either does not stop you asking us again.
09 If this changes
Adding a newsletter would mean changing this page first, and the cookie notice with it. If you are reading this on a version of the site that asked you to accept cookies, or that took anything from you beyond the five routes named above, this page is out of date and that is a bug worth telling us about.
Questions about any of this: daniel.leite@teialoom.com. A reply inside a month, free.