Cookie Policy

This website still sets no cookies at all. An earlier version of this page said we had started using Google Analytics, Google Ads, and the Meta Pixel. The consent machinery for those was built, but the tags were never switched on, and the page should not have described them as live. It is corrected here.

What is true today: no analytics tag, no advertising tag, no cookie written by us, and nothing disclosed to Google or Meta. The controls below are real and already working - they simply have nothing to switch off yet. If we do enable a tag, this page changes first, and in the EEA, the UK, and Switzerland nothing would load until you accepted.

Three controls, all of which work immediately and none of which requires an account:

• Cookie preferences, from the link in the footer of every page. Analytics and advertising are separate switches - you may accept one and refuse the other.
• Do Not Sell or Share My Personal Information, also in the footer. This turns advertising off and is the CCPA opt-out.
• Global Privacy Control. If your browser or extension sends the GPC signal we treat it as a refusal of everything on this page, in every country, without asking you anything.

None of these cookies is set anywhere today. If we ever enable them, then in the EEA, the UK, and Switzerland none would be set until you accept, refusing would be one click in the same place and of the same size as accepting, and we would not ask again afterwards.

None of the cookies in the analytics and advertising rows is set today - the tags that would write them are not enabled. They are listed so you can see exactly what would appear if we turned them on. Durations are the maximum set by the provider. If enabled, they would be set only after you accept, or, outside the EEA, the UK, and Switzerland, until you refuse.

Neither Google nor Meta receives anything from this website today. Their tags are configured in our code but not enabled, so no request is made to either of them and no identifier leaves your browser. They remain in the subprocessor table above because the integration exists and could be switched on; the table says plainly that it has not been.

If we do enable them, this is what would apply. Google LLC would receive analytics and advertising identifiers under Google Consent Mode v2, which tells Google your consent state alongside every request and requires it to restrict processing accordingly, with IP addresses truncated by Google Analytics before storage. Meta Platforms Ireland Ltd. would receive advertising identifiers via the Meta Pixel, with Meta’s Limited Data Use flag set for visitors we identify as being in California - and applied anyway where we cannot determine the US state, rather than guessing in our own favour.

Both would be independent controllers for their own purposes. We could tell them what we consent to on your behalf and stop sending them data, but we could not delete what they hold. Their own policies would govern that, and both offer their own opt-outs.

What we never send them: your email address. The waitlist is not uploaded to any advertising platform as a custom audience, a lookalike seed, or a hashed conversion. You gave us that address for one thing, and this is not it.

• No session recording, heatmaps, or replay of what you did on a page
• No fingerprinting beyond what the tags above do by default
• No data broker relationships, and no sale of personal information for money
• No advertising cookies inside the Service itself - this is the marketing website only

Write to privacy@mneia.dev. If you want a decision reviewed by a person rather than a preference centre, that address reaches one.