Privacy Policy
The short version
- We do not sell your personal information. Ever.
- We run no third-party advertising: no ad network, no advertising identifier, and nothing about you shared with advertisers. The only promotions you will ever see here are Retaz's own.
- Retaz is an 18-and-over product.
- Retaz hosts no music. Playlists are lists of track references, and playback happens in your own streaming service.
- Your account data is stored in the United States (Section 11).
- Public playlists, with your display name or @handle, can be seen by anyone, including on retaz.fm, where search engines can find them (Section 2).
- Direct messages are stored on our servers and can be read by our safety team. They are not end-to-end encrypted.
- You can export your data and delete your account at any time, from inside the app or by email. A few records stay after you delete your account, and Section 7 lists them.
This policy explains what Retaz LLC ("Retaz", "we", "us") collects, why, and what your rights are. It covers the Retaz mobile app for iPhone and Android, the retaz.fm website (including its former waitlist), and the journalists and music creators we contact about Retaz. It describes what Retaz does today, not what it might do later. If we add features that change what we collect, we will update this policy first.
1. Who we are
Retaz LLC is a West Virginia limited liability company headquartered in Lewisburg, Greenbrier County, West Virginia, USA. For anything in this policy, contact info@retaz.fm.
2. What we collect in the app
You sign in to Retaz with your Apple or Google account. There is no email-and-password sign-up. When you use the app, we collect:
- Email address. Provided by Apple or Google when you sign in. If you use Apple's private relay, we receive the relay address, which is fine with us.
- Your name from Google or Apple. If you sign in with Google, Google also gives us the name and the profile picture address on your Google account, and our sign-in service may keep them with your sign-in record. We use the name only to suggest a display name. If you sign in with Apple, Apple may share your name with the app, which does not keep it.
- Display name. The name other people see. We suggest one from your Google name or from the first part of your email address, and you can change it. It does not have to be unique.
- Unique handle. The @handle other people see. You pick it at sign-up, it is unique to you, and you choose whether your handle or your display name is shown by default. If you change your handle, we keep the old one with your account identifier, so that no one else can take it straight away.
- Account identifier. A random ID that ties your data to your account.
- Country, and optionally a state, province or region and a city. Profile fields you pick, not location readings: your phone's region setting suggests a country, which you can change. We do not collect device location. If your country is Ukraine, the app asks for your region. Your country, and for Ukraine your region, decide whether you can be recognized in La Chispa, and you cannot change them in the app while La Chispa runs (La Chispa Rules 7.7).
- Changes to your country or region. When you set or change your country or your state, province or region, we keep a record of the old and new values, when it happened, and whether you or we made the change, to review La Chispa eligibility (La Chispa Rules 7.7). You cannot see this record in the app, but it is in the in-app export (Section 9). The record is deleted with your account (Section 7).
- Social-platform handles. Any usernames you choose to add to your profile for other platforms. These are optional.
- Profile avatar. Avatars are built-in artwork. We store the short key of the preset you pick, and any initials (up to three), color and flag you add to it, never an uploaded photo.
- Language preferences and locale. So Retaz can speak your language.
- Birth year and a minor flag. To apply our 18-and-over rule, the app asks for your birth month and year, never the day. It checks your age on your phone and keeps only the year: the month is not stored. This is self-declared. We also store a minor flag derived from the year. Because the minimum age is 18, that flag should never be set on a live account: we keep it as a safety check so that a wrongly-entered birth year is caught rather than ignored. On an iPhone with iOS 26 or later, the app also asks Apple's Declared Age Range service for your Apple Account's age range. You can decline to share it; if it shows you are under 18, you cannot continue. We do not store Apple's answer.
- Two declarations for La Chispa Country Champions (from November 17, 2026). If your playlist leads its country when La Chispa closes, we may ask you for a written declaration of a legal name for the sanctions screen and any contract, and confirmation of where you live at the close and the date of any move. We send the request after the tally is captured, in the same words to everyone missing the same item, and we never ask for an identity document. We do not give your legal name to the independent observer (see Section 6).
- Content you create. Playlists (titles, descriptions, the "why" text, hashtags, track lists, and the visibility setting you choose), comments and replies, communities you create, posts you write in a community and songs you suggest for one (see "Communities" below), your curator bio, feedback you submit, and translation suggestions you offer.
- Publish attestation. When you publish a playlist you affirm that you made it yourself. We record the time of that affirmation and the terms version you accepted.
- How you interact. Votes (hearts), saved and bookmarked playlists, songs you like and songs you mark as "not for me", curators and Scenes you follow, communities you join and the hearts you give community posts, people you block, reports you file, comments you post, and direct messages you send. Because hearts decide La Chispa, each heart you give or withdraw is also written to a separate record that no one can change, with your account identifier, the playlist and the time (Section 7).
- Founders, referrals and badges. Whether you are a Founder (you signed up before October 15, 2026); your referral code and, if a member referred you, which member; and your Curator badge, the other badges awarded to you and the ones you pin. Other members can see your Curator badge and your pinned badges, and signed-in members can see whether you are a Founder.
- Technical data. Our sign-in service records the IP address and device type of each session. Our hosting platform's logs record IP addresses, device types and the addresses the app requested, which can include your account identifier or what you searched for; these logs are kept for 7 days.
- Report submissions. If you report content, we store which item you reported and the category you chose from a fixed list of 12. Reports cover playlists, profiles, comments, direct messages, communities, and community posts. The report form has no free-text field.
Who can see your profile and what you publish
Any member who is signed in can see your display name, handle, avatar, curator bio and Curator badge. If your profile is public, they can also see your country, region and city, the links to your other profiles, and your privacy settings. Turning your profile private hides those from your profile and keeps your name off lists such as a community's members and out of search, except that someone who types your exact @handle finds you and sees your country. Your public playlists still show the country and region they belong to. Your email address, birth year and referral details are never shown to other members.
Some things can be seen by anyone, signed in or not: your public playlists, with their title, note and your display name or @handle, and the comments on them; your curator bio; and, if your profile is public, a curator page with your display name or @handle, country, badge and number of public playlists. retaz.fm shows pages for shared playlists and curators. Signed-in members can see the full La Chispa leaderboard, and anyone can see its top five, worldwide and in each country, with each playlist's title, its curator's display name or @handle and the curator's declared country. Search engines and AI crawlers can index the pages on retaz.fm, and copies they keep are outside our control.
Direct messages
Retaz includes one-to-one direct messages. If you and another member follow each other when your conversation starts, your messages go straight to them. If you do not, your messages arrive as a message request: the other member sees who sent it and what it says, and can accept it, decline it (you are not told), block you, or report it. A member can turn off new message requests in the app's privacy settings, and when either of two members has blocked the other, neither can message the other. From October 15, 2026, both members need a membership to send or receive direct messages. A message can be between 1 and 4,000 characters.
Please read this part carefully. Your direct messages are stored on our servers in readable form. They are not end-to-end encrypted. Our safety team can read message content when reviewing a report or acting to keep the community safe, and messages are translated automatically into the reader's language (see "Automatic translation" below). Before you start your first conversation, the app shows you a notice that explains this and asks you to agree. You can report a direct message the same way you report anything else (Section 8). If either of you deletes your account, the whole conversation is deleted, both sides (Section 7).
Communities
A community is a group a member creates around the music they love, with a feed of posts. Anyone signed in to Retaz can look around a community without joining. From October 15, 2026, creating a community, joining one, posting, giving a heart to a post and suggesting a song need a membership. When you use Communities, we store:
- Communities you create. The name, the avatar you pick from the Retaz library, the description, any house rules, the primary genre, up to three hashtags, the language, and the anchor playlist (one of your own public playlists), with when you created it. You are shown as its owner wherever it appears.
- Your memberships. Which communities you belong to and whether you own each one; when you joined; when you agreed to the Retaz guidelines that every community follows, and to the community's house rules, which everyone must do to join or create a community; and when you last posted or gave a heart there, so the app can show your most recent communities first.
- Posts. A post is one song from the Retaz catalog and a caption of up to 250 characters, with no links. We store the caption, the song, who wrote it and when.
- Hearts on posts. One per member per post: which post, and when. A heart on a post is its own record. It is not a heart on a playlist, and it never counts in La Chispa.
- Song suggestions (the Soundboard). When a community has a Community playlist, its members can suggest a song for it, with optional thoughts of up to 250 characters and no links. We store the song, who suggested it and when, the thoughts, and whether the suggestion is waiting, added, declined, withdrawn or expired (a suggestion expires after 30 days). When a song is added to a Community playlist, we record who added it.
- Co-curators. A community's owner can invite members who have joined it to co-curate: to review suggestions and add songs to the Community playlist. Only a member who holds a membership can be invited, and the app tells the owner when someone they choose does not hold one. We store who was invited, by whom and when, and whether they accepted or were removed.
- Invitations to join. A community's owner and its co-curators can invite a member who holds a membership to join. To find someone, they search by name or @handle under the same rules as people search (a private profile is found only by its exact @handle), but only members who hold a membership are shown. For each, they see a name, @handle and avatar, and whether that member is already in the community or has already been invited; members who have blocked each other cannot find or invite each other. We store the community, who was invited, who invited them and when, and whether and when the invitation was declined. An invitation is deleted when you join; an open one has no expiry; a declined one is kept while the community and your account exist, so that community does not invite you again. If the member who invited you deletes their account, the invitation stays without their name. An inviter can send at most 20 invitations a day.
- Requests to join. An owner can turn on approval to join. You then ask to join; we store the community and when you asked, and the owner and the co-curators see your request. It is deleted when it is answered, when you cancel it, after 14 days, or with your account. You are told if it is approved; if it is declined, no one is told.
- Private communities. Communities are public unless their owner makes them private. A private community is left out of Discover, Trending and search, and out of the communities other people see on its owner's profile, and only its members see inside it ("Who can see what", below). Private means private from other members, not from Retaz: reports and our safety team's review still reach inside it.
Who can see what. Everyone signed in to Retaz can see a community's name, avatar, description, house rules, genre, hashtags, language, anchor playlist, owner and number of members, and can read its posts. Each post shows its author's display name or handle and avatar, when it was posted, its song and its number of hearts. The app never shows who gave a heart to a post, not even to the community's owner; it shows you only whether you gave one. Anyone signed in can also open a community's list of members, which shows each member's display name or handle and marks the community's owner. Members whose profile is private, and members you have blocked or who have blocked you, are counted but not named. A private community shows all of this, and its Community playlist, only to its members; anyone else who reaches it, through an invitation or a link, sees no more than its name, that it is private and whether joining needs approval. The list of communities you belong to is shown only to you. The thoughts you add to a song suggestion are seen only by you and the community's curators, who also see your name with the suggestion if your profile is public. Each song on a Community playlist shows signed-in members who added it, by name if that member's profile is public and neither has blocked the other, and otherwise without a name. The community shows its owner as Curator and its co-curators as Co-Curator, and only the owner sees who has been invited to co-curate. Anyone who opens a community's invite link, signed in or not, sees the community's name and, for a public community, its number of members; nothing else about a community is shown to anyone who is not signed in. When either of two members has blocked the other, neither sees the other's posts or the communities the other owns.
Flags and removals. Anyone who can see a community or a post can flag it, and a flag is a report (Section 8). When three different members have flagged the same post, it is hidden from everyone but its author until our safety team has reviewed it; a flagged community stays visible while we review it. A community's owner can remove any post in their community, and must give a reason to remove someone else's. We keep that reason, who removed the post and when, and a record of each time an owner deletes or restores their community, so that our team can review how owners use these tools. The reason is not shown in the app.
Leaving and deleting. You can leave any community you joined; your posts and hearts there stay, and you can still delete your posts. A deleted post disappears from the community at once, whether its author deleted it or the owner removed it, and we keep it out of sight, so that a report about it can still be checked, until the community is erased or its author deletes their account. An owner cannot leave their own community but can delete it: it disappears for everyone at once, and the owner can restore it from My Corner for 72 hours. When the 72 hours are up, it is erased within the hour, with its memberships, posts, hearts on posts, invitations and requests to join and the record of owner actions. Reports about it or its posts stay with our safety team (Section 8). If you delete your account, the communities you own are erased at once with everything in them, including other members' posts, and your memberships, posts and hearts in other communities are deleted with the rest of your data, subject to "What we keep after you delete your account" (Section 7).
Discover and Trending. Discover's "Your genres" list shows communities whose genre or hashtags match the hashtags on your own playlists and on the playlists you have hearted, and names the hashtag that matched; it does not use your listening history. Trending lists the communities with the most joins, posts and hearts on posts in the last 48 hours. Its "Your Country" and "Your Area" lists compare the country, and the state, province or region, on your profile with those on each community owner's profile, so if you create a community, members whose profile names the same country, or the same region, can find it there, even when your profile is private. Both lists are worked out each time you open them, and are not stored.
Posts, community names, descriptions and house rules are shown as written: they are not sent for automatic translation. Invite links and shares go through your phone's share sheet: they carry the community's name and its own link on retaz.fm, with your invite code in the link if you are a Founder, and we are not told who you send them to. On a phone without Retaz, the link goes to the App Store or Google Play; on Android, Google Play hands the community and the code to the app when it is installed, so it can open that community. Your communities, memberships, posts, hearts on posts, song suggestions and co-curator roles are in the in-app export (Section 9).
Automatic translation
Comments and direct messages are translated automatically into the reader's language for members who hold a membership. Only the text and the reader's language are sent for translation, never your name or account details; Section 6 names the two services that do this. Translations are stored so the same text is not translated twice, and they are deleted when the original comment or message is deleted, and in any case after 90 days.
Notifications
Retaz can send you these notifications: when you earn your Curator badge; when your playlists get new hearts, at most once a day and never saying who hearted; when someone comments on one of your playlists, with the commenter's handle and how many comments are new; when someone replies to your comment, with their handle; when a song you suggested is added to a Community playlist; when you are invited to co-curate a community, with the name of the member who invited you; when someone you invited to co-curate a community accepts or declines; when you are invited to join a community, with the name of the member who invited you; when someone answers your invitation to join; when your request to join a community is approved; when a member sends you a direct message, unless the conversation is still a message request, with their name or @handle and how many messages are waiting, never the message itself; and four La Chispa notices, sent to everyone with notifications on: when La Chispa opens (October 17, 2026), three days and one day before it closes (November 13 and 15, 2026), and when the Global Champion is announced (December 1, 2026). Notifications are off unless you turn them on, with "Notify me when I earn it" on the Curator badge card or with the Push notifications switch in Settings, and then allow notifications when your phone asks. Nothing is sent to your phone, and no notification address is stored, until you do both.
When you turn them on, we store a push token for your device. A push token is an address your phone's notification service gives us so a message can reach that device. It is not a name, an email, or a location, and it cannot be used to read anything on your phone. We store one per account and use it only to send you the notifications listed above. We never use it to advertise anything else, we never sell it, and we share it only with Expo to deliver those notifications (Section 6). Turning the Push notifications switch off in Settings deletes it from our servers at once, and so does signing out. If you turn notifications off in your phone's settings instead, the address stops working, but we delete it only when a notification to it fails, when you sign out or when you delete your account.
The app also keeps a list of the notifications we have sent you, under Notifications in Mail. Notices about your badge, your hearts, comments and replies, songs you suggested, invitations to co-curate and the answers to yours appear there even if notifications are off on your phone. Three kinds appear only there and are never sent to your phone: new song suggestions and new requests to join for a community you curate, and changes to this policy. Message alerts are the opposite: we never add them to the list, because the conversation itself is the record; with notifications on, they go to your phone. Each entry holds what the notice says and when it was sent, and is deleted after 90 days, or with your account.
Crash and performance reports
When the app crashes or hits an error, we receive a technical report so we can fix it. A report contains the error itself, where in the app it happened, the screen you were on and a short trail of the app's activity just before it, and basic device information such as the model, operating system and app version. A share of app activity is also sampled for performance timings, so we can find what is slow.
Reports can include your account identifier, so we can tell which account a problem affected: from app version 1.0.19, the app adds it while you are signed in and removes it when you sign out. They never include your name, email address, IP address, cookies or request headers, and a web address in a report keeps only the site and the path, with identifiers taken out of it and never the part after a "?". They are technical diagnostics about the software, not a record of what you listened to or who you talked to. Sentry keeps them in the United States, for the periods in Section 7.
Your listening activity (Last Spin and Tuned In)
When you open a playlist to play it, we record that you opened it (we call this a spin). Your own spin history is private to you. We use it to show you Last Spin (your recent listening) and to power Tuned In, which surfaces playlists that other people have put together. This is our own product data. We do not send it to any outside analytics or advertising service, and it is never used to target ads.
Finding songs, importing and exporting
Retaz hosts no music. To find a song, the app or our server asks a music service's catalog, which receives your search or the link you pasted, never your Retaz account identifier, name or email. A link you paste to add a song is stored as you pasted it, including any tracking codes the sharing service added to it, and anyone who can see the playlist can see the link. We also record which country's Apple Music catalog your phone checked a song in, and other signed-in members can read it.
If you connect Apple Music, Deezer or SoundCloud, your sign-in to that service stays on your phone, encrypted, and we do not keep it. Importing a playlist reads it from your account at that service. Exporting a playlist sends that service its title, its note and its songs, from your phone. An export to Apple Music adds "Curated by @yourhandle on Retaz" to its description unless you turn that off.
Our own product counters
To understand how the app is used without any outside analytics service, we record, for your account, the first time certain things happen: for example, that the membership offer was shown to you, that you started a purchase and whether it completed or failed, which music service you chose, and that you connected Apple Music. We also keep totals, which identify no one. Only Retaz can read them, no analytics or advertising company receives them, and the marks for your account are deleted after 12 months, or with your account.
The operations log and our automated checks
To keep the service, its voting and its moderation honest and working, our database writes an event to an operations log when members sign up, publish, give a heart, file a report or send feedback. Most events identify the member by a code instead of the account identifier, but sign-up events, and reports about a member, carry the account identifier itself. A sign-up event also records the member's country, language setting and whether they are an adult (never the birth year), and a heart records the playlist, the time, and the code and country of the member who gave it. The log never contains names, handles, email addresses or the text of anything you write. Automated agents, AI models we run on Amazon Bedrock in the United States, can be given these events to summarise them and to flag anything unusual for a founder to review. One of them checks hearts: it reads the hearts given in each five-minute window as these coded records, in Amazon's United States regions only, and flags patterns that look coordinated for a founder to review. It never counts, holds or strikes a heart. The agents cannot look anything else up, and they never make a decision about you. The log is kept after you delete your account (Section 7).
Messages from Retaz about Retaz
Retaz has a free tier and a paid membership. On the free tier, importing or exporting a playlist is never followed by a message from Retaz, and neither is the first playlist you publish; after that, each time you publish another playlist, we show you a short message about Retaz once it has been published. The action always completes first: the message never blocks it, and you can dismiss it after three seconds.
This is Retaz talking to you about Retaz. There is no advertiser, no ad network and no advertising software involved, nothing about you is sent anywhere, and no advertising identifier exists in the app. The message depends only on the fact that you just published a playlist.
To make the free allowance work, we keep a small count on our own servers of how many playlists you have published. It is a counter attached to your account, nothing more, and we keep it on our servers rather than on your phone so that reinstalling the app does not quietly reset it. Paid members are not counted at all. The count is deleted with your account.
Your membership
We never see your card. Apple or Google handles every payment for a membership bought in the app, through the store you buy from. Your card number does not reach Retaz, and we could not store it if we wanted to.
What we do keep is a record of the membership itself: that you have one, when it starts and ends, how it was acquired (a purchase, a Founders place, a referral, a press year, or a benefit you earned), the price tier and, for App Store purchases, the amount charged and its currency, whether a purchase was real or a store test, when a refund ended it or a reversed refund restored it, and the transaction identifier the store gives us. When you buy, the app also gives the store a reference to your account so that the purchase can be matched to it: Apple receives your Retaz account identifier, and Google receives a one-way hash of it. We use the record to know whether your membership is active, to recognise a renewal or a refund, and to reconcile our own figures against what the stores report. When Apple or Google confirms a refund, we end that paid period automatically, and under the La Chispa Rules the hearts given during it stop counting, as do hearts an account gives after a store test purchase (Section 9 says how to ask a person to review this). The record is deleted with your account.
3. What we do not collect
- Location. No device location, ever. Your profile country, and any state, province, or city, are fields you pick yourself.
- Contacts, photos, or audio. The app does not read your contacts, upload photos, or record audio.
- Music files. Retaz hosts no audio. Full tracks play only through your own Apple Music subscription, and short previews are provided by Apple. Playback happens through links into your own streaming service.
- Card and payment details. Retaz never sees them. Apple or Google handles every payment for a membership bought in the app. What we keep is the membership record described in Section 2 under "Your membership", never a card number.
- Advertising or tracking identifiers, third-party analytics, or advertising profiles. The app sends none of these, and we use no advertising identifier. (We do keep a private record of the playlists you open, described in Section 2. It stays on our own systems and is never used for advertising.) We do use a crash-reporting service, named in Section 6 and described in Section 2; it is not an advertising or analytics tool and it receives no advertising identifier. Our own product counters (Section 2) stay on our own systems too.
- Anything for an advertiser. There is no ad network in Retaz and no advertising software from anyone else. Retaz does show you messages about Retaz itself, described in Section 2 under "Messages from Retaz about Retaz". Those are chosen by what you just did in the app, never by building a picture of who you are, and no one outside Retaz is involved in showing them to you.
4. The retaz.fm website, the waitlist, and press and creators
The website
Like any website, retaz.fm is served through hosting infrastructure (Cloudflare) that processes visitors' IP addresses and request details (the address requested, including anything after a "?" in it, the browser and the time) to deliver pages and protect against abuse. Cloudflare keeps logs of the requests that our own code on its network answers, such as pages for shared playlists and curators, prices and the La Chispa live panel, with the full address requested, under its retention settings for our account. If a request fails, your browser may send Cloudflare a short error report about it. The site sets no cookies and runs no analytics, advertising or cross-site tracking; it remembers your language and view choices in your own browser's storage.
The site loads fonts from Google Fonts, its emoji script from jsDelivr, and its flag images from twemoji.maxcdn.com. Each of them receives a standard web request from your browser, including your IP address.
To show prices for your region, and to help choose a language on your first visit, the site uses the country that Cloudflare derives from your network address when it delivers the page; no outside lookup service is asked, the country is not stored, and you can change the region and the language on the page.
Pages for shared playlists and curators, and the La Chispa top five, show what members have published (Section 2). Search engines and AI crawlers can index them.
On our redeem page, where a journalist or creator redeems a press year, each attempt to redeem a code is recorded with a salted hash of the visitor's IP address, never the address itself, to stop code guessing; these records are deleted after about two days. When the app opens our tutorials page, it tells the page your app language, your platform, whether you use the light or dark look, and whether you have a membership or are a Founder, so that the page shows the right tutorials.
The waitlist
If you joined the waitlist on retaz.fm before its signup form was removed in October 2026, we hold your email address and, if you used the extended signup form, the country, primary music platform, and "how did you hear about us" answer you chose. The list is stored in Ireland. We use it only to send you news about Retaz's launch and the app. No spam, and we never sell or share the list. To be removed, email info@retaz.fm and we will delete your entry.
Press and creators
If you are a journalist, a news desk or a music creator, we may hold your name or handle and the contact details you publish, with your outlet or platform, country and language and, for creators, your audience size and what you post. We gather these from your own public pages, with help from an AI research assistant (Anthropic's Claude), and keep them in our working files. We use them only to tell you about Retaz and La Chispa, and we do not give the lists to anyone else. If we give you a press year, we keep the code (stored only as a hash) with a label that may name you, and when it was redeemed and by which account.
Our legal basis is legitimate interests (Art. 6(1)(f)) in telling the press and creators about Retaz. You can object at any time: reply to any of our emails, or write to info@retaz.fm, and we will not contact you again. We keep these lists until December 1, 2027, twelve months after the La Chispa result, apart from a short list of people who asked us not to contact them, which we keep so that we don't. A press code's label is deleted when the code expires unredeemed, or twelve months after it was redeemed.
5. Why we use your data (purposes and legal bases)
| Purpose | Data involved | GDPR legal basis |
|---|---|---|
| Provide your account and the core service (playlists, votes, saves, finding songs, imports and exports, translation) | Account data, content, interactions | Performance of a contract (Art. 6(1)(b)) |
| Apply the 18-and-over rule, and catch a wrongly-entered birth year | Birth year, minor flag; on iOS 26, Apple's age range (not stored) | Performance of a contract and legitimate interests (Art. 6(1)(b), (f)) in keeping an adults-only service free of minors |
| Running La Chispa: counting hearts, applying the Rules' strike of hearts after a refund or a store test purchase, and showing the leaderboard | Hearts, the heart record, your membership record, country and region | Performance of a contract (Art. 6(1)(b)): the La Chispa Rules are part of our Terms |
| Keeping the heart record and the La Chispa record after you delete your account, so that the result can be checked | The heart record and the La Chispa record (Section 7) | Legitimate interests (Art. 6(1)(f)) in a fair result that can be checked, and in establishing or defending legal claims (Art. 17(3)(e)) |
| Check that a La Chispa Country Champion is eligible, and have the result certified independently | Legal name, residence confirmation; coded La Chispa records | Legitimate interests (Art. 6(1)(f)) |
| Safety, moderation, and community integrity (reviewing reports, enforcing guidelines, keeping voting honest) | Content, reports, blocks, account data | Performance of a contract and legitimate interests (Art. 6(1)(b), (f)); legal obligation (Art. 6(1)(c)) for notices and decisions under the EU Digital Services Act; legitimate interests in protecting children when we report material to United States authorities |
| Keeping the service, its voting and its moderation honest: the operations log and our automated checks | Operations log events (Section 2) | Legitimate interests (Art. 6(1)(f)) |
| Waitlist news | Waitlist email and signup answers | Consent (Art. 6(1)(a)); withdraw any time |
| Delivering direct messages and message requests between members | Message content, sender and recipient | Performance of a contract (Art. 6(1)(b)) |
| Running Communities: creating, joining and leaving communities, posting, hearts on posts, song suggestions, co-curating, invitations and requests to join, private communities, and restoring a deleted community | Community details, memberships and when you agreed to the guidelines, posts, hearts on posts, suggestions and their thoughts, who added each song to a Community playlist, co-curator invitations and roles | Performance of a contract (Art. 6(1)(b)) |
| Keeping Communities safe: hiding a post that three members have flagged until we review it, keeping deleted posts so that a report can still be checked, and reviewing how owners remove posts | Flags, posts, the owner's reason and the record of owner actions | Legitimate interests (Art. 6(1)(f)) in a safe community; legal obligation under the EU Digital Services Act where it applies (Art. 6(1)(c)) |
| Reviewing how playlist owners remove comments | The removed comment, who removed it, when, and the reason | Legitimate interests (Art. 6(1)(f)) in a safe community |
| Showing you Discover's "Your genres" list and Trending's "Your Country" and "Your Area" lists | Hashtags on your playlists and on the playlists you hearted; the country and region on your profile and on each community owner's profile; recent joins, posts and hearts on posts | Legitimate interests (Art. 6(1)(f)) in helping members find communities |
| Showing you Last Spin and Tuned In from your own listening activity | Playlist-open (spin) records | Legitimate interests (Art. 6(1)(f)) |
| Understanding how the app is used, with our own product counters | First-time marks for your account, and totals | Legitimate interests (Art. 6(1)(f)) in understanding and improving the service |
| Sending you the notifications listed in Section 2 | Push token; what each notice says | Consent (Art. 6(1)(a)); withdraw any time with the Push notifications switch in Settings or in your phone's settings |
| Keeping the list of your notifications in the app | What each notice says and when it was sent | Performance of a contract (Art. 6(1)(b)) |
| Diagnosing crashes and performance problems | Error reports, device type, recent app activity and your account identifier | Legitimate interests (Art. 6(1)(f)) in a working, secure app |
| Security, logs, backups and app updates | IP addresses, device type, request addresses, installation identifier | Legitimate interests (Art. 6(1)(f)) in a working, secure service |
| Running your membership: knowing it is active, and recognising a renewal or a refund | Membership record (Section 2, "Your membership") | Performance of a contract (Art. 6(1)(b)); legitimate interests (Art. 6(1)(f)) in meeting United States tax and accounting duties |
| Running and protecting retaz.fm, and showing prices for your region | IP address, request details, the country derived from your network address | Legitimate interests (Art. 6(1)(f)) |
| Public pages for shared playlists and curators, and the public La Chispa top five | What you publish (Section 2) | Performance of a contract (Art. 6(1)(b)) |
| Telling journalists and creators about Retaz, and press years | Contact details from public pages; press codes and their labels | Legitimate interests (Art. 6(1)(f)); for a press year, the terms of the gift (Art. 6(1)(b)) |
| Responding to your requests and legal compliance | Whatever the request involves | Legal obligation and legitimate interests (Art. 6(1)(c), (f)) |
6. Who receives your data
Service providers
We use a small number of service providers, and only to run Retaz. Where a provider processes personal information on our behalf, it does so under a data processing agreement. There are two exceptions today. Expo does not publish one: for Expo we rely on its terms and on its certification under the EU-U.S. Data Privacy Framework (Section 11). And our working files, such as our lists of journalists and creators, are kept on a personal Microsoft OneDrive account under Microsoft's consumer terms; we will move them to a Microsoft business account after December 1, 2026. Our providers are:
- Supabase: our database, sign-in service, server functions and file storage. The app's data is stored in the United States, on Amazon Web Services in Northern Virginia (us-east-1); the retaz.fm waitlist is stored separately, in Ireland. Supabase also holds our hosting platform's logs and backups, for 7 days. It does not use your data for its own purposes.
- Amazon Web Services: Amazon Bedrock runs the Claude model that translates comments and direct messages, in EU regions, and receives only the text being translated and the reader's language. Amazon Bedrock also runs the AI models of our automated operations checks, in Amazon's United States regions, and they receive only the coded operations log events described in Section 2.
- Microsoft: Azure AI Translator is our backup translation service, used only when a first translation fails our quality checks. It receives only the text being translated and the reader's language, through Microsoft's global service, so the text can be processed outside the EU. Microsoft OneDrive also stores our working files, such as our lists of journalists and creators (Section 4).
- Expo: delivers notifications, and only if you turned them on. To set them up, Expo receives your phone's installation identifier and its Apple or Google notification address; to deliver one, it passes our message and your push token to Apple's or Google's notification service, which delivers it to your device. Expo also delivers app updates: each time the app checks for one, it sends Expo a random installation identifier, the platform and app version, the updates installed and, after a crash, up to 1,024 characters of the error message, and the request carries your phone's IP address. Expo does not receive your account data.
- Sentry: receives the crash and performance reports described in Section 2, which can include your account identifier but never your name, email address or IP address, and keeps them in the United States (Section 7).
- Cloudflare: hosts and protects retaz.fm, including the pages for shared playlists and curators and the La Chispa top five, and keeps the request logs described in Section 4.
- Google Workspace: our email. What you send to info@retaz.fm, safety@retaz.fm or our other addresses at retaz.fm is stored there, and we reply from it.
- Twilio SendGrid: will deliver email to members if we start sending it. We send members no email today, and SendGrid receives nothing.
- DataRep: our representative in the EU, the EEA and the UK (Section 14). It receives the requests and questions you send it and passes them to us.
Direct messages are stored on the same Supabase infrastructure as the rest of your account data; no separate third-party messaging provider is involved. Their text reaches Amazon Web Services, and Microsoft if needed, only to be translated.
Others who receive data
- Apple and Google: sign-in, app distribution, payment for memberships bought in the app, and delivery of push notifications to your device. Apple also answers the app's age-range question on iOS 26 (Section 2), and Google serves the website's fonts. Their own privacy policies govern what they collect on their side.
- Music services: Apple Music, Deezer, SoundCloud and the other services you use or link to. When you search for a song or paste a link, the service concerned receives the search or the link, unchanged, from your phone or from our server, never with your Retaz account identifier, name or email. A link you paste from YouTube, Spotify, SoundCloud, Audiomack or Anghami goes to that service's own link preview. When you connect a service, import or export, your phone deals with that service directly, under your own agreement with it.
- Map and image services: when the app shows its world map, your phone loads the map's code from unpkg.com and its map images from OpenFreeMap, and cover art loads from the music services' image servers. Each receives your phone's IP address with the request, and nothing from us that identifies you. The website's equivalents are listed in Section 4.
- Anthropic: one founder uses Claude, Anthropic's AI assistant, on Anthropic's consumer plan (Claude Pro) for engineering, operations and research; it can see personal information when it is used to read our database (it has read-only access), our email or our working files. On that plan, Anthropic handles what it sees under its own terms and privacy policy, as a company in its own right, not as our processor.
- The authorities: when the law requires it, or to protect someone from serious harm, including reports of child sexual abuse material to the National Center for Missing and Exploited Children (NCMEC) in the United States (Section 8).
- Other members and the public: what you publish, as Section 2 describes under "Who can see your profile and what you publish".
The independent La Chispa observer. An independent observer certifies the La Chispa result: an individual in the United States, engaged by a signed letter, who is not our agent and whom we will name with the result on December 1, 2026. Before anything leaves us, account and playlist identifiers are replaced by codes. The observer, and anyone assisting them, receives coded records of every heart (which coded member, which playlist and when); each coded member's declared country and region, birth year, history of changes to them, badge and referral links; the Country Champions' declarations, with any legal name removed; for each playlist being assessed, its title, songs and their changes, visibility, authorship and moderation state; membership records, including the transaction identifier the store gave us; the founders' related parties, coded, with their relationship; and fingerprints of the counting code and of the heart record. The observer never receives names, handles, display names, email addresses, phone numbers or message content. We keep the table that matches each code to a member. The observer may use the records only to certify the result, must keep them in encrypted storage we do not control, and deletes them twelve months after the result is announced (December 1, 2026).
Checks that need a name. We do the checks that need a name ourselves. For the sanctions screen of a La Chispa Country Champion (Section 2), we search a downloaded copy of the United States government's sanctions lists, so the name does not leave Retaz, and we give the observer only the method and the result.
We do not sell personal information, and we do not share it for cross-context behavioral advertising. We disclose data only to the recipients in this section.
7. How long we keep data
- Account data and content: kept while your account exists.
- When you delete your account: deleting in the app removes your account and its data at once and permanently, apart from the records listed under "What we keep after you delete your account" below. Because it removes your playlists and communities, it also deletes other members' comments, hearts, saves and listening records on your playlists, the communities you own with everything in them, and every direct message conversation you were in, both sides. From November 17, 2026 at 00:00 US Eastern Time (2026-11-17T05:00:00Z) until the final La Chispa tally has been captured, normally a few minutes later, account deletion is paused; try again once it has been captured (La Chispa Rules, Section 1.6). If you request deletion by email instead, we complete it within 30 days. See our account deletion page for the exact steps.
- What we keep after you delete your account:
- The heart record: every heart you gave or withdrew, with your account identifier, the playlist and the time. Deleting your account adds a withdrawal for each heart it removes, including other members' hearts on your playlists.
- The La Chispa record: the final tally captured on November 17, 2026, with each heart it counted and the account identifier of the member who gave it, the standings, and our recount checks. If you had a playlist in La Chispa, it also keeps your declared country and region, birth year, signup date, badge and whether you held a membership, as they stood at the capture.
- We keep the heart record and the La Chispa record so that the result can be checked, until December 1, 2027 or until any dispute about the result has ended, whichever is later, and then delete them or remove what identifies you.
- The operations log (Section 2), with no time limit at present.
- Handles you gave up, with your account identifier, with no time limit at present.
- Reports about you, for two years after the case is closed, or longer while the law requires us to keep them.
- Traces in other members' things: a name credited on a playlist another member adopted from you; the reason a community's owner gave for removing one of your posts; other members' notifications that name you, until they are deleted after 90 days; and, if you redeemed a press code, its label and when you redeemed it, for twelve months after that.
- Crash and performance reports already sent to Sentry, with your account identifier, until their periods end: up to 90 days for crash and error reports, and up to 13 months for performance data.
- Logs and backups on our hosting platform, for 7 days.
- Direct messages: kept while both members' accounts exist. When either member deletes their account, the whole conversation is deleted, both sides.
- Communities, posts and hearts on posts: a community is kept until its owner deletes it, or deletes their account. A deleted community can be restored for 72 hours and is then erased within the hour, with its memberships, posts, hearts on posts, invitations and requests to join and the record of owner actions. Your memberships, posts and hearts are kept while your account is active and the community exists. A deleted post is kept out of sight until the community is erased or its author deletes their account. Song suggestions are kept, with what happened to them, until the community is erased or the member who made them deletes their account, and a co-curator role ends when its member leaves the community or deletes their account. An invitation to join is deleted when it is accepted, and a declined one is kept while the community and the invited member's account exist; a request to join is deleted when it is answered or cancelled, or after 14 days. Deleting your account erases the communities you own, with everything in them, and your memberships, posts, hearts and suggestions everywhere else.
- Comments a playlist's owner removed: kept out of sight, with the record of the removal, until the playlist is deleted or the comment's author deletes their account.
- Spin history (Last Spin, Tuned In): kept for 24 months, and deleted sooner with your account.
- Changes to your country or region: kept while your account exists and deleted with it; the La Chispa record keeps your country and region as they stood at the capture.
- Push token: deleted when you turn the Push notifications switch off, when you sign out, when you delete your account, or when a notification to it fails.
- Your notifications list: each entry is deleted after 90 days, and all of them with your account. Our records of message alerts for you are deleted the same way, whether or not they reached your phone.
- Stored translations: deleted with the original comment or message, and in any case after 90 days.
- Product counters: the marks for your account are deleted after 12 months, or with your account. Totals, which identify no one, are kept.
- Feedback you send in the app, and emails you send us: kept for two years; in-app feedback is deleted sooner if you delete your account.
- Reports you file: deleted with your account.
- Your membership record: deleted with your account.
- Your requests about your data: we keep a record of each request and our answer for three years.
- Waitlist emails: kept until launch communication ends or you ask to be removed, whichever comes first.
- Press and creator lists: until December 1, 2027 (Section 4).
- Crash and performance reports: Sentry keeps crash and error reports for up to 90 days, and sampled performance data for up to 13 months.
8. Moderation and safety reports
When you report content, the report goes into a restricted queue that only our safety team can read, and a person reviews it; today the team is Retaz's two founders. Reports are stored with the category you chose (one of 12: covering playlists, profiles, comments, direct messages, communities, and community posts) and which item you reported. A flag in Communities is a report: when three different members have flagged the same community post, it is hidden from everyone but its author until we have reviewed it. Our safety team reviews new reports by hand every day. To reach our safety team directly, email safety@retaz.fm. If we find material depicting child sexual abuse, we hide it and report it to the National Center for Missing and Exploited Children (NCMEC), as United States law requires. We keep reports for two years after the case is closed, unless the member who filed one deletes their account first (Section 7).
A playlist's owner can remove a comment someone else left on it, and must give a reason. The comment is then hidden from everyone, its author included, and we keep it, with who removed it, why and when, so that our team can review the removal, until the playlist is deleted or the comment's author deletes their account. When either of two members has blocked the other, neither can comment on the other's playlists.
9. Your rights
Exercising a right never costs you anything and never results in worse service.
- Export your data any time from inside the app (Settings > Privacy > Export my data). The file holds your profile and settings; your playlists and their songs, including any you gave to a community; the hearts you gave and withdrew; the playlists you saved, the songs you liked or marked "not for me", and the curators and Scenes you follow; the people you blocked and the reports you filed; your comments and replies (one a playlist's owner removed is in it, with when, but not who removed it or why) and the comments you removed from your own playlists; the direct messages you sent and the list of your conversations; your notifications list and the message alerts we recorded for you; your communities, memberships, posts, hearts on posts, the playlists you pinned and the actions you took as an owner; your song suggestions, the songs credited to you on Community playlists and your co-curator roles; the invitations to join you received and sent, without the other member's name, and your requests to join while they wait; your Curator badge, the badges recorded as awarded to you and the ones you pinned; your membership record; your email choices; the changes to your country or region; and your translation suggestions. Other members appear in it only as random identifiers, never by name or contact details, and messages you received and other members' words are not in it. Some records are not in it either, such as your sign-in email address, the store's transaction identifier and our internal notes; you can ask us for a copy of those (this section).
- Delete your account any time from inside the app, or by email. Details: retaz.fm/delete-account.
- If you are in the EU/EEA or UK (GDPR): you can access, correct, delete, and receive a portable copy of your data; restrict or object to processing; withdraw consent at any time; and complain to your supervisory authority.
- If you are in California or another US state with a privacy law: you can know what we collect, delete it, and correct it. We do not sell or share personal information as those laws define it, and we will never discriminate against you for exercising a right.
- Automatic decisions. When Apple or Google confirms a refund, we end that paid period automatically, and under the La Chispa Rules the hearts given during it stop counting, as do hearts an account gives after a store test purchase. The La Chispa count itself is mechanical, with no human judgement and no random draw. You can ask a person at Retaz to review any of these decisions by writing to info@retaz.fm.
To exercise any right, email info@retaz.fm from the address associated with your account. If you cannot write from that address, for example because you use Apple's private relay, tell us, and we will find another way to confirm that the account is yours. If you are in the EU, the EEA or the UK, you can also write to our representative, DataRep (Section 14). We respond within 30 days, and we keep a record of each request and our answer for three years.
10. Age policy: 18 and over
You must be at least 18 years old to create an account or use Retaz, everywhere we operate, or older where your country sets a higher age of majority. We ask for your birth month and year at sign-up and keep only the year; this is self-declared, which means we rely on you telling us the truth rather than verifying it. On an iPhone with iOS 26 or later, the app also asks Apple for your Apple Account's age range (Section 2). If we learn that an account belongs to someone under 18, we close the account and delete its data. Earlier versions of this policy set the minimum at 16 and described extra protections for members aged 16 and 17; with the minimum at 18 there are no such members.
11. International transfers
Retaz is a United States company. The app's data is stored in the United States, with Supabase on Amazon Web Services in Northern Virginia (us-east-1), and we access it from the United States and, at times, from the EU. Most of our service providers are in the United States too (Section 6). If you are in the EU, the EEA or the UK, your data reaches the United States under these safeguards:
- Supabase: the EU standard contractual clauses (Module Two) and the UK addendum, which are part of Supabase's data processing addendum.
- Amazon Web Services, Microsoft, Google, Cloudflare, Expo and Sentry: each is certified under the EU-U.S. Data Privacy Framework and its UK Extension, which the European Commission and the UK government recognise as giving adequate protection. Where a provider's data processing terms also include standard contractual clauses, those apply as well.
- Anthropic (Section 6): in the United States, and not certified under the Data Privacy Framework; we use it under its own consumer terms.
- The independent La Chispa observer receives only coded records, and no means of identifying anyone (Section 6).
Some processing stays in the EU: translation by Amazon Bedrock runs in EU regions, and the old retaz.fm waitlist is stored in Ireland. To ask for a copy of a safeguard, write to info@retaz.fm.
12. Security
Data moves between the app and our backend over encrypted connections (HTTPS/TLS), and access to production data is restricted. Direct messages are encrypted in transit and at rest on our servers, but they are not end-to-end encrypted: our safety team can access message content as described in Section 2. No online service can promise perfect security, and we will not pretend otherwise; if a breach ever affects your data, we will notify you as the law requires.
13. Changes to this policy
When we change this policy, we will post the new version here with a new effective date. For material changes we will give you notice in the app or by email before the change takes effect. This policy has not yet been reviewed by outside counsel; it describes our actual practices honestly and will be refined as Retaz grows.
14. Contact
Retaz LLC, Lewisburg, Greenbrier County, West Virginia, USA.
Privacy questions, requests, and complaints: info@retaz.fm
Safety reports: safety@retaz.fm
Representative in the EU, the EEA and the UK (Article 27 of the GDPR and the UK GDPR): Data Protection Representative Limited, trading as DataRep. Email datarequest@datarep.com and write "Retaz LLC" in the subject line, or use the form at www.datarep.com/data-request. By post, write to DataRep at the address for your country on our EU, EEA and UK contacts page. Address letters to DataRep, not to Retaz LLC, or they may not reach it. For questions about your account or membership, write to info@retaz.fm.