Cookie Policy

1. What cookies and similar technologies are

A cookie is a small text file that a website asks your browser to store and to send back on subsequent requests. Cookies are how a conventional site remembers that you are logged in, what is in a basket, or which language you chose. They can be set by the site you are visiting ("first-party") or by another domain whose content is embedded in the page ("third-party"), and they may last only until you close the browser ("session") or for a defined period ("persistent").

Several related technologies do similar jobs:

• Local storage — a small key-and-value store held by your browser for a particular site. Unlike a cookie, it is never attached to network requests; it is only readable by pages from the same site, running in your own browser.
• Session storage — the same idea, but cleared when the tab closes.
• Pixels and web beacons — tiny embedded images used to record that a page or an email was opened.
• Fingerprinting — inferring an identifier from the characteristics of your device and browser rather than storing one.

Of all of the above, this site uses exactly one: a single local storage key, described in section 3. It uses no cookies, no session storage, no pixels, no beacons and no fingerprinting.

2. The usual categories

Storage on a website is conventionally sorted into three categories. It is worth setting them out so that you can see which ones apply here.

• Strictly necessary. Required for the site to function — session identifiers, load balancing, security tokens, consent records. These usually do not require consent because the site cannot work without them. This site sets none: it is a set of static pages with no session, no login and no basket.
• Functional. Remember a preference you expressed — a language, a theme, a filter — so the site behaves the way you last left it. This site uses exactly one, described below.
• Analytics and marketing. Measure audience behaviour, attribute traffic, build profiles, or target advertising. This site uses none. There is no analytics product, no advertising pixel, no tag manager, no session recorder, no heat mapping and no social media tracker anywhere on it.

3. What this site actually stores

Here is the complete list. It is one row long, and we would rather publish a short honest table than a long generic one.

The value stored is one of four short words: all, tables, chips or materials. It contains no identifier, no personal data and nothing derived from you. It never leaves your browser: local storage is not transmitted with network requests, and the site has no server-side code that could read it. If your browser blocks storage, or you use private browsing, the filter still works — it simply starts from "Everything" each time.

No other key, cookie or storage entry is created by this site. If you inspect your browser's storage for bringbackourgirls.org and find something else, it did not come from us — please tell us at [email protected].

4. Why there is no consent banner

Consent banners exist because most sites set cookies that require consent — analytics, advertising and profiling technologies that the UK Privacy and Electronic Communications Regulations (PECR) and the UK GDPR, like their EU equivalents, treat as needing a freely given, informed opt-in before they are placed.

This site has nothing in that category:

• it sets no cookies of any kind;
• it runs no analytics, advertising or profiling technology;
• the single local storage key it writes is a functional preference, written only as a direct result of you clicking a filter button, and containing no identifier.

Showing a consent dialog in those circumstances would ask you to consent to something that does not happen. We think that is worse than useless: it trains people to dismiss dialogs without reading them, and it implies a level of data collection that is not taking place. So there is no banner, and this page exists instead.

If that ever changes — if we were to introduce analytics, for example — we would ask for consent properly, before anything was set, and we would say so on this page first.

5. Third-party fonts

One third party is involved in loading this site. The Manrope typeface is requested from Google Fonts when a page loads.

That request does not set a cookie and does not store anything in your browser. It does, however, necessarily disclose your IP address, your user agent string and the referring page to Google, which acts as an independent controller in respect of that request under its own privacy policy. This is the same exchange that occurs whenever any resource is loaded from another domain.

If you would rather not make that request, a content blocker set to block fonts.googleapis.com and fonts.gstatic.com will prevent it. The site is built to remain fully legible and fully functional on the fallback system typeface; nothing but the shape of the letters changes.

No other third-party resource is loaded anywhere on this site. There are no embedded videos, maps, chat widgets, social buttons, comment systems or externally hosted images — every illustration is a local file drawn in-house.

6. Managing cookies in your browser

Even though this site sets no cookies, you may wish to review or restrict what other sites store. Every major browser allows this. The paths below were accurate at the date at the top of this page; browser menus change from time to time.

Google Chrome

Menu (⋮) → Settings → Privacy and security → Third-party cookies to control cookie behaviour, or Delete browsing data to clear what is already stored. Per-site controls are under Site settings → View permissions and data stored across sites, where you can also remove a single site's data.

Mozilla Firefox

Menu (☰) → Settings → Privacy & Security. Use Enhanced Tracking Protection to choose a blocking level, and Cookies and Site Data → Manage Data… to inspect or remove what an individual site has stored.

Safari (macOS)

Safari → Settings → Privacy. "Prevent cross-site tracking" is on by default; Manage Website Data… lists what each site has stored and lets you remove it. On iOS and iPadOS, go to Settings → Apps → Safari → Clear History and Website Data.

Microsoft Edge

Menu (…) → Settings → Cookies and site permissions → Manage and delete cookies and site data. See all cookies and site data lets you search for a single site and remove its entries.

Blocking all storage will affect many websites that genuinely need it, and may make it impossible to stay signed in anywhere. It will not break this site.

7. Clearing this site's local storage

To remove the one key this site writes, clear site data for bringbackourgirls.org using the per-site controls described in section 6. In Chrome, Firefox and Edge you can also open developer tools (F12), go to the storage or application panel, select local storage for this site and delete the atl:products-tab entry directly.

Removing it has no consequence beyond resetting the product filter to "Everything" on your next visit. It is not used for anything else, and nothing about your visit depends on it.

8. Changes to this policy

If the storage this site uses ever changes, this page changes with it — the table in section 3 is meant to be exhaustive and current, not indicative. The "Last updated" date at the top of the page shows when it was last revised.

Any addition that required consent would be announced here and would be requested before it was set, not after. We would rather keep this page boring.

9. Contact

Questions about this policy, or about anything you have found stored by this site: [email protected].

See also our Privacy Policy for how personal data is handled more generally, and our Legal Information page for the identity of the site operator.

Sport Casual Limited, 7 Grove Park Road, Wrexham, Clwyd, LL12 7AA, United Kingdom.