Resonance Privacy Addendum

Last updated: 2026-10-05Listening history, presence, country data, Discord presence, and local-library data specific to Resonance.

Resonance Privacy Addendum

This addendum describes the data practices that are specific to Resonance. It supplements — and does not replace — our general Privacy Policy: for what personal data we collect platform-wide, our legal bases for processing it, your GDPR rights, how to reach us about data requests, and cookies, see that policy.

This page covers what is particular to Resonance: your listening history, your library, presence ("now playing"), the country recorded with each play and what artists see of it, Discord Rich Presence, local tracks and their cover art, open-catalogue tracks whose audio and cover art come from Audius servers, connected services and playlist transfer, what ASAI can read about your listening, pairs, and the privacy settings that control all of it.

This addendum is published in good faith and is pending review by qualified EU/Estonian legal counsel; nothing here is a substitute for formal legal advice.

1. Listening history

Resonance records what you listen to — which tracks, when, and for how long — while you use the service. We use this history to:

  • Show you your own listening statistics and your daily listening streak;
  • Build personalised recommendations, including your "Made for You" selections;
  • Calculate the royalties owed to artists for plays of their tracks; and
  • Produce the aggregated audience figures that artists see for their own tracks (Section 4).

This history is tied to your account and is retained while your account is active. General account-data retention and what happens when you close your account are covered in Data Retention.

2. Your library

Your saved tracks, favourites, and playlists are stored against your account so they stay available across your devices and sessions. They are treated as account data under the general Privacy Policy and Data Retention schedule.

3. Presence — "now playing"

Resonance can show what you are currently playing.

It is off by default. Sharing your activity is switched off for every new account. Nothing about what you are playing is shown to anyone until you turn it on yourself.

We ask you, and we record your answer. The first time you open Resonance, a welcome window asks you — separately — whether to share your listening activity, whether to allow a public profile showcase, and whether to show your listening history. Each choice starts off. Every time you change one of these, in the welcome window or later in Settings, we write an entry to a consent record: what you changed, to what value, where you changed it, and when. We keep that record so that both you and we can show what you actually agreed to.

Who can see it once it is on. Please read this carefully, because there are two different surfaces:

  • The friends feed inside Resonance — the "friends listening" list — only ever shows people you follow and who follow you back. A one-directional follow shows nothing.
  • Your profile page is different. If your profile is public and you have activity sharing on, the track you are playing is shown to anyone who opens your profile, including people who do not follow you and people who are not signed in at all.

If you want the second one to be restricted too, use Hide profile in Settings → Privacy: with it on, your profile — and the presence on it — is visible only to you and to your mutual friends. You can also switch off "now playing" specifically, and leave the rest of your profile visible.

You can turn any of this off at any moment, and it stops immediately.

4. Country of listening, and what artists see

We record a country code with every counted play. It is stored alongside the play, and it is used to produce the geographic audience breakdown artists see for their own music.

Where the country comes from. It is taken from the country on your APERTURESyndicate profile, not from the address of each request. When you registered, the form suggested that country from your connection and you could change it; you can change or clear it in your profile at any time. If your profile has no country set, the play is recorded without one.

Regional availability. A few recordings are free to play only in some countries. When you press play on one of them, we check the country that our network provider (Cloudflare) derives from your IP address for that request and, if the recording is not available there yet, decline to play it. That country is used only for this check and is not stored with your plays.

What artists see. An artist can see, for their own tracks and releases, a breakdown of counts by country — how many listeners and how many streams came from each country. This is aggregated: it does not name you, and it does not tell an artist what else you listen to.

Two honest caveats:

  • There is no minimum-audience threshold on this breakdown. If you are the only listener from your country for a given track, that country appears with a count of one. In a small audience, that can be identifying — particularly combined with the top-listeners list an artist can see for their own tracks, which shows nicknames and avatars (a listener whose profile is hidden appears there as "Private listener").
  • Plays made in a private session are excluded from these artist figures entirely.

If this matters to you, a private session is the direct control, and you can also leave the country field on your profile empty.

5. Privacy settings

Settings → Privacy gives you direct control over what is visible to others:

  • Hide your entire profile — when enabled, your profile is visible only to you and to your mutual friends.
  • Independently of the above, you can show or hide, one by one:
    • Your listening statistics
    • Your streak
    • Your top/favourite track — this also controls whether your anthem and garland are served to other people
    • Your public playlists
    • Your listening-history section
    • Your "now playing" presence
  • On the desktop app, Discord Rich Presence (Section 6).

Each toggle applies immediately, can be reversed at any time, and is written to the consent record described in Section 3.

6. Discord Rich Presence and the OBS overlay (desktop app)

The Resonance desktop app can show what you are playing on your Discord profile.

What is sent to Discord: the track title, the artist name, the cover image address, playback timestamps, and a button linking to the track on Resonance that other Discord users can click. This data goes to Discord and is displayed by Discord to whoever can see your Discord profile — that is outside our control and is governed by Discord's own terms and privacy policy.

How it is switched on. The setting is off by default. It broadcasts only when you have switched it on and activity sharing is on (Section 3), which is off by default too. The toggle appears in two places, Settings → Desktop and Settings → Privacy, and only in the desktop app. Switching either of them off stops the broadcast.

Private sessions are never broadcast to Discord.

OBS overlay. The desktop app can also show what you are playing in your streaming software through a "now playing" overlay. It is off by default, runs only on your own computer at a local address that the streaming software reads, and sends nothing to us; what you then broadcast is up to you.

7. Local tracks, and their cover art

Audio files you add to Resonance from your own device ("Local Tracks") stay on your device, except in the cases listed below. We do not inspect or analyse their audio, do not use it for recommendations, and never add it to the catalogue.

These things about a local track can leave your device:

  1. Cover art you set yourself. If you give a local track your own cover image, that image is uploaded to our public media storage and served from a public, unauthenticated address, so it can be displayed in Listen Together and in your Discord card. It is stored under a name derived from the image's contents, and it is not indexed or listed anywhere, but it is not secret: anyone with the address can open it. The same applies to a cover from your Locker that is used in these features — a copy of it is placed in public storage.
  2. The title and artist, wherever you have chosen to share activity — the friends feed, your profile, Listen Together, or Discord.
  3. The audio itself, if you publish it as your profile anthem or in your profile showcase. That is a deliberate act with an explicit confirmation, and it is described in the Locker Policy.
  4. The audio, temporarily, in Listen Together. If you play a local track in a Listen Together room as its host or a controller, a temporary copy of the audio goes to our private storage so the others in the room can hear it. It is deleted when the room closes, and in any case within a few hours (Section 6 of the Resonance Terms of Service).

If you never set a custom cover, never share activity, never play a local track in Listen Together and never publish one to your profile, nothing that identifies your local tracks reaches us — only how long you listened, which counts towards your own streak and statistics.

8. Private sessions

You can mark an individual listening session as a Private session. A private session:

  • Still counts normally toward artist royalties and toward your own streak and statistics;
  • Is never added to your listening history;
  • Is never used as input to "Made for You" or any other recommendation;
  • Is never broadcast as presence — to your friends, to your profile, or to Discord — regardless of your other settings;
  • Is never sent to a connected listening-history service (Section 12);
  • Is left out of what ASAI can read about your listening (Section 13); and
  • Is excluded from the country breakdown and the top-listeners list artists see (Section 4).

9. Uploaded files

Files you upload to your Locker are covered by the Locker Policy, which sets out what is kept private and which of them — your anthem and your showcase — are deliberately public.

10. Identity

Consistent with the platform-wide rule, your internal handle is never shown to other users through any Resonance feature — not in profiles, presence, playlists, Listen Together, family rosters, or anywhere else. What other users see is your nickname and avatar.

This applies inside the Family plan as well: a family owner sees members by nickname and avatar only, and sees nothing about what they listen to. See the Premium & Subscription Terms.

11. Open-catalogue tracks (Audius)

The Resonance catalogue includes tracks by independent artists from the open Audius network (see Open Catalogue). Their audio is not stored with us: when you play one, your device loads the audio directly from Audius network nodes. The cover art of these tracks and their artists' profile images are also loaded from Audius servers — already when you browse the catalogue, search, or see a "now playing" card, not only when you press play.

Audius therefore receives your IP address and the technical data of the request — for example, details of your browser or app, the time of the request, and which file was requested.

Recipient: Tiki Labs, Inc. d/b/a Audius and the nodes of its network. Audius receives this data directly from your device, not from us, and processes it under its own Audius Privacy Policy. Network nodes may be located outside the EU.

We pass nothing else to Audius — not your account, not your nickname, not your listening history. We record plays of these tracks on our side the same way as any other (Section 1).

12. Connected services and playlist transfer

Your listening history in another service. In Settings you can connect a listening-history service. ListenBrainz can be connected today; Last.fm and Spotify can be connected only once we enable them, and until then the app marks them as unavailable. When you connect a service, we store the access token it gives us, encrypted, and use it only for that connection.

While a listening-history service is connected and not paused, each counted play — track title, artist, album, duration and time — is queued and sent to that service in your name from our servers. Plays in a private session are never sent. What happens to your history there is governed by that service's own terms and privacy policy. You can pause or disconnect at any time; disconnecting erases the token. Sent entries are removed from our queue about a month after sending.

Bringing a playlist in. You can create a Resonance playlist from a pasted list of tracks, from a public SoundCloud playlist link and — where we have enabled them — from a public YouTube playlist or a Spotify playlist of your own. Our server reads the titles and artists from that source and matches them against the Resonance catalogue. Only that metadata is transferred; no audio is downloaded.

13. ASAI and your listening

ASAI, the platform's AI assistant, can read a summary of your own Resonance listening when you ask it about your music: your total and recent listening hours, number of plays, streak, library size, top five artists and tracks, and your last five plays. It reads only the account of the person talking to it, and plays in a private session are left out. The summary becomes part of that conversation and is handled like the rest of it — see AI Data & Training. You can switch this off in ASAI under Settings → Privacy ("Let ASAI see your Syndicate account").

14. Pairs

If you and a mutual friend pair up — one of you invites, the other accepts — each of your profiles can show the other person: their nickname and avatar, how many days you have been paired and, as the pair continues, their anthem, their avatar beside yours, and a track you have both listened to. Anyone who can open your profile sees this, under the same visibility rules as the rest of it. Each of you can switch the anthem, avatar and shared block off in the profile editor, and either of you can end the pair at any time.

15. Rebellion

If you connect Resonance in the game Rebellion, the game reads your playlists and streams their tracks on your computer; the audio is held only in memory and is never written to disk. A catalogue track from which the game has actually played 30 seconds or more of audio counts like a play in Resonance — in your listening history, statistics and streak, and towards royalties (Section 1). The game has no private session, and it does not report plays of your own cloud files. What the game receives and what it never stores is set out in Rebellion & Resonance and the Rebellion Privacy Notice.

Contact

Operator APERTURESyndicate OÜ · Registry code 17384111 · VAT EE102972654 Priisle tee 8, Lasnamäe linnaosa, Tallinn, Harju maakond, 13914, Estonia Company registration details

This addendum is governed by the laws of Estonia, with the courts of Tallinn having jurisdiction, and is subject to the GDPR, the EU Digital Services Act, and applicable Estonian and EU consumer-protection law. The English-language version of this addendum is the controlling version.

Version history

  • v2.4 — 2026-10-05 — Section 15: Rebellion streams Resonance and keeps no copy on disk; a play counts from 30 seconds of audio actually played.
  • v2.3 — 2026-10-04 — New Section 15: Resonance in the game Rebellion — plays there count like plays in Resonance, and the game has no private session.
  • v2.2 — 2026-10-01 — New Sections 12–14: connected listening-history services (ListenBrainz now; Last.fm and Spotify once enabled) and playlist transfer, the summary of your own listening that ASAI can read when you ask, and pairs. Section 4: the profile country was suggested from your connection at sign-up, and for the few region-restricted recordings we check the country of the request without storing it. Section 6: Discord presence is now off by default; the OBS overlay is described. Section 7: playing a local track in Listen Together uploads a temporary copy of its audio, and the time you spend listening to local tracks counts towards your own statistics. Section 8: private sessions are not sent to connected services or included in what ASAI reads.
  • v2.1 — 2026-09-26 — New Section 11 on Audius open-catalogue tracks: their audio, cover art, and artist images load directly from Audius network servers, so Audius (Tiki Labs, Inc. d/b/a Audius) receives your IP address and the technical data of the request and processes them under its own privacy policy. We do not pass your account, nickname, or listening history to Audius.
  • v2.0 — 2026-07-31 — Presence is now documented as it actually behaves: off by default, asked for in the welcome window, written to a consent record — but visible on a public profile to anyone, not only to mutual friends as previously claimed. Newly disclosed: the country code recorded with every play and the per-country breakdown artists see, including its lack of a minimum-audience threshold; Discord Rich Presence and exactly what it sends; and the fact that cover art for local tracks is uploaded to public storage, which the previous "local tracks never reach us" wording contradicted. Corrected private sessions (there is no daily quota any more) and added their exclusion from artist geography.
  • v1.0 — 2026-07-02 — Initial publication.
Resonance Privacy Addendum | AS Docs