What we collect

Your name

So the person who calls you back knows who they are asking for.

Your phone number

So we can call you back. On the waitlist, it is also the number we call or text when ordering opens, and only if you ticked the box that allows it.

Your email address, if you give it (waitlist only)

Optional. We email you when ordering opens and about our plans, and only if you ticked the email box. Every email has a link to stop them.

Your ZIP code (waitlist only)

So we know where the people waiting are, in case ordering does not open everywhere on the same day.

Who the system is for

Yourself, a parent, a spouse, another family member, or someone else. It changes the conversation, so the agent has it before they dial.

Campaign attribution

Up to six campaign tags from the web address you arrived on (utm_source, utm_medium, utm_campaign, utm_term, utm_content and a Google click identifier), the page you landed on, the host name of the site that referred you, and the time of that first visit. This tells us which advertising is worth paying for. It contains nothing about you.

A record of your consent

The exact sentence you agreed to, its version, the moment you agreed, the page you were on, your network address and your browser's user agent. On the waitlist we also keep both sentences exactly as they were shown and which boxes you ticked. This is evidence of what you were shown, which protects you as much as it protects us.

What we do not collect

No home address, no date of birth, and no medical information. The call-back form has three fields; the waitlist has five, and the only optional one is email. There is nothing else hidden in either. We do not buy lists and we do not sell yours.

No advertising pixels

This site carries no advertising pixel and no third-party advertising tracker. Not from a social network, not from a search engine, not from an affiliate network. The only measurement on the site is our hosting provider’s own page analytics, which counts page views and does not identify you.

This is enforced in the code, not only promised here: the content security policy this site sends permits no advertising origin at all, so a pixel could not load even if someone added one by mistake.