Legal · Updated November 8, 2026

Cookie Policy

This Cookie Policy explains how Audora uses cookies and similar technologies.

1. What Are Cookies?

Cookies are small text files stored on your device when you visit a website. They help websites remember your preferences, maintain your session, and understand how the site is used.

2. Cookies We Use

Audora uses only the following categories:

2.1 Strictly Necessary Cookies

Required for:

• Authentication
• Security
• Core platform functionality

These cookies cannot be disabled as they are essential for the service to function.

Audora also keeps some things in your browser's local and session storage: your sign-in session, your cookie choice, checkout progress, one-time invite links while you read the page, and the drafts of forms you have not saved yet, so a closed tab does not lose your work. It also keeps preferences you set, such as light or dark mode, the calendar view in Promo, to-dos you have hidden, and when you last opened Reach. None of these is sent to anyone else. Signing out removes the session, and clearing this site's data in your browser removes the rest.

Audora's own usage records. When you are signed in, each browser tab keeps a random session ID (audora.usage_session, in session storage, removed when the tab closes). It is first-party and strictly necessary for those records: it groups the records described in the Privacy Policy, section 4, which are kept in Audora's own database and never sent to anyone else. You can turn these records off in Account settings › Privacy & data › Product usage records.

2.2 Analytics Cookies

Used to:

• Understand platform usage
• Improve performance and stability

Audora uses Google Analytics 4, from Google, only if you accept analytics cookies. Until you do, no Google script loads. It sets two cookies, _ga and _ga_52E1HRK5VW, which keep a random ID for up to 13 months, so a return visit counts as the same visitor. Google receives the address of the page without anything after the "?", the page you came from (also without it), your browser and device type, and an approximate location derived from your IP address. We also send two events: when an application is sent and when an account is created, with the page you came from and the plan you chose. Google signals and advertising features are turned off. Rejecting, or turning analytics off in Account settings › Privacy & data, stops these events and deletes both cookies.

2.3 Application Source (Local Storage and One Cookie)

If you arrive on audora.music from another site — a search result, a link, a social post — Audora records the domain that sent you in a cookie named audora_src. It holds the domain only, never the full address, never an identifier, and it lasts 30 days. It is set on your first page here, because that is the only moment your browser tells us where you came from, and it is removed as soon as its value has been folded into the record below.

When you open the sign-in or application page, Audora keeps a small record in your browser's local storage (audora.landing) of how you reached it:

• The page on audora.music you came from, for example a guide
• The domain of the site that sent you, if any, for example google.com — never the full address
• Campaign tags in the link (utm_ parameters), if there were any
• The plan you chose before applying, if you chose one

The record contains no identifier. If you send an application, the record goes with it, so we can see which pages bring artists to Audora; if you do not apply, it never leaves your browser. It is no longer used after 30 days.

If you arrive through another artist's referral link, the referral code is kept the same way (audora.referral, 30 days) so the invitation can be credited to them when you create an account.

None of these records is used for advertising or shared outside Audora, with one exception: if you have accepted analytics cookies, the page you came from is included in the analytics event recorded when an application is sent or an account is created. You can remove them at any time by clearing this site's data in your browser; applying and signing up work exactly the same without them.

2.4 Players from YouTube and Spotify

Some pages show a video or song in a player from YouTube (through youtube-nocookie.com) or Spotify. The player loads only when you press play: the video on your Home page, and Listen or Watch on an artist's public page. Until then, nothing is requested from YouTube or Spotify: the picture shown before play is a copy kept on Audora’s own site. Once a player loads or plays, YouTube or Spotify may store cookies or other data in your browser under their own policies (the Google Privacy Policy and Spotify’s Privacy Policy). The YouTube player is part of the YouTube API Services, under the YouTube Terms of Service. Audora does not read these cookies, and you can clear them in your browser at any time. What YouTube and Spotify receive is in the Privacy Policy, section 6.6.

3. Consent

Audora applies EU-standard cookie consent mechanisms. When you first visit our site, a cookie banner allows you to accept or decline non-essential cookies. You can change your preferences at any time using "Cookie settings" in the site footer or, when signed in, in Account settings › Privacy & data.

Audora also honors the Global Privacy Control (GPC) browser signal. When GPC is detected, non-essential analytics cookies are automatically suppressed without requiring further action from you.

The cookie banner and the Global Privacy Control signal govern analytics cookies. The application-source records in section 2.3 — the audora_src cookie, audora.landing and audora.referral — are not analytics cookies and are not affected by either; you can remove them by clearing this site's data in your browser.

Note that disabling strictly necessary cookies via your browser settings may prevent the platform from functioning correctly.

4. Updates

This Cookie Policy may be updated to reflect changes in technology or law. Material changes will be communicated via the platform.