Legal
Cookie Policy
Last updated: 16 September 2026
MAILHAUS uses limited browser storage during the MVP so the landing page, demo app, and open beta can work reliably.
Browser storage currently used
The app may use local storage to keep demo workspace data, local waitlist fallback entries, selected project, temporary UI state, and local/private QA test sessions.
Supabase authentication may use cookies or browser storage to maintain a session when real auth is configured.
Analytics and tracking
We use PostHog (PostHog Inc., EU Cloud) for aggregate website analytics. It is cookieless: it sets no analytics cookie and stores no identifier in your browser, and IP addresses are anonymised. It does not run inside the signed-in workspace.
The public waitlist endpoint may store source, path, referrer, and basic metadata to understand which pages produce signups.
Managing storage
You can clear local MAILHAUS data by clearing browser site data for `mailhaus.co.uk` or your local development host.
Clearing storage may remove demo records, local waitlist fallback entries, and temporary app state from that browser.