Privacy
Here is what the committed website code configures and what the signup handler stores. The linked files describe those settings; they do not establish every service's deployed settings or retention practices.
Last updated 16 October 2026 · Kontour AI LLC
This page is about the website. The Station app collects different things, on hardware you control, and has its own policy: what the Station app collects →
Reading the site requires no account. Analytics, session recordings, fonts, and hosting can still involve data collection.
The production layout configures two analytics tools: Umami and PostHog. The code enables page and click analytics, including PostHog autocapture and page-leave events. PostHog uses browser local storage for persistence and sets person_profiles: 'identified_only'. This site's loader does not call identify to attach a name or email. Browser and session identifiers can still link events over time; these settings do not establish anonymity. The PostHog loader checks Do Not Track before loading its SDK, and the Umami script is configured with data-do-not-track="true". See the configuration →
The PostHog loader configures session replay with maskAllInputs: true, intended to mask input fields such as the signup email. Page text, interaction history, and browser/session identifiers can still be recorded. Input masking is not a guarantee that a recording cannot identify someone. We have not verified vendor-side retention or every deployed replay setting from this source review.
The layout loads typefaces from Google Fonts, so font requests expose connection information such as an IP address to Google. Cloudflare Pages handles site requests. The layout can also load Cloudflare Web Analytics when a deployment supplies its token. This code review does not establish whether that optional beacon is enabled or how these vendors retain request data.
The signup handler writes five fields into the subscriber record: your email address, which page you submitted it from, the time you submitted it, your browser's user-agent string, and the page that referred you. The handler writes that record into the configured Cloudflare key-value store. This describes the application's write path, not all infrastructure logs or account access controls. See the code that writes it →
To stop the form being hammered, the same code counts submissions per IP address for ten minutes at a time. That counter expires on its own and is never written into your signup record.
We use the address to send occasional build updates, and to reply if you started a conversation. We do not sell it, rent it, share it with advertisers, or load it into an ad network.
We keep it until you ask us to delete it. There is no self-serve unsubscribe link yet — that is a real gap, not a policy — so for now, email hello@kontourai.io and ask, and we will delete the record and confirm. You can ask for a copy of what we hold the same way.
The layout and security policy name the services below. The policy restricts script and connection destinations; it also permits HTTPS images from other hosts. It does not establish a complete inventory of vendor processing or retention. See the allowlist →
If what the site collects changes, this page changes in the same commit — the history is public, so you can see what it said before. Questions, deletions, or anything else: hello@kontourai.io.