CookiesFor people who build with AI

What this site stores in your browser.

Each cookie set here, the contest tracker, our visit counter, and the other sites your browser may contact.

Last changed: 18 November 2026.

The short version

We use no advertising cookies. Our own code sets a cookie only when you answer the tracker question, start a sponsor checkout or sign in. DataFast, which counts our visits, sets four cookies of its own. You get them unless you are asked first and do not accept. Our own code also keeps one short mark in your browser, listed below. Readers never need to sign in: only the site admin and people who claim a firm's profile do.

Every cookie

NameWhen it is setWhat it is forHow long it lastsWho sets itAsked first?
tracker_consentWhen you press Accept or Decline, in the tracker bar or on the privacy page. Only visitors who are asked see these buttons.It holds one word, accepted or declined, and nothing else.180 days, or until you clear it.Emergent.FM, in your browser.No. It holds your answer.
emfm_sponsor_accessWhen you start a sponsor checkout, before you go to Stripe.It holds the secret behind your private sponsor link, so the page you come back to can show you that link once. It is never sent to Stripe.2 days.Emergent.FM's server.No. The checkout you asked for needs it.
sb-<ref>-auth-token, which may be split into parts that end in .0, .1 and so onWhen the site admin, or someone who claims a firm's profile, opens a sign-in link. It is renewed on the admin and claim pages.It keeps you signed in. It holds your sign-in session, your user id and your email.400 days, or until you sign out.Emergent.FM, through Supabase's sign-in code.No. The sign-in you asked for needs it.
One or more cookies whose names start with sb-<ref>-auth-token and end in -code-verifierWhen the site admin asks for a sign-in link and Supabase sends it.A one-time check that the link is opened in the same browser.It is deleted when the link is used. If not, 400 days.Emergent.FM, through Supabase's sign-in code.No. The sign-in you asked for needs it.
datafast_visitor_idOn each page where you get DataFast.A random code for your browser, so DataFast can tell a new visitor from one who comes back.365 days.DataFast's script, on emergent.fm.Yes, if you are in an asked country. Otherwise no.
datafast_visitor_first_seen_atOn each page where you get DataFast.The time DataFast first saw your browser here.365 days.DataFast's script, on emergent.fm.Yes, if you are in an asked country. Otherwise no.
datafast_visitor_session_countOn each page where you get DataFast.How many visits your browser has made.365 days.DataFast's script, on emergent.fm.Yes, if you are in an asked country. Otherwise no.
datafast_session_idOn each page where you get DataFast.A random code for this visit.30 minutes. Each page view or click it sends starts the 30 minutes again.DataFast's script, on emergent.fm.Yes, if you are in an asked country. Otherwise no.

In these names, <ref> is the short name of our Supabase project.

Kept in your browser, not a cookie

emfm-consent-focus is kept in your browser's session storage for about a second. It is set when you change your tracker answer on the privacy page, just before the page reloads. It holds only the figure 1. After the reload it puts keyboard focus back on your answer, so a screen reader reads it out. Then it is deleted. It is never sent to us or anyone else. It is not asked for first, because it only finishes what you pressed.

DataFast keeps a few things in session storage too. They are set out under our visit counter.

The contest tracker

Emergent.FM is an entry in the Ship or Die contest. The contest makes each entry run its traffic tracker. The tracker is a script from www.ship-or-die.com. The contest organisers run it: JustShipIt Pte. Ltd., in Singapore.

When a page loads, when you move to another page of the site, and when you come back to its tab, the script sends them:

  • the path of the page, such as /listen;
  • the site that sent you here, but not the page on that site;
  • the utm_source and utm_medium tags in the page address, if there are any;
  • yes or no: does the page address hold an ad-click code.

Your network address reaches their server too, as it does with any request. The organisers say: "We do not collect ... cookies, or persistent browser identifiers through this script."

The script does nothing when your browser sends a Global Privacy Control signal. That is the script's own code, as we read it on 18 November 2026. Chrome does not send this signal on its own. We do not read the signal ourselves.

It is never loaded on pages whose address holds a private link: the unsubscribe pages, the page that stops notices, and a sponsor's private page. Nor is it loaded on the sign-in callback or the admin screens.

The organisers' privacy policy says what they keep and for how long. Our privacy page says what we keep.

Our own visit counter: DataFast

We use DataFast to count visits to this site. DataFast is a company outside this site. Its script comes from datafa.st. This part says what the script does, as read from its script on 18 November 2026.

It sets the four DataFast cookies in the table above. DataFast's own guide says its script "uses cookies for visitor identification".

It also keeps datafast_pageview_state in your browser's session storage. Session storage is cleared when you close the tab. When the page address holds a Stripe checkout code, it keeps a mark named datafast_stripe_payment_sent_ and then the code, so it sends that payment only once. The script has the same mark for two other payment services, with polar or lemonsqueezy in place of stripe. It reads datafast_ignore from local storage, and sends nothing when that is set to true. We never set it.

When a page loads, and when you move to another page of the site, the script sends DataFast:

  • the full page address, with any part after a question mark;
  • the page that sent you here;
  • the size of your window and your screen;
  • your browser's language and time zone;
  • the visitor and visit codes from its cookies;
  • any ad-click codes in the page address.

When you click a link to another site, it sends that link's address and words. When you come back from a Stripe checkout, the page address holds Stripe's checkout code. The script sends that code to DataFast as a payment. Your network address reaches DataFast too, as it does with any request.

If you are asked first, it loads only if you accept. Your one answer covers it and the tracker. When you press Accept, the tracker starts on that page. DataFast starts on a later page, once our server has your answer. If you decline, a page that runs either one reloads without them. Everyone else gets DataFast without being asked.

It is never loaded on the same pages as the tracker: the unsubscribe pages, the page that stops notices, a sponsor's private page, the sign-in callback and the admin screens.

If you decline later, its cookies stay in your browser until they run out or you delete them. Where DataFast keeps what it gets, and for how long, is up to DataFast. We have not set a time limit with it.

Who is asked first

We go by the country our hosting provider reports for your visit. If it is in the European Union, Iceland, Liechtenstein, Norway, the United Kingdom or Switzerland, you are asked first. A bar on the page has two buttons: Accept and Decline. One answer covers both the tracker and DataFast. Neither loads unless you accept.

Everyone else gets both without being asked. So does a visit with no country reported.

Some places report a country code of their own, so they are not asked today. They include the French overseas regions, Saint Martin, Saint Barthélemy, Åland, Gibraltar, Jersey, Guernsey and the Isle of Man.

Changing your answer

You can change your answer at any time on the privacy page, in the box under The contest traffic tracker. It covers DataFast too. The box shows your answer now, with Accept and Decline. One press changes it, and the box shows the new answer at once. Other tabs of this site that you have open follow the new answer.

If you are asked, the footer of each page has a Tracker choice link to that box. You can also delete the tracker_consent cookie in your browser.

Other sites your browser may contact

  • www.ship-or-die.com, on each page, if you get the tracker. Your browser loads the script from there and sends the details above.
  • datafa.st, on each page where you get DataFast. Your browser loads its script from there and sends the details above.
  • Stripe, at checkout.stripe.com, only when you go to checkout. Stripe sets its own cookies there, under its own rules.
  • Our radio server, at stream.emergent.fm and live.emergent.fm, only when you press play on the radio page.
  • Supabase, which holds our audio files, only when you press play on one of them.

On 18 November 2026, before we added DataFast, we checked ten pages. As they loaded, none of them contacted a site not on this list.

Emergent.FM is run by Red Sovereign LLC. Ask about cookies at legal@emergent.fm.