Cookie notice

This notice explains the limited use of cookies and similar technologies on the current Atlas51 website.

Read this alongside our Privacy Notice, which explains how we handle your personal data more broadly.

1. What cookies are

A cookie is a small text file that a website places on your device when you visit. It is read back by the website on subsequent visits. Cookies serve different purposes: some are necessary for the site to function; others help us understand how it is used; others support advertising.

This notice also covers similar technologies — including local storage and pixel tags — that work in comparable ways.

2. Your cookie choice

We use a first-party preference record called atlas_consent to remember your Analytics and Marketing choices. It is stored in a cookie and in local storage on your device. The cookie is set for 180 days; the local-storage copy helps us restore your current choice where a browser does not make the cookie available. This record is not used for advertising or cross-site tracking. Both choices are off until you turn them on, and each works independently of the other.

Brochure downloads. After we record your brochure request, a necessary first-party HttpOnly cookie named atlas_brochure_<trip-slug> lets this browser download that trip’s private PDF for one hour. It contains a random grant, not your email address, and is used only to provide the download you requested. It does not enable analytics or subscribe you to marketing.

Saved trips on this device. When you use Save in the film reader, we keep your chosen trips in local storage as atlas51_saved_trips. This holds only references to those trips, not your name, contact details or an analytics identifier, and is not sent to Atlas51 or shared between devices. We write it only when you save or remove a trip. It works independently of your Analytics and Marketing choices and stays until you remove the trips or clear site storage.

The newsletter card. While you read, the site may show a card inviting you to subscribe to Stories from the Field. If you close the card or sign up through it, we save that answer in local storage as atlas_prompt so that we do not show it to you again for a while. It holds a count and a date, never your email address. We write it only when you close the card or sign up, not when the card is merely shown, and it works whatever your Analytics and Marketing choices. Clearing your site storage removes it.

3. Analytics, only with your consent

Until you make an affirmative Analytics choice, the Google tag is not loaded and no Google Analytics data is sent. The page sets a denied-by-default Google Consent Mode state only; that does not load Google or send a request to it.

If you allow Analytics cookies, we set a random visitor identifier (atlas_anon_id) and a record of how you arrived (atlas_attribution), and we load Google Analytics 4 (GA4). The arrival record holds the campaign tags or referring website, the page you landed on, and any advertising click identifier carried in the link you followed, so that we can tell which campaign produced an enquiry made days later. GA4 measures the pages and trips you view, the catalogue filters you use, the trip cards and links you click, how far down a trip page you read and which sections you open, film playback and completion, page sharing, the website a link takes you to when you leave us, form starts, the step at which a form failed and whether a submission succeeded, whether a brochure request succeeded and whether you clicked its download link. Those events name the trip and the type of action; they never include what you typed into a form, your name, email address, phone number or message.

With Analytics consent, our games also send coarse events for game loading, starts, retries, completion or failure, sharing and active play time. These events do not include your route trace, score table, name or other free-text entries.

Basic game play counts, separately from Google Analytics. To understand use of and improve our games, we keep one daily total of run starts for each game, including full restarts. Pausing or recovering at a checkpoint does not add another play. The count request contains only the game name. The totals contain no visitor identifier, IP address, referrer or individual play history, and are not used for advertising. They are approximate play totals, not unique-player counts. Our hosting providers still process ordinary connection information to deliver and protect the website; this is separate from the aggregate counter.

Basic counts work without Google Analytics consent. You can object at any time, free of charge, using Game play counts; the same link is available in both games before play and when paused. We also respect browser Do Not Track and Global Privacy Control signals. We store only your requested on/off preference in atlas_game_play_counts local storage until you change it or clear site storage. No default preference or tracking identifier is written. Your choice applies to future starts in that browser; daily totals cannot be linked back to or removed for a particular person.

We do not use Google Ads or session-replay technology. We will update this notice and ask for an appropriate choice before introducing a new non-essential technology.

4. Marketing, only with your consent

If you allow Marketing cookies, we load the Meta Pixel from Meta Platforms. It is used only when you allow Marketing cookies; before that, no Meta script loads and nothing is sent to Meta, whatever your Analytics choice. The pixel records the pages and trips you view and whether an enquiry, application or Field Notes sign-up succeeded, so that we can measure advertising on Meta's platforms and, in time, show relevant adverts there. It sets Meta's own cookies on our site. We do not send Meta your name, email address, phone number or anything you typed into a form, and we do not use advanced matching.

5. The cookies we use

6. Managing or withdrawing your choice

Use the Cookie settings link in the site footer at any time to change or withdraw Analytics or Marketing consent. Withdrawing Analytics stops further GA4 measurement; withdrawing Marketing stops the Meta Pixel sending anything further. You can also delete the atlas_consent cookie and local-storage record through your browser settings. Deleting or blocking cookies may affect the functionality of this and other websites.

Via your browser: Most browsers allow you to view, block, or delete cookies through their settings menu. Links to browser cookie-management guides:

• Chrome: support.google.com/chrome/answer/95647
• Firefox: support.mozilla.org/en-US/kb/cookies-information-websites-store-on-your-computer
• Safari: support.apple.com/en-gb/guide/safari/sfri11471/mac
• Edge: support.microsoft.com/en-us/microsoft-edge/delete-cookies-in-microsoft-edge

7. Google, Meta and international transfers

Google provides GA4 and Meta Platforms provides the Meta Pixel. If you allow Analytics or Marketing cookies, Google or Meta may process the resulting information outside the United Kingdom. Our Privacy Notice explains the safeguards we use for international transfers and how to ask for more information.

8. Changes to this notice

We review this notice when our use of cookies changes. The date at the top of this page shows when it was last updated.

9. Questions

If you have questions about how we use cookies, contact us at tommy@atlas51.co or write to us at our registered office: 2 Beeches Road, London, England, SW17 7LZ.