RETAZ

Privacy Policy

Effective November 11, 2026 · Retaz LLC · Lewisburg, Greenbrier County, West Virginia, USA
Supersedes the version effective October 31, 2026. Digital Services Act contacts. Section 14 no longer lists our single point of contact or our legal representative under the Digital Services Act. Both are on our EU, EEA and UK contacts page. DataRep is still our representative under Article 27 of the GDPR and the UK GDPR. Nothing about how we handle personal data changes.
The October 31 note follows, unchanged. That version superseded the one effective October 28, 2026. Private profiles. Section 2 now says what other members can see of a private profile; since October 31, 2026 they can no longer read its region, city, links or privacy settings.
The October 28 note follows, unchanged. That version superseded the one effective October 27, 2026. Our working files. Section 6 now says that our working files are kept on a personal Microsoft OneDrive account under Microsoft's consumer terms, a second exception to our data processing agreements beside Expo, and that we will move them to a Microsoft business account after December 1, 2026. Co-curators. Section 2 now says that only a member who holds a membership can be invited to co-curate, so the owner who invites them can tell whether they hold one. Invitations and private communities. Section 2 now describes invitations to join a community, requests to join and private communities: what we store, who sees each, how long each is kept, and that our safety team's review still reaches inside a private community. As with co-curators, only members who hold a membership can be invited, and the search shows only them. Sections 5, 7 and 9 and our account deletion page match. Community invite links. Section 2 now says what a community's invite link carries and what anyone who opens it sees, and names the notice an owner gets when someone answers an invitation to co-curate. Message alerts. Section 2 now says that, with notifications on, we tell you when a member sends you a direct message, never with the message itself, and that these alerts are not kept in your notifications list. Sections 7 and 9 match.
The October 27 note follows, unchanged. That version superseded the one effective October 12, 2026. This version corrects the earlier one wherever it did not match what our systems do. Where your data is stored. Sections 6 and 11 said the app's data is stored in the European Union. It is stored in the United States, with Supabase on Amazon Web Services in Northern Virginia, and has been since June 2026. Section 11 now names the safeguards for data from the EU, the EEA and the UK, and says that we access it from the United States and, at times, from the EU. Who receives data. Section 6 now names every provider and recipient. It adds Google Workspace (our email), Expo's app updates, our automated operations checks on Amazon Web Services, the AI assistant we use to build and run Retaz (Anthropic's Claude), Microsoft OneDrive (our working files), Twilio SendGrid (not yet used), DataRep, the music services, and the services that serve the app's map and images, and it removes Songlink, which we no longer use. It says that our backup translation service can process text outside the EU, describes what the independent La Chispa observer receives, and says how we run the sanctions screen without a name leaving Retaz. Crash reports. Section 2 said that crash reports never contain your account identifier. They can include it, so that we can tell which account a problem affected; they never include your name, email address or IP address. Section 7 now says how long Sentry keeps them, including after an account is deleted. What we collect and who can see it. Section 2 now also covers what Google gives us at sign-in, the birth month the app asks for but does not keep, Apple's age check on iOS 26, technical data such as the IP addresses in sign-in sessions and logs, what other members and anyone on retaz.fm can see, finding songs, imports and exports, our own product counters, the operations log and the automated check of hearts, and the reference the stores receive when you buy. Communities and notifications. Section 2 now describes the Soundboard, where members suggest songs for a community's Community playlist, and co-curators, and it lists every notification the app sends today, including replies to your comments, songs you suggested and invitations to co-curate. After you delete your account. Section 7 said that, apart from records the law requires, only the La Chispa record is kept after you delete your account, and only from November 9, 2026. In fact the record of every heart has kept account identifiers since August 2026, and a few other records stay too. Section 7 now lists each one and how long it is kept, says that deleting an account also deletes other members' comments, hearts and saves on its playlists, and no longer says that membership records are kept for tax purposes, because our systems do not keep them yet. Our account deletion page matches. Safety reports. Section 8 now says how reports are reviewed today: by a person, every day. Your rights. Section 9 now lists what the in-app export holds and where to find it (Settings > Privacy > Export my data), offers another way to confirm that an account is yours, and says how to ask a person to review an automatic decision. The website, press and creators. Section 4 now describes the website in more detail, and covers the journalists and music creators we contact. Legal bases. Section 5 now covers each of these, and gives legitimate interests rather than legal obligation as the basis for the 18-and-over check and for tax records.
The October 12 note follows, unchanged. That version superseded the one effective October 9, 2026. Communities. Section 2 now describes Communities, which arrive with an app update in October 2026: the communities you create and join, when you agreed to the guidelines, your posts, and the hearts you give posts (their own records, never counted in La Chispa). It says who can see each of them, that the app never shows who gave a heart to a post, how a flag hides a post and what we keep when an owner removes one, how Discover and Trending use your playlists, the playlists you hearted and the country and region on your profile, that a deleted post is kept out of sight so a report about it can still be checked, and that a deleted community can be restored for 72 hours and is then erased. It also describes the list of a community's members, which anyone signed in can open, and who is counted there but not named. Sections 5, 7 and 8 match. Comments. Section 8 now says that a playlist's owner can remove a comment with a reason, which we keep with the comment for review, and that members who have blocked one another cannot comment on each other's playlists. Sections 5 and 7 match.
The October 9 note follows, unchanged. That version superseded the one effective October 4, 2026. Notifications. Section 2 now lists every notification Retaz can send: your Curator badge, new hearts (at most once a day) and new comments on your playlists, and four La Chispa notices sent to everyone with notifications on. It also says how to turn notifications on and off, that turning them off in Settings deletes your push token at once, and that the app keeps a list of the notices sent to you for 90 days (Sections 5 and 7 match). The earlier wording named only the Curator badge. La Chispa certification. Section 2 now describes two declarations a La Chispa Country Champion may be asked for from November 17, 2026: a legal name for the sanctions screen and any contract, and confirmation of where they live at the close, never an identity document. Section 6 names the independent observer who certifies the result as a recipient of coded La Chispa records only, kept for twelve months after December 1, 2026. Section 7 says that from November 9, 2026, if you have a playlist in La Chispa, the La Chispa record (your declared country and region, birth year, signup date, badge and whether you held a membership, as they stood at the final tally) is kept after you delete your account, so the result can be checked. Section 5 gives the legal basis.
The October 4 note follows, unchanged. That version superseded the one effective October 1, 2026. Our representative in the EU, the EEA and the UK. Retaz LLC's representative under Article 27 of the GDPR and the UK GDPR, and its legal representative under Article 13 of the Digital Services Act, is DataRep (Data Protection Representative Limited), appointed from October 2, 2026. Section 14 and our EU, EEA and UK contacts page give the details. An earlier version of this policy named a representative at an address that was not theirs. If you wrote to that address, please write again using the details in Section 14.
The October 1 note follows, unchanged. That version superseded the one effective September 25, 2026. Fewer messages from Retaz on the free tier. From October 15, importing or exporting a playlist, and publishing your first playlist, are never followed by a message from Retaz, and the free allowance now counts only the playlists you publish (Section 2). Message requests. Section 2 and Section 5 now describe message requests, which the app already offers: members who do not follow each other can still message, as a request the other member can accept or decline. They also say that from October 15, 2026, both members need a membership to send or receive direct messages. Changes to your country or region. Section 2 and Section 7 now say that we keep a record of changes to your country or your state, province or region, including the first time you set them, to review La Chispa eligibility, and delete it with your account. Section 2 also says that your country, and for Ukraine your region, decide whether you can be recognized in La Chispa, and cannot be changed in the app while La Chispa runs. Deleting your account while La Chispa is counted. Section 7 now says that account deletion is paused from November 17, 2026 at 00:00 US Eastern Time until the final La Chispa tally has been captured, normally a few minutes later.
The September 25 note follows, with one correction: memberships are sold in the app from October 15, 2026. That version superseded the one effective August 8, 2026. Memberships are sold in the app from October 15, 2026, and Apple or Google handles every payment. The sections on your membership, payment details, providers and legal bases now say so.
The August 8 note follows, unchanged. That version superseded the one effective August 5, 2026. The minimum age to use Retaz is now 18. It was 16 in earlier versions. Nobody under 18 can hold a Retaz account, so the sections below that described extra protections for 16 and 17 year olds no longer describe anyone, and say so.
The August 5 note follows, unchanged. That version superseded the one effective July 29, 2026. This update is written ahead of two changes that begin on October 15, 2026, so that you read about them before they happen rather than afterwards. First, on the free tier Retaz will start showing you short messages about Retaz itself after your first playlist creation, import and export; the previous version said flatly that we show no ads, which will stop being true even though these are our own messages and involve no advertiser. Section 2 and Section 3 now describe them, and the counters that make the free allowance work. Second, memberships open, so Section 2 now describes what a membership record contains and Section 3 states plainly that your card details never reach us. The July 29 update corrected what we say about crash reporting, and that correction stands unchanged.

The short version

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:

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:

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

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)

PurposeData involvedGDPR legal basis
Provide your account and the core service (playlists, votes, saves, finding songs, imports and exports, translation)Account data, content, interactionsPerformance of a contract (Art. 6(1)(b))
Apply the 18-and-over rule, and catch a wrongly-entered birth yearBirth 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 leaderboardHearts, the heart record, your membership record, country and regionPerformance 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 checkedThe 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 independentlyLegal name, residence confirmation; coded La Chispa recordsLegitimate interests (Art. 6(1)(f))
Safety, moderation, and community integrity (reviewing reports, enforcing guidelines, keeping voting honest)Content, reports, blocks, account dataPerformance 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 checksOperations log events (Section 2)Legitimate interests (Art. 6(1)(f))
Waitlist newsWaitlist email and signup answersConsent (Art. 6(1)(a)); withdraw any time
Delivering direct messages and message requests between membersMessage content, sender and recipientPerformance 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 communityCommunity 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 rolesPerformance 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 postsFlags, posts, the owner's reason and the record of owner actionsLegitimate 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 commentsThe removed comment, who removed it, when, and the reasonLegitimate interests (Art. 6(1)(f)) in a safe community
Showing you Discover's "Your genres" list and Trending's "Your Country" and "Your Area" listsHashtags 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 postsLegitimate interests (Art. 6(1)(f)) in helping members find communities
Showing you Last Spin and Tuned In from your own listening activityPlaylist-open (spin) recordsLegitimate interests (Art. 6(1)(f))
Understanding how the app is used, with our own product countersFirst-time marks for your account, and totalsLegitimate interests (Art. 6(1)(f)) in understanding and improving the service
Sending you the notifications listed in Section 2Push token; what each notice saysConsent (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 appWhat each notice says and when it was sentPerformance of a contract (Art. 6(1)(b))
Diagnosing crashes and performance problemsError reports, device type, recent app activity and your account identifierLegitimate interests (Art. 6(1)(f)) in a working, secure app
Security, logs, backups and app updatesIP addresses, device type, request addresses, installation identifierLegitimate interests (Art. 6(1)(f)) in a working, secure service
Running your membership: knowing it is active, and recognising a renewal or a refundMembership 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 regionIP address, request details, the country derived from your network addressLegitimate interests (Art. 6(1)(f))
Public pages for shared playlists and curators, and the public La Chispa top fiveWhat you publish (Section 2)Performance of a contract (Art. 6(1)(b))
Telling journalists and creators about Retaz, and press yearsContact details from public pages; press codes and their labelsLegitimate interests (Art. 6(1)(f)); for a press year, the terms of the gift (Art. 6(1)(b))
Responding to your requests and legal complianceWhatever the request involvesLegal 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:

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

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

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.

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:

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.