What this website collects, and what it does not.

What the contact form collects

The form on /contact and /demo asks for your name, work email, organisation, and what you need: a topic and a rough device count. Your role, your country and a message are optional. Nothing else on the site collects anything about you.

There is one field you will not see: a hidden input a person never fills in and an automated script usually does. If it arrives filled, the submission is discarded.

Where it goes

Straight to a mailbox we read, sent through Amazon SES in us-east-1. It is not passed to a third-party form service, a CRM we have not named here, a mailing list, or any enrichment service that would attach to you what you did not tell us.

Two processors are involved and both are named rather than implied: Cloudflare, which serves this site and through whose network your submission passes, and Amazon Web Services, which delivers the mail.

Your IP address is hashed, not stored

To stop one machine flooding the form, the server counts recent submissions per origin. It does that against a SHA-256 hash of your IP address, never the address itself, and the count expires after an hour. A rate limiter needs to know that two submissions came from the same place; it never needs to know where.

Your country (the country alone, derived by Cloudflare from the connection) is attached to the submission so a reply arrives at a sensible hour.

Cookies, and what is kept on your device

This site sets no cookies. If you use the light/dark toggle, that choice is stored in your browser's local storage under itzal-theme. It stays on your device, is never sent to us, and clearing site data removes it.

How long we keep it

A submission is kept while the conversation it started is live, and deleted afterwards. Ask us to delete it sooner and we will.

Your rights, and how to use them

Ask for a copy of what we hold, ask for it corrected, or ask for it deleted, by writing to us through the contact form, which reaches a named person rather than a queue. We will not ask you to prove anything beyond enough to be sure we are answering the right person.

Depending on where you live you may also have the right to complain to a supervisory authority. Our establishment is in the United States, which has no single federal authority for this. If you are in the UK or the EU you may complain to your own national supervisory authority. If you are in another jurisdiction you may also have a route to your own regulator; we will not object to you using it.

Analytics

This site can load Google Analytics 4, through Google Tag Manager, and does so only if you accept the banner. Until you answer, neither is requested: the container is not in the page, no connection to Google is opened, and declining leaves Google with no record that you were here. That is a deliberate departure from the usual arrangement, where the tag loads immediately in a “denied” state and your address reaches the vendor before you have been asked. On a product built around not moving data before a decision is made, the usual arrangement was the wrong shape.

If you do accept, Google sets cookies (_ga and _ga_FTVDVF66QP, which last two years) giving your browser a random identifier, and receives the pages you open, the site that referred you, your device and browser, and an approximate location derived from your IP address. Google processes this for us and also for its own purposes under its own terms. Our lawful basis is your consent, which is the reason the question comes first. We use it to learn which pages answer a question and which waste your time. We do not attempt to identify you from it, and we do not combine it with anything you send us through the contact form.

You can change your answer whenever you like: reopen the cookie choice. Declining later stops this site sending anything further, but it cannot reach back and delete what Google already holds: Google’s own controls are the only route to that.

Two limits we have kept. The Content-Security-Policy this site is served under still names the hash of every inline script and still grants no unsafe-inline, which means the tag manager cannot be used to inject arbitrary code: Custom HTML tags in the container are refused by your browser, not merely left unconfigured. And no advertising or remarketing tag is configured at all: ad_storage, ad_user_data and ad_personalization are set to denied and stay denied whichever button you press.

One exception, stated because it is currently true: our host injects Cloudflare Web Analytics into pages served to browsers. The policy above blocks it from executing, but it is present in the markup and you can see it in view-source. It is being turned off; until it is, this paragraph is the accurate statement.