Data Processing Agreement
Version 1.0. In force from 22 November 2026.
This agreement is part of our Terms of Service. It covers the personal data in your firm's records in Tyndall Air, which we process for your firm. It is written to meet Article 28 of the UK General Data Protection Regulation (UK GDPR). Words such as controller, processor, personal data and personal data breach have the meanings UK GDPR gives them.
1. Roles
Your firm is the controller of the personal data in its records. We, Michael Stevenson trading as Autaimate, are its processor.
A workshop and the tester firms it allows to see a site are each the controller of their own records. When a workshop's owner gives a tester firm access to a site, that is the workshop's instruction to us to show that tester firm what Tyndall Air shows a tester. When a tester firm issues a test report, the workshop it is about may read and download its PDF.
2. What we process, and why
The details of the processing are in Annex 1. We process it only to provide Tyndall Air to your firm under the Terms.
3. Your instructions
We process the personal data only on your firm's documented instructions. Those instructions are the Terms, this agreement, and what your firm's people do in Tyndall Air. If the law requires us to process it in any other way, we will tell you first, unless the law forbids it. We will tell you if we think an instruction breaks data protection law.
We do not sell the personal data, use it for advertising, or use it to train any artificial intelligence.
4. Who can see it
Michael Stevenson is the only person at Autaimate with access to your records, and the only person with access to our accounts at the providers that hold them (Neon, Cloudflare, Amazon Web Services, Clerk, Resend, Stripe, Speechmatics and Sentry) or at GitHub, where Tyndall Air's code is kept. Anyone we later give access to will be bound by a duty of confidentiality first, and we will update this section.
5. Security
We protect the personal data with the measures in Annex 2, and keep them under review.
6. Sub-processors
You give us general permission to use the sub-processors in Annex 3. Each is bound by a written agreement that protects the personal data as this agreement does.
Before we add or replace a sub-processor, we will email your firm's owners at least 30 days ahead. If your firm objects on reasonable grounds and we cannot resolve it, your firm may stop using Tyndall Air, and we will refund any days already paid for after the date it stops.
We remain responsible to your firm for our sub-processors.
7. Helping you
We will help your firm, as far as we reasonably can:
- answer requests from people exercising their rights. Many can be answered from what Tyndall Air shows and lets you download. If a request reaches us, we will pass it to your firm without undue delay and will not answer it ourselves unless you ask us to;
- keep the personal data secure, deal with a breach, and carry out a data protection impact assessment or consult the ICO, using the information we hold about how Tyndall Air works.
8. Personal data breaches
We will tell your firm's owners by email without undue delay, and within 48 hours of becoming aware, of any personal data breach affecting your firm's records. We will say what we know: what happened, what data and how many people it affects, what we have done, and what we will do. We will add to it as we learn more.
9. When your firm leaves
Your records stay readable and downloadable while your firm's sites are closed, as the Terms describe. When a site has been closed for 5 years without a break, we will delete its records.
Your firm can instead ask us to delete all of its records sooner.
Asking. One of your firm's owners asks on the Records page in Tyndall Air, after confirming it is them. A workshop can ask once all its sites are closed; any firm can ask once no site payment it makes or receives is running and no handover of a site's payment is open. If no owner of your firm can sign in, email us at hello@tyndallair.co.uk: we will check that you are an owner of the firm before we make the request for it.
Time to cancel. We email every owner of your firm when the request is made, and any owner who joins while it is open. Nothing is deleted for 7 days, and any owner can cancel the request on the Records page until it is carried out. The request ends, and nothing is deleted, if your firm starts using Tyndall Air again (a site reopened, a payment begun or a handover opened), or if, when the 7 days are over, the owner who asked in Tyndall Air is no longer an owner. When a request ends, we email everyone who was told of it.
Deleting. Within 30 days of the 7 days ending, or of your firm's billing being settled if that is later (its last invoice paid, and any credit or balance we owe it refunded), we delete your firm's records from Tyndall Air's database. Before then, your firm's owners can download all of its records, with the exceptions the Terms list; once they are deleted, we cannot give them back. With them go a tester firm's reports on your sites that it had not issued, and every link between your firm and another firm's sites ends. We also delete your firm's organisation at our sign-in provider; each person's own sign-in account stays theirs, and each may ask us to delete it, as our Privacy notice explains. At our payment provider, we remove every card your firm gave us and clear the name, email address, phone number and addresses it holds for your firm; if we hold no invoice to your firm, we delete your firm as a customer there. Then we email every owner what was deleted, and what is kept and until when.
What is kept, and until when.
- Our invoices to your firm, and what they name (each site's name and the first line of its address): kept as the law requires, as our Privacy notice explains, without the links that open them at our payment provider.
- An issued test report is a record of both the tester firm and the workshop it is about: it is kept, unchanged, while the other firm still holds it, with the names it was issued with, and so are its PDF and the logo it printed.
- Your sites and LEV systems, by name only, where those invoices or reports name them; their addresses, postcodes and other details are deleted.
- Apart from those reports, anyone from your firm named on a record we keep is shown on it as "Former member", no longer linked to their sign-in, and your firm as "Former firm".
- The record of your request, with your firm's name and who accepted our Terms for it and when: kept for 6 years after your records are deleted, so that we can show what was agreed and what was done, and then the names are deleted from it.
- Photos, documents and PDFs are stored locked against deletion for 5 years from when each was stored, a setting we check before every change to Tyndall Air, so that nothing in Tyndall Air, and no mistake, can delete them early. Those deleted with your records cannot be opened through Tyndall Air meanwhile, and each is deleted the day after its lock ends; our email tells you the last of those days. A file a kept record names is kept with it, and deleted once nothing names it.
Copies in recovery systems are deleted as those copies expire, as the Privacy notice describes. If we ever restore Tyndall Air's database from such a copy, we delete your firm's records from it again before it is used.
10. Audits
We will make available the information your firm reasonably needs to show that this agreement is kept, including our data map: the list of every field Tyndall Air holds, why, where and for how long. We will answer reasonable written questions. Your firm, or an auditor it appoints who is bound by confidentiality, may inspect how we meet this agreement once a year, on 30 days' notice and at your firm's cost, in a way that does not reveal other firms' records.
11. Transfers outside the UK
Some sub-processors process personal data outside the UK. Each transfer is protected as Annex 3 sets out: by an adequacy regulation, the provider's certification under the UK extension to the EU-US Data Privacy Framework, or the European Commission's standard contractual clauses with the UK's International Data Transfer Addendum.
12. Liability and duration
The limits of liability in the Terms apply to this agreement. This agreement lasts for as long as we process your firm's records.
Annex 1: details of the processing
| What | Details |
|---|---|
| Subject matter | Keeping a workshop's local exhaust ventilation (LEV) records, and a tester firm's test reports, in Tyndall Air |
| Duration | For as long as your firm uses Tyndall Air, then as section 9 describes |
| Nature | Storing, organising, showing, printing to PDF, emailing about, and deleting records |
| Purpose | Providing Tyndall Air to your firm under the Terms |
| People | Your firm's owners, supervisors, operatives and engineers; people your firm invites; sole traders whose own names are a firm's or a site's name; people named in the free text your people write |
| Personal data | Names of the people who did, set, raised, fixed, signed off or changed each record, and the log of who changed what and when; when each check was started and finished on the device and received by the server, whether it was done offline, and the offline kit it used; invitees' email addresses, while an invitation lasts and for 90 days after; engineers' qualifications and certificate numbers, and, for each issued report, the sign-in's id and how long before the issue the engineer last confirmed their identity; site names and addresses, and firm names (which may be a sole trader's own; a firm's and a site's names also appear on the public verify page of each issued report and HSE visit pack); a tester firm's logo; free text your people write, such as notes and defect descriptions; voice notes, as audio only until they are turned into text |
| Special category data | None is expected. Do not put health information about anyone into Tyndall Air |
| Not collected | Location or GPS, card numbers, audio once it is turned into text. Photos must be of equipment, never of people; the app removes location and other hidden data from every photo |
Annex 2: security measures
Keeping firms apart and records true
- Every request reads and writes only the records of the signed-in person's own firm, and the database enforces the same separation a second time, with row-level security. A tester firm reads a workshop's site only through database functions that check the workshop's access grant.
- What a person may do is read from the database on every request, from their role in the firm, and never trusted from the browser. Anything not allowed is refused.
- The access grant is checked on every request, so taking it back takes effect at once.
- Records that are evidence cannot be changed or deleted by the app: the database refuses. A band, schedule or document is corrected by an amendment with a reason. Every change records who made it and when.
- Issued reports and HSE visit packs are stored once, fingerprinted, and never overwritten.
Storage and transfer
- All connections use TLS (HTTPS).
- The database is held by Neon in AWS London. Neon encrypts stored data with AES-256 (Neon's security overview, read 19 November 2026).
- Photos, documents and PDFs are held in private Cloudflare R2 storage in its EU jurisdiction, reachable only through Tyndall Air's own server, and locked against deletion and overwriting. R2 encrypts stored objects with AES-256 (Cloudflare's R2 data security page, read 19 November 2026).
- Photos are taken only with the app's own camera; location and other hidden data are removed on the device, and the server refuses a photo that still holds any.
Sign-in and devices
- Sign-in is by a one-time code sent to the person's email address. A sign-in ends after 8 hours without use and after 7 days at most.
- Adding or changing a card, starting to pay for a site, closing a site, handing a site's payment to a tester firm, and issuing a test report all need the person to have confirmed their identity again within the last few minutes.
- What the app keeps on a device is removed at sign-out.
Running the service
- Logs hold a fixed list of fields and never a name, email address, IP address, sign-in token or page address. Error alerts carry the same kind of fields.
- The service's keys are held as encrypted secrets in Cloudflare, and the keys used to deploy it as encrypted secrets in GitHub, never in the code.
- Every change is tested automatically before it reaches Tyndall Air, including tests that one firm cannot reach another's records, and every dependency is checked against published security advisories.
- A separate test system holds made-up data only.
- Every night the database and the files are backed up to two places: Cloudflare R2 in its EU jurisdiction, and Amazon Web Services in London, where each copy is locked so that nobody, including us, can delete or change it early. Database copies are encrypted before they leave the backup run. The one key that can read them is held by us in our own Google account, apart from every system that runs or stores the backups. The backup's database login can read every record and change none. How long the copies are kept is in the Privacy notice, section 14.
Not in place. We have no independent security certification (such as ISO 27001 or SOC 2) and have not had a penetration test.
Annex 3: sub-processors
| Sub-processor | What it does | Personal data | Where | Transfer protection |
|---|---|---|---|---|
| Neon (part of Databricks) | The database | All records | AWS London | In the UK. Neon's data processing agreement includes the standard contractual clauses with the UK Addendum for any access from outside the UK (read 19 November 2026) |
| Cloudflare, Inc. | Runs Tyndall Air's servers and the app; stores photos, documents and PDFs; makes PDFs; turns a voice note into text if Speechmatics fails; limits floods of requests; holds backup copies | All records pass through it; files and backup copies stored | Files and backup copies: EU. Processing: Cloudflare's network worldwide | UK extension to the Data Privacy Framework; otherwise standard contractual clauses with the UK Addendum (Cloudflare's data processing addendum, version 6.4, read 19 November 2026) |
| Amazon Web Services EMEA SARL | Holds backup copies of the database (encrypted) and of photos, documents and PDFs | All records, in backup copies | AWS London (eu-west-2) | In the UK. AWS's data processing addendum, in the AWS Service Terms, includes the standard contractual clauses with the UK Addendum for any transfer outside the UK (read 21 November 2026) |
| Clerk, Inc. | Sign-in | Names, email addresses, sign-in sessions and their device and IP details, invitations, firm names | United States | UK extension to the Data Privacy Framework, with a UK Addendum (Clerk's data processing agreement) |
| Resend | Sends emails | Recipients' email addresses; what each email says: the firm, site and point, what was found, a link; never a reading's value, a photo, or the name of a person who did or should have done something | Sent from Ireland through Amazon SES; stored in the United States | Standard contractual clauses with the UK Addendum; and the UK extension to the Data Privacy Framework (Resend's data processing agreement, read 7 November 2026) |
| Stripe Payments UK Ltd and Stripe, LLC | Billing (our own processing, listed here because invoices name your sites) | The firm's name, the owner's billing email, each site's name and first address line on invoices | UK and United States | UK extension to the Data Privacy Framework; Stripe's data transfers addendum with the UK Addendum (read 13 November 2026) |
| Speechmatics | Turns voice notes into text | Voice note audio: we ask for it to be deleted as soon as the text is back, and it is deleted within 7 days at most | Its EU region; a UK company | Standard contractual clauses with the UK Addendum for its own providers outside the UK and EEA (read 11 November 2026) |
| Functional Software, Inc. (Sentry) | Error alerts | Our internal ids only, never a name or address; held 30 days | Stored in its EU region, Frankfurt | Standard contractual clauses with the UK Addendum, and the UK extension to the Data Privacy Framework (Sentry's data processing amendment, version 5.1.0, accepted 18 November 2026) |