Privacy policy
Three things on this site involve your data: an analytics cookie you can refuse, a cookie of our own that remembers how you found us (also yours to refuse), and a demo form you choose to fill in. This page explains all three in full. No “we value your privacy”, no 4,000 words of hedging.
Everything describing what this website actually does is accurate and taken from the code. Anything in [square brackets] is a fact only Ensign can confirm — company details, retention periods, contracts with suppliers. Those are unresolved, and this notice stays up until they are.
Last updated: [date of approval]
Four points, then the detail.
- We use Google Analytics to see how people find and use this site. In the UK it stays switched off until you press Accept, and you can change your mind from any page.
- If you press Accept, one cookie of our own also remembers the page you arrived on and any campaign link that brought you here, for 30 days. It is read only if you submit the demo form. Press Reject and it is never written.
- Advertising cookies are switched off permanently. Not as a promise — the site is built to send Google a hard-coded refusal on every one of them, whatever you choose.
- If you fill in the demo form, it becomes an email to two people and one entry in the enquiry list we run ourselves, so we can follow up and see which marketing led to it. Nothing else is done with it.
We don’t sell data, share it with advertisers, or build profiles. The rest of this page is the detail, because UK GDPR requires it and because a summary you can’t check isn’t worth much.
Who is responsible for your data.
ZeroCount is the AI takeoff product of Ensign and this site is aitakeoff.com. The data controller — the organisation that decides what happens to your data and answers for it — is:
[registered company name], registered in England and Wales, company number [company number]. Registered office: [registered office address]. Registered with the Information Commissioner’s Office under registration number [ICO registration number].
For anything on this page — a question, a correction, or a request to delete what we hold — email jonathan@ensign.software.
Cookies and analytics.
If you are visiting from the UK, the EEA (which includes Iceland, Liechtenstein and Norway), Switzerland or California, Google Analytics is switched off before the page finishes loading and stores nothing on your device until you press Accept on the banner. Everywhere else it starts on and the banner lets you turn it off. Either way the banner appears, and either way your choice sticks.
Pressing Accept also allows one cookie of our own, described below, which remembers how you first arrived. Press Reject and it is never written; change your mind later and it is deleted.
You can change your mind at any time with the Cookie preferences button at the bottom of every page. It reopens the same banner; whichever button you press replaces your previous choice immediately.
The cookies themselves
- zc_consent — set by us
- Records nothing except your answer to the banner: “granted” or “denied”. It is set only when you press one of the two buttons, lasts 12 months, is first-party, and is marked SameSite=Lax and Secure. We read it on every page load to decide whether to show you the banner and how to configure analytics. It is the reason you are not asked twice.
- zc_attr — set by us
- Where you arrived from: the first page you landed on, the site that sent you here if there was one, any campaign tags in the link (utm_source and the like, or a Google Ads click identifier) and the time. It is written only after you press Accept — until then it is held in the page’s memory and lost when you leave — lasts 30 days, is first-party, and is marked SameSite=Lax and Secure. Nothing reads it except the demo form: if you submit an enquiry, it is attached to that enquiry so we can see which marketing brought you. Press Reject and it is deleted.
- _ga and _ga_… — set by Google Analytics
- Only ever present once analytics is active. They give your browser an identifier so Google can tell a returning visitor from a new one, and one session from the next. Google sets them, Google controls their lifetime, and Google’s documented default is two years. Reject analytics and they are never set; if you have already accepted and change your mind, clear your cookies for this site to remove them.
What we ask Google to measure
When analytics is on, the site reports:
- Which pages you view.
- How far down each page you scroll — reported at 25%, 50%, 75% and 100%.
- Which buttons and navigation links you click, and where on the page they were.
- When a link takes you off the site, and which link it was.
- How far you get through the demo form: that you saw it, that you started it, that you finished a field, that you submitted it, and whether validation stopped you.
- Which comparison and pricing content you look at, and the £55 licence value attached to a completed enquiry.
One point worth being explicit about: the “finished a field” event sends the name of the field — “email”, “phone” — and never a single character of what you typed into it. Nothing you enter in the form is sent to Google.
Advertising: off, permanently
Google’s consent framework has four switches. We grant at most one of them. Ad storage, ad user data and ad personalisation are set to denied in every code path on this site — before the banner, after you accept, after you reject, on every page. There is no combination of choices that turns them on. We run no advertising pixels, no remarketing tags and no third-party trackers of any kind.
If a link you clicked carries a Google Ads click identifier, it arrives as part of the page address, so Google Analytics receives it with the page view if you accept analytics. We keep our own copy of it in the cookie above only after you press Accept, only to see which enquiries an advert produced, and never to target anyone.
Our typeface is downloaded when the site is built and served from our own server, so displaying this page does not send your IP address to Google Fonts.
The one thing that happens whatever you choose
When a demo request is sent successfully, our server tells Google that an enquiry happened. That message contains the licence value (£55), the currency, and a label saying it came from the form. It contains nothing you typed — not your name, not your email, not your company. It is sent server to server and stores nothing on your device.
If you accepted analytics, we attach your existing Google Analytics identifier so the enquiry is not counted twice. If you rejected it, there is no identifier to attach, so a random one-time value is generated that links to nothing and is never stored. We do this because ad blockers hide a large share of B2B traffic and we would otherwise have no idea whether our marketing works.
The demo form, and where it goes.
The form asks for four things, all required: your name, your company, your email address and your phone number. It also offers a list of trades you estimate, with an optional free text box if none of them fit. That is the entire set of fields.
There is one more input you cannot see: an empty box that automated spam scripts fill in and humans never do. If it arrives filled, we bin the submission without sending it anywhere. It collects nothing about you.
What happens next
The site checks the fields, turns them into an email, and sends it through Resend — our email delivery provider — from leads@aitakeoff.com, with your address as the reply-to. It arrives in 3 inboxes:
- sales@ensign.software
- jonathan@ensign.software
- brandon@bsquared.software
The first two are Ensign. The last is the development partner who builds and runs this website, and who is on the enquiry so that a broken form is noticed rather than silently losing your request.
This website has no database of its own. Your enquiry is emailed to those inboxes and, if our enquiry-tracking system is reachable, recorded there as one entry in our enquiry list: the same details — name, company, email, phone, trades — plus, if you accepted cookies, the page and campaign that first brought you here. If you rejected cookies it records only the page the form was on. We run that system ourselves on a Hetzner server. An outage there never loses your request, because the email is sent first.
[To confirm: whether enquiries are also copied into any further CRM or contact list at Ensign, and who provides the two mailboxes].
We use it to contact you about a ZeroCount demo, and for nothing else. There is no marketing list to add you to. We do not need one.
Your IP address and the form
To stop scripts hammering the form, the server counts submissions per IP address and refuses more than three in any sixty seconds. That count lives in the server’s memory, is not written to disk, and disappears entirely whenever the site is restarted or updated. Your IP address is not attached to your enquiry or sent anywhere.
Where the site runs, and what it logs.
aitakeoff.com runs on a server rented from Hetzner Online GmbH, located in [data centre country]. Everything is served over HTTPS and the site sends strict transport security, frame, referrer and content-type headers on every response.
Like any web server, it produces technical logs, which can include your IP address, the time of the request, the page requested and your browser’s user agent string. These exist to keep the site running and to investigate abuse. They are kept for [server log retention period].
Who else touches your data.
Three companies are involved in running this site. That is the complete list.
- Google (Google Analytics 4)
- Measures how the site is used, once you have allowed it. Google is a US company and processes this data outside the UK.
- Resend
- Delivers the demo request email. Your name, company, email address, phone number and selected trades pass through Resend’s systems on the way to the two inboxes. Resend is a US company.
- Hetzner Online GmbH
- Provides the server the site runs on, and currently the server our enquiry-tracking system runs on. Hetzner is a German company.
Google and Resend both involve your data leaving the UK. The safeguard relied on for each transfer is [to confirm: Data Privacy Framework certification, standard contractual clauses or an IDTA, plus written processor agreements with each supplier].
Nobody else receives your data. We do not sell it, rent it or trade it, and no advertising network is involved at any point. We would disclose it if we were legally required to — a court order, for example — and we would tell you unless the law stopped us.
How long we keep it.
- Your demo enquiry
- [Retention period to confirm — how long the enquiry email, and its entry in our enquiry-tracking system, are kept if it does not turn into a customer relationship]. Ask us to delete it sooner and we will.
- Analytics data held by Google
- [Retention setting to confirm — the GA4 property is set to either 2 or 14 months]. Aggregate reporting outlives that; the event-level data does not.
- The zc_consent cookie
- 12 months, then your browser deletes it and the banner asks again.
- The zc_attr cookie
- 30 days, then your browser deletes it. Pressing Reject deletes it immediately. If you submit an enquiry, the landing page and campaign details it held become part of that enquiry and follow the enquiry retention period above.
- Google Analytics cookies
- Set and controlled by Google; their documented default is two years.
- Server logs
- [Server log retention period to confirm].
- The rate-limit count
- Held in memory for sixty seconds and lost on every restart.
Why we are allowed to do any of this.
- Analytics and attribution cookies, and the data they generate
- Your consent — regulation 6 of PECR and Article 6(1)(a) of the UK GDPR. You can withdraw it at any time from the Cookie preferences button in the footer, and withdrawing is exactly as easy as giving it.
- Your demo enquiry
- Steps taken at your request before entering into a contract, Article 6(1)(b), and our legitimate interest in answering business enquiries, Article 6(1)(f). You asked us to get in touch; that is what we use it for, and recording the enquiry in our own list is part of answering it.
- Rate limiting and server logs
- Our legitimate interest in keeping the site available and free of abuse, Article 6(1)(f).
- Counting the enquiry server-side
- Our legitimate interest in knowing whether our marketing works, Article 6(1)(f). The message carries no personal data and stores nothing on your device, which is why it does not depend on the cookie banner.
What you can make us do.
Under UK GDPR you have the right to:
- Ask what we hold about you and get a copy of it.
- Have anything wrong corrected.
- Have it deleted.
- Restrict what we do with it while a dispute is sorted out.
- Object to us relying on legitimate interests, including for anything resembling marketing.
- Receive what you gave us in a portable format, or have it sent to someone else.
- Withdraw consent for analytics at any time, without it affecting anything done beforehand.
Email jonathan@ensign.software and we will respond within one month. It is free. Tell us the email address you used on the form — finding your data means searching two inboxes and our enquiry list for it, and knowing the address makes that quick and complete.
If we get it wrong, you can complain to the Information Commissioner’s Office at ico.org.uk/make-a-complaint or on 0303 123 1113. We would rather you came to us first, but you are not obliged to.
Things this site does not do.
- No automated decision-making or profiling that produces legal or similarly significant effects. A human reads every enquiry.
- No special category data. We do not ask for it and you should not send it — health, ethnicity, beliefs, none of it belongs on a takeoff software enquiry.
- Not directed at children. This is business software sold to UK contractors, and we do not knowingly collect data from anyone under 18.
- No accounts, no logins, no payment details on this website. Anything to do with a ZeroCount licence itself happens after we have spoken to you and is not covered by this page.
Changes to this policy.
If what the site does changes, this page changes with it and the date at the top moves. If a change affects what we do with data we already hold, we will ask again rather than assume.
Questions, corrections, or anything that reads as evasive to you: jonathan@ensign.software.