Privacy notice
Version 1.0. In force from 22 November 2026.
This notice explains what personal data we hold, why, where, for how long, and your rights. It covers this website, the Tyndall Air app, and emails to and from us.
1. Who we are
Tyndall Air is provided by Autaimate, the trading name of Michael Stevenson, a sole trader. We are registered with the Information Commissioner's Office (ICO) as a data controller, number ZC115961.
- Email: hello@tyndallair.co.uk
- Postal address: The Bristol Office, 2nd Floor, 5 High Street, Westbury-on-Trym, Bristol, BS9 3BY
There is no separate data protection officer: Michael Stevenson deals with every question about personal data himself.
2. Two roles
For a firm's records we are a processor. Workshops and tester firms use Tyndall Air to keep their own records: their register, checks, photos, defects, documents, test reports and who did each. The firm decides what goes in and why, so the firm is the controller, and we process that data only on its instructions, under our Data Processing Agreement. If your question is about a firm's records, such as a check with your name on it, please ask that firm first. If you write to us, we will pass your request to the firm and help it answer.
For everything else in this notice we are the controller: this website, emails to us, signing in, keeping Tyndall Air secure, invitations we send ourselves, and billing.
3. This website
This website sets no cookies, runs no analytics and loads nothing from anyone else: every page, font and image comes from this address. We keep no record of your visit.
The site is served by Cloudflare. As with any website, your browser sends your IP address and browser details with each request, and Cloudflare uses them to deliver the page and to protect the site from attacks, under its agreement with us. The legal basis is our legitimate interest in running a website that is safe to visit.
4. Emailing us
Email to hello@tyndallair.co.uk passes through Cloudflare's email routing, which forwards it to our own address and on to a Google Gmail account, where it is kept. Google holds Gmail in the United States and elsewhere, under Google's own terms and privacy policy, not under a data processing agreement with us; your message is protected in transfer as Google's terms set out. We use what you send to answer you, on the basis of our legitimate interest in answering the people who write to us, or, if you are asking about using Tyndall Air, to take steps towards a contract you have asked about. We delete enquiries 2 years after the last message, unless they become part of a customer's billing records (section 9) or of a complaint or claim.
Post sent to our postal address is received by our address provider, Duport, which scans business post and emails it to us.
5. Signing in to Tyndall Air
To sign in, a person needs an account with our sign-in provider, Clerk: their name and email address, and a one-time code sent to that address each time. Clerk holds these in the United States, with the details of each sign-in (such as the device and IP address used), for as long as the account exists. A person who belongs to no firm may ask us to delete their account, and we will do so within 30 days. Without a name and an email address a person cannot use Tyndall Air. For sign-in, Tyndall Air itself keeps Clerk's id for the person, their role in each firm, and a copy of their name, which stays on the records they made after they leave a firm (records are evidence). It does not keep members' email addresses: Clerk holds them. When a firm's owner downloads the firm's records, each current member's verified email address is read from Clerk at that moment and put in the download, and not kept by us; nobody's address is read once they have left the firm.
To keep sign-ins secure we record, for each sign-in, when it was first and last used, to the minute, against the sign-in's own id and nothing else about the person. A sign-in ends after 8 hours without use and after 7 days at most. Each record is deleted 8 days after the sign-in was last used.
When someone starts a firm, they accept our Terms of Service for it, and we record that they did: the firm, which of its owners accepted, the version of the Terms and the time. It is the record of our agreement with the firm. We keep it because we have a legitimate interest in being able to show what was agreed with the firm, by whom and when; where the firm is the person themselves, as a sole trader, we keep it because it is part of our contract with them. We keep it for as long as the firm's records are kept, and delete it with them, unless the firm asks us to delete its records sooner: then we keep it with the record of that request, as below.
When a firm asks us to delete its records (our Data Processing Agreement, section 9), we keep a record of the request: the firm's name and kind, which of its owners asked and from which sign-in (or our note of how we checked a request made by email), when it was asked, and whether it was cancelled or carried out and when; if it was carried out, the firm's Terms record above and the number of records deleted, by kind. To email the firm's owners about the request, we hold their Clerk ids with it until each has been told that it ended or was carried out. We keep the record because we have a legitimate interest in being able to show what the firm asked and what we did, for 6 years after its records are deleted, the time in which a claim about our agreement could be brought; then we delete the names, the sign-in's id and any note from it, and from the firm's earlier requests that did not go ahead. A request that does not go ahead is kept with the firm's records.
When a test report is issued, we keep with it the sign-in's id and how long ago the engineer last confirmed their identity, as proof that the engineer named on the report issued it. That record is kept by the tester firm with the report.
6. Keeping Tyndall Air working and secure
- Request logs. Each request to Tyndall Air writes a log line from a fixed list of fields: what was asked for, the answer's status, and our own internal ids, which identify a person only through our database. It never holds a name, email address, IP address, sign-in token or the address of a page. Cloudflare keeps these lines for 7 days.
- Error alerts. When something fails, we are sent an alert with the same kind of fields, through Sentry, which holds it in its EU region (Frankfurt) for 30 days. Sentry is set never to store IP addresses.
- Limiting floods. To stop a flood of requests, Cloudflare counts requests for one minute at a time by the sender's IP address, or by the person's Clerk id. The count is not logged or kept.
- Downloads of a firm's records. When a firm's owner downloads its records, we keep a record of the download's one-time ticket: the firm, the owner, which part, the sign-in's id, and when it was made, used and finished. We keep a fingerprint of the ticket, never the ticket. Each record is deleted a day after its ticket expires. The download itself is also recorded in the firm's audit trail, which is part of the firm's records.
The legal basis for this section and section 5 is our legitimate interest, and the firms', in keeping Tyndall Air and its records secure.
7. Cookies and storage on your device
This website sets nothing on your device.
The Tyndall Air app keeps on your phone or computer only what it needs to work, including with no signal: the checks and report changes not yet sent, a copy of what is needed to open a check or report offline, and the app's own files. Everything the app keeps is removed when you sign out. Clerk keeps the cookies and storage that keep you signed in. During sign-in, Clerk's abuse and fraud protection checks the device in the browser, and Cloudflare's bot check, which Clerk uses, may keep what it needs to tell people from bots; profile pictures in Clerk's sign-in screens load from Clerk. All of this is strictly necessary for the app to work, so we do not ask for consent. There are no advertising or analytics cookies.
8. Invitations
Invitations a firm sends are part of the firm's records, which we process for the firm (section 2); the rules below are how Tyndall Air handles them for every firm. When a firm invites someone by email, Tyndall Air keeps that email address for the invitation and for 90 days after it ends (accepted, withdrawn, declined or expired). Then the address is deleted from our live database. The rest of the invitation (who sent it, for what role or site, when, and how it ended) is kept with the firm's records.
Invitations to join a firm are sent through Clerk, which keeps its own record of each invitation, including the address, under Clerk's own retention. Invitations to let a tester firm test a site are emailed through Resend, which keeps its own log of the email under its own retention: 30 days on our plan, the email itself included.
When we invite someone ourselves to set up a firm, we start the invitation from GitHub, which shows the address on that run's page until the run is deleted; we delete the run once the invitation has gone. We send the invitation through Clerk. We delete Clerk's copy, with the copies of its email Clerk stored, about 90 days after the invitation was accepted, withdrawn or ran out.
When someone starts setting up a firm and does not finish, we keep who started it and the firm's name for 30 days after the attempt is abandoned, then delete both. Clerk held an organisation with the firm's name and the starter's id; we ask Clerk to delete it when the attempt is abandoned. One left behind any other way is found by a daily check and deleted, normally within a day or two; the check is monitored, and we are alerted if it stops.
No copy or hash of a deleted address is kept, once the recovery copies in section 14 have expired.
For invitations we send ourselves, the legal basis is our legitimate interest in inviting the firms that have asked to use Tyndall Air.
9. Billing
When a firm's owner first adds a card, we send our payment provider, Stripe, the firm's name and that owner's email address, so Stripe can bill the firm and email its invoices. An owner may also add a billing address in Stripe's own pages. The card is entered on Stripe's own page and kept by Stripe: we never see or store a card number, only its brand, last four digits and expiry, to show which card is on file. Each invoice names each site's name and the first line of its address.
We keep invoices until 31 January after the end of the tax year they fall in, plus 5 years, as HMRC requires of a sole trader, and after that for as long as the firm's other records are kept. Which card is on file is kept with the firm's records, for as long as they are kept. When a firm's records are deleted at its request, we remove its cards from Stripe and clear the name, email address, phone number and addresses Stripe holds for it; if we hold no invoice to the firm, we delete it as a Stripe customer. We will delete our record of each request to Stripe after 1 year. Stripe cannot delete an invoice once it is issued, so Stripe keeps its copy for as long as it keeps invoices.
The legal basis is our contract with the firm, and our legal duty to keep tax records.
10. Emails we send
Tyndall Air emails a firm's people only about its own records and account: invitations, reminders of checks and documents due, missed checks, new defects, and billing notices to owners. We send no marketing email. These emails are part of the service the firm has asked for.
The email address is read from Clerk at the moment of sending and not kept by Tyndall Air. Emails are sent through Resend, from Ireland, through Resend's own provider Amazon SES. Resend stores its record of each email in the United States.
11. Voice notes
This is part of a tester firm's records, which we process for the firm (section 2). An engineer can dictate a note in a test report. The recording is sent to Speechmatics, a UK company, which turns it into text in its EU region; if Speechmatics fails, it is sent instead to Cloudflare's speech-to-text service. The recording is never stored by us. We ask Speechmatics to delete it as soon as the text is back, and if that fails, Speechmatics deletes it itself within 7 days; Cloudflare keeps nothing once it has answered. The engineer edits the text, and only the edited text is kept, in the report.
12. Who helps us
We use these providers, each on our instructions, except Google, which holds our email under its own terms (section 4).
| Provider | What for | Where |
|---|---|---|
| Neon | The database: every record | AWS London |
| Cloudflare | Serving the app and this site, running Tyndall Air, storing photos, documents and PDFs, making PDFs, rate limits, email routing to us, backup copies (section 14) | Files and backup copies stored in the EU; processing on Cloudflare's network worldwide |
| Amazon Web Services | Backup copies (section 14) | London |
| Clerk | Sign-in: names, email addresses, invitations | United States |
| Resend | Sending emails | Sent from Ireland, stored in the United States |
| Stripe | Billing | UK and United States |
| Speechmatics | Turning voice notes into text | EU |
| Sentry | Error alerts | EU (Frankfurt) |
| GitHub | Starting invitations we send ourselves to set up a firm | United States |
| Duport | Receiving and scanning our post | United Kingdom |
| Google (Gmail) | Our email, including enquiries to us | United States and elsewhere |
The full list of the providers that process firms' records, with how each transfer is protected, is in our Data Processing Agreement.
We never sell personal data, and we share it with nobody else unless the law requires us to.
13. Where data is held, and transfers abroad
Records are held in a database in London, and photos, documents and PDFs in the European Union, which UK law recognises as protecting personal data adequately. Backup copies are held in London and in the European Union. Not all data stays in the UK: Tyndall Air runs on Cloudflare's worldwide network, and sign-in data is held in the United States.
Where personal data goes to the United States, it is protected by the provider's certification under the UK extension to the EU-US Data Privacy Framework, or by the European Commission's standard contractual clauses with the UK's International Data Transfer Addendum, as each provider's agreement sets out. Our Data Processing Agreement lists which applies to each provider that processes firms' records. GitHub relies on standard contractual clauses (GitHub's privacy statement, read 19 November 2026). Duport is in the UK. Our email is held by Google, as section 4 explains.
14. How long we keep data
| Data | Kept for |
|---|---|
| A firm's records | At least 5 years from each record's date, then while the site remains with us; we will delete them when the site has been closed for 5 years, or sooner if the firm asks, as our Data Processing Agreement explains |
| Invitation email addresses | 90 days after the invitation ends |
| An unfinished firm start | 30 days after it is abandoned |
| A sign-in's last use | 8 days after it was last used |
| The record that a firm accepted the Terms | As long as the firm's records, and deleted with them; if they are deleted at the firm's request, 6 years after that, then the name of who accepted is deleted |
| A firm's request to delete its records | 6 years after the records are deleted, then the names, the sign-in's id and any note in it are deleted; a request that does not go ahead, as the firm's records |
| A download's ticket | A day after it expires |
| Request logs | 7 days |
| Error alerts | 30 days |
| Invoices | 31 January after the tax year, plus 5 years, then as the firm's records |
| Enquiries to us | 2 years after the last message |
| Voice recordings | Not kept |
| Backup copies | The database: 30 days in the EU, 90 days in London; photos, documents and PDFs: 366 days (below) |
Recovery copies. Copies kept only to recover from a failure still hold deleted data until they expire: the database's restore history, which keeps the database's past states for 7 days; our nightly backup; and the database's own error log, if a change to that record was ever refused (the log can show the row). The nightly backup keeps an encrypted copy of the database for 30 days with Cloudflare in the European Union, and for 90 days with Amazon Web Services in London, where nobody can delete it early, then deletes it within 3 days. It keeps a copy of each photo, document and PDF for 366 days in both places, and makes a fresh copy of each file still held, so a deleted file is gone from every backup within 13 months. The backup is used only to recover Tyndall Air after a failure.
15. Your rights
You have the right to ask us for a copy of your personal data, and to ask us to correct it, delete it, limit what we do with it, or send it to you in a usable form. You can object to our use of it where we rely on our legitimate interests. Some rights do not apply in every case: for example, a check or an issued report is evidence and is never changed: a wrong reading is put right by a later check, and a report by a new report. Target bands, check schedules and documents are corrected by an amendment with a reason.
We make no decisions about people by automated means.
To use a right, email hello@tyndallair.co.uk. We will answer within one month. For a firm's records, we will pass your request to the firm, as section 2 explains.
If you are unhappy with how we use your data, please tell us first. You also have the right to complain to the Information Commissioner's Office, ico.org.uk.
16. Changes to this notice
We will publish any change here with its date, and email the owners of firms using Tyndall Air about any change that affects them.