Skip to the text
JellyAtlas

Cookie Notice

Updated 18 August 2026 · Australian Capital Territory, Australia

Back to the atlas

This page lists everything jellyatlas.com stores in your browser. The list is short, and we would rather show it in full than describe it in general terms.

1. Cookies, local storage and why they differ

A cookie is a small file a site asks your browser to keep and send back on the next visit. Local storage and IndexedDB do something similar but stay in the browser instead of travelling with each request. All three are covered by this notice, because from your side they amount to the same thing: data held on your device by a website.

2. Strictly necessary

One entry, always present once you answer the consent bar.

  • userConsent — local storage, kept until you clear your browser data. Records whether you pressed Accept or Decline so the bar does not reappear on every page. Without it the site still works, but you would be asked again each time.

3. Analytics and measurement

None. There is no analytics tag on this site: no Google Analytics, no Meta pixel, no heatmap tool, no third-party measurement script of any kind. Visitor numbers, when we look at them at all, come from the plain access logs of our web host, described in the Privacy Policy.

4. Advertising

None. JellyAtlas carries no advertising banners and sells no placements, so there is nothing here for an advertising network to set. No third party places a cookie on this site for marketing purposes.

5. Notifications

Only after you agree. If you press Accept or submit the update form with the consent box ticked, our script loads the OneSignal web push library, which then keeps its own entries in your browser:

  • keys beginning with os_ — local storage, holding the subscription state for this browser;
  • ONE_SIGNAL_SDK_DB — an IndexedDB database holding the push token and delivery preferences;
  • OneSignalSDKWorker.js — a service worker registered in your browser so a notification can arrive while the tab is closed.

Until that moment, the OneSignal library is not requested at all. It is not in the page source and there is no script tag for it anywhere on this site; our own script adds it at the instant you consent, and not before.

6. What Accept and Decline actually do

Accept stores your choice, hides the bar and loads the notification library so your browser can ask you for permission. Decline stores your choice, hides the bar, and clears anything push-related that was already in the browser: the os_ keys in local and session storage, the consent key itself and the ONE_SIGNAL_SDK_DB database. Declining never limits what you can read; the atlas is identical either way.

7. Changing your mind later

  • Clear the site data for jellyatlas.com in your browser settings; the consent bar will greet you again on the next visit.
  • Block notifications for this site in your browser's permissions panel; that overrides any earlier Accept.
  • Chrome, Firefox, Safari and Edge all keep these controls under Settings, then Privacy or Site settings.
  • Write to team@jellyatlas.com and we will remove the subscription from our side as well.

8. Updates to this notice

If we ever add something that stores data in your browser, it will be listed here before it is switched on, and the date at the top will change. This version is current as of 18 August 2026. The rules for using the site are in the Terms of Use.