Skip to content
Audiobly OÜ · Legal

Cookie Policy

Which cookies Audiobly sets, what each one is for, how long it lasts — and why you are not being asked to accept anything.

Last updated
5 September 2026
Cookies we set
One
Tracking cookies
None
Contact
privacy@audiobly.com
The short version. Audiobly sets a single cookie, and it exists only to keep you signed in. We use no analytics, no advertising, no cross-site tracking and no third-party pixels. Strictly necessary cookies do not require consent under the ePrivacy Directive or the GDPR, which is why this site has no cookie banner — not an oversight, but the consequence of not tracking you.

01The cookie we set

NamePurposeTypeLifetimeAttributes
audiobly_refreshKeeps you signed in to the platform between visits, by allowing a new access token to be issued without re-entering your password.Strictly necessary30 days, or until you sign outHttpOnly, Secure, SameSite=Strict, scoped to the path /v1/auth

The cookie is HttpOnly, so no JavaScript on the page — ours or anyone else's — can read it. It is scoped to the authentication endpoints only, so it is not sent on ordinary API requests, which reduces both the exposure surface and the cross-site request forgery risk.

02Other storage in your browser

Your access token is held in the memory of the browser tab and is discarded when the tab closes. It is not written to a cookie, to localStorage or to sessionStorage.

The public marketing pages of this website set no cookies at all — you can read every page here without one being written.

03What we deliberately do not use

  • No analytics cookies — no Google Analytics, and no third-party analytics of any kind on the platform.
  • No advertising or retargeting cookies, and no advertising networks.
  • No cross-site tracking, tracking pixels, web beacons or device fingerprinting.
  • No social media plugins that set cookies on our pages.
  • No session replay or heat-mapping tools.

If that changes — if we add analytics, for example — we will update this policy and introduce a consent mechanism before setting any non-essential cookie, because at that point one would genuinely be required.

04Registration pages we host for organisers

Where an event organiser uses Audiobly to run registration, the public registration page may record referral information — such as the campaign parameters in the link a delegate followed — where that organiser has configured it. That organiser is the controller for those pages and for the data collected on them; their own privacy and cookie notices apply alongside this one.

05Managing cookies yourself

Every major browser lets you see, block and delete cookies through its settings, and offers a private browsing mode that discards them at the end of the session.

One consequence worth knowing. Because the only cookie we set is the one that keeps you signed in, blocking cookies for audiobly.com will not stop any tracking — there is none to stop — but it will stop you staying signed in to the platform, and you will be asked to log in again on every visit.

06Changes, and how to reach us

When we make a material change we will update the date at the top and publish the new version. Questions about this policy, or about anything else to do with personal data, go to privacy@audiobly.com. See also our Privacy Policy.