Privacy
What this site collects, who else sees it, and how to get rid of it.
Last updated 14 September 2026
Reading the site
Nothing is collected. There is no analytics script, no tag manager, no advertising pixel and no cookie of ours on any page — the site is a set of static files and a shader. Our host, Cloudflare, keeps ordinary server logs of requests, including IP addresses, to serve the site and keep it up; we do not build profiles from them.
The 3D wall runs on your own graphics hardware. It measures nothing about you and sends nothing anywhere.
Signing in
Signing in is Sign in with Google, and that is the whole of it. You authenticate at accounts.google.com, not here. Your password, one-time code or passkey never touches this site, and we could not read it if we tried.
What comes back is one identity token: a short statement, signed by Google, saying who you are. It carries your name, your email address, your profile picture and the identifier Google uses for you, and your account page lists every field of it. It is not an access token — there is no key to your mail, your files, your calendar or your contacts in it, we did not ask for one, and there is nothing here that could be used to act as you at Google.
We check that token before believing a word of it: the signature against Google's published keys, that Google issued it, that it was issued to this site rather than some other one, that it answers the one-time value this page generated, and that it has not expired. A token that fails any of those is thrown away.
It is kept in this tab's storage and nowhere else. Closing the tab discards it, it expires on its own within the hour, and nothing goes to localStorage, where it would outlive the visit. We have no server that could store it, because we have no server.
Because Google is who you sign in with, Google knows that you use this site, in the same way it would for any site you sign in to with it. What Google does with that is governed by its own privacy policy, and you can withdraw this site's access at any time from your Google account's connections.
If you sign in to two different accounts on one browser, anything cached for the first is deleted the moment the second arrives. We key that cache on the issuer and your identifier, so two people with the same identifier at different providers are never the same person here.
Booking a demo
The booking form is Cal.com, an open-source scheduler, embedded from cal.com. It loads only when you open the booking page — not on any other page of this site — so nothing from Cal.com runs while you are simply reading.
What you type into it goes to Cal.com and to us: your name, your email address, the time you picked and anything you write in the notes. If you are already signed in, your name and address are filled in for you and remain editable. We use it to hold the call and to follow up about it, and for nothing else.
The call itself is held on Cal Video, Cal.com's own video room. The confirmation carries that link, and joining it needs no account and no download — the meeting runs in your browser. There is no Google Meet, no Zoom and no third meeting provider in the middle of it: the only company handling the call is the one that handled the booking.
Who else processes it
- Cloudflare — serves the site; request logs.
- cal.com — Cal.com; scheduling, confirmations, and the Cal Video room the call is held in.
- Google — authenticates you and tells us your name and email address. That is its whole part in this: it is not in the booking, and it is not in the call.
That is the whole list. We do not sell anything to anyone, and there is no fourth party you have not been told about.
How long
The identity token: until it expires, or the tab closes — whichever comes first. Cached page state: until you sign out, or a different account signs in on that browser. Bookings and the mail around them: kept while we are in touch, and deleted on request.
Your say
You can see what is held, clear it, and sign out from your account page. For access, correction, export or deletion of anything beyond the browser — a booking, a thread of mail, the account itself — write to suzan@omnidynamics.dev and we will do it and tell you what was removed. If you are in the UK or the EU, those are your rights under the GDPR and you do not have to cite it to use them; you may also complain to your data protection authority.
This site is not for children, and we do not knowingly collect anything from anyone under 16.
Changes
This page is versioned alongside the code it describes. Material changes move the date at the top, and anything that widens what we collect will be asked for rather than announced.