Legal
Cookies and Browser Storage
Last updated September 10, 2026
This notice and the AME waitlist are intended solely for users located within the United States.
The site is reachable from anywhere, so this notice also describes what happens if you reach it from outside the United States: we do not use advertising measurement unless you accept it.
AME sets no analytics cookie, and sets an advertising cookie only where advertising measurement is on
Nothing on this site ever sets an analytics cookie. Where advertising measurement is on, Meta may set an identifier such as _fbp, described below. Where it is off, no Meta cookie is set, and any Meta cookie already in your browser is removed. We also record your choice itself, so we do not ask again.
We use no analytics service, no tag manager, no session recording, and no fingerprinting. We use one advertising and measurement technology, the Meta Pixel. If you are in the United States it is on unless you turn it off. Everywhere else, and whenever we cannot tell where you are, it stays off until you accept it.
We use six small items of browser storage, all our own.
What we store in your browser
| What we store | Why | Cleared |
|---|---|---|
| How you first arrived | The site that referred you, recorded as the site and page only, never the full link and never its query parameters, any campaign details in the link you followed, Meta’s click identifier fbclid if the link carried one, the AME page you landed on, and when you arrived, so we can understand which outreach channels are effective | When you clear browser storage |
| How you most recently arrived | The same details for your most recent arrival, so we can see the route you took back to AME | When you clear browser storage |
| Visitor id | A random id AME creates for this browser, so repeat visits from the same browser hold together. It is ours, it is random, and it holds nothing about you. We do not use it to work out who you are | When you clear browser storage |
| Session id | A random id AME creates for the visit you are in now, so the pages and form steps of one sitting hold together. It is stored with the time you were last active, which is what ends the visit. It is ours, it is random, and it holds nothing about you | When the browser session ends, or after 30 minutes with no activity |
| Advertising measurement choice | Records whether you turned advertising measurement on or off, so we do not ask again, and so a choice to turn it off is remembered even when your browser blocks site storage | When you clear browser storage, or when you change the choice on Your Privacy Choices |
| Opening-playback preference | Stops AME’s opening experience from replaying in the same browser tab. It records nothing about you | When you close the tab |
Each value is length-limited. This information is attached to a waitlist or application submission, and it is also attached to the website and form activity events described below, which happen before you submit anything.
The visitor id and the session id are pseudonymous. They are random values AME generates in your browser, they contain nothing about you, and we do not use them to identify anyone personally. They tell one browser and one visit apart from another, and nothing more.
Website and form activity events
Separately from browser storage, we record a small number of limited website and form activity events. They happen while you are using the site, and most of them happen before you submit anything: opening the waitlist form, starting to fill a form in, reaching a later step, and whether a submission succeeded or failed. We do not send a form activity event merely because you load or read a page. Something you do has to start it.
These events do not include your name, email address, or form answers. They may include the page, the type of interaction, your visitor id and session id, the arrival information already stored in your browser, and ordinary technical information associated with the request. Where advertising measurement is on, they may also carry Meta’s identifiers _fbp and _fbc. Where it is off, they never do. We use these events to understand form usage, prevent abuse, and diagnose submission failures.
Third parties
Every typeface, style, script, and media file is served from AME’s own servers. There are two exceptions.
The Meta Pixel loads from Meta only where advertising measurement is on for you, and never before that has been decided.
Cloudflare Turnstile loads from Cloudflare. It is a bot-protection check that tells a person apart from an automated script, and it guards the waitlist and application forms against automated abuse. It loads when you open the waitlist form, and on the application form when you first type into it. It does not load while you are only reading a page. Any cookie Cloudflare sets for that check is Cloudflare’s own security cookie. AME does not use Turnstile for advertising or for measurement.
Advertising measurement
AME advertises on Meta. To understand which campaigns bring people here, we use the Meta Pixel, an advertising and measurement technology provided by Meta. Where it is on, we use it for conversion attribution, so we can see which campaigns lead people to join, and for retargeting and audience measurement, so we can reach more people who are a fit for AME.
If you are in the United States, the Pixel is on unless you turn it off. We tell you it is running and give you a way to stop it. Everywhere else, and whenever we cannot tell where you are, the Pixel is off until you accept it, and nothing is requested from Meta before then. We work out where you are from your browser’s own time zone setting. That is not exact, so anyone we cannot place is asked first rather than measured.
The Pixel never runs, and we never ask, when your browser sends Global Privacy Control or Do Not Track, or when you have told us you are under 18. If you turn measurement off at any point, we tell Meta to stop, we drop anything not yet sent, and we remove _fbp and _fbc.
Meta’s click identifier is not the same as Meta’s cookies. If you arrive on a link that carries Meta’s click identifier, fbclid, we keep that value with your arrival details in your browser. That capture is first-party and happens whatever you choose, because the identifier is part of the link you followed.
_fbp and _fbc are Meta cookies, and _fbc is the cookie form of that click identifier. We read them, and include them with the events described above and with a waitlist or application submission, only where advertising measurement is on for you. Where it is off, we do not read them, we do not build _fbc out of a click identifier, and no Meta cookie is set at all.
This is separate from AME’s own first-party records, which are the visitor id, the session id, and the arrival information described above. Those stay first-party and are unaffected by this choice.
What we do not do
No third-party analytics. No session recording or heatmaps. No fingerprinting. No data brokers. No sale of personal information. No advertising cookies or ad-network tags anywhere advertising measurement is off.
Your choices
Clear or block browser storage at any time in your browser settings. AME keeps working. The form still submits and the site still functions. Only our view of where visitors came from is affected.
You can change your choice at any time on Your Privacy Choices. We honor recognized opt-out signals. If your browser sends Global Privacy Control or Do Not Track, the Meta Pixel does not load, we do not ask, and any earlier acceptance is ignored for as long as that signal is on.
Contact
legal@meetame.com
bh-EDGE Management LLC, a Georgia limited liability company
100 North Point Center, Suite 125, Alpharetta, GA 30022