Privacy Policy
Last updated: 13 November 2026
67fm has no tracking. Listening, reading the chat and paying for a song need no account, and listening is anonymous. If you pay to put a song on air, we keep what is needed to play it and to keep the payment records the law asks for. If you want to write in the chat, you sign in with Google and pick a public @handle. This page explains exactly what, why, and what you can ask us to do.
1. Who is responsible
ZOOMERS NETWORK LGTM S.R.L. (CUI 51548084) is the controller of your personal data on 67fm. Write to contact@67fm.app for any question or request about your data. Our full details are on the company details page. We have not appointed a data protection officer; we are not required to.
2. If you just listen
- Listener count: your browser makes up a random code each time you open the page and sends it to us every 3 seconds, so we can show how many people are listening. It is not stored in a cookie, it changes every time you reload, and we keep it in memory for about 12 seconds after your last visit. It is not linked to you in any other way.
- Server logs: like every website, our hosting providers Cloudflare and FastAPI Cloud receive your IP address and browser details with each request, and keep standard logs for security and troubleshooting. To stop floods of requests, Cloudflare also counts the requests from each IP address over a minute, separately at each of its locations, and asks you to wait if there are too many. We do not store these counts or your IP address for them.
- Song search: when you search for a song (to put it on air, or for a private room's playlist), what you type goes to our server at Cloudflare, which asks YouTube's own search for it. YouTube receives the search words from Cloudflare, not your IP address or cookies. Results for the same words are kept in Cloudflare's cache for an hour, not linked to you. We do not keep your searches in our database; Cloudflare's standard logs may include them, like any request.
- YouTube: YouTube's player loads only when you tap Tune in, in YouTube's privacy-enhanced mode. From then on your browser connects to Google, which receives your IP address and may set its own cookies or storage. Before you tune in, nothing on the page loads from Google: our fonts are hosted by us and video thumbnails come through our own domain. See section 7 and our cookie page.
We use no analytics, no advertising and no tracking of our own, and we do not sell anything about anyone.
3. If you pay to put a song on air
- At Stripe: Stripe's checkout page collects your email address, your card or other payment details, and your billing country. Your card details go straight to Stripe; we never see them. We can see in Stripe the email address, the amount, the payment status and the country, as needed to handle the payment and any refund.
- In our database: the YouTube video you chose (its ID and title), your bid, the display name you typed, when you paid and when it aired, a reference that links the song to its Stripe checkout, and the Stripe payment reference, which we use if the song has to be refunded.
- Your display name is public. It is shown to everyone on air and in the queue. It is optional; leave it empty and we show "anon". Please do not type your full name or contact details if you do not want them seen.
- If you are signed in to the chat, your song is linked to your chat profile and shown as your @handle instead of a display name. See section 4.
4. If you use the chat
Anyone can read the chat without an account. To write in it or react, you sign in with Google and pick a handle.
- Signing in with Google: Google's sign-in page opens from accounts.google.com, in a small window, only when you click "Sign in with Google". When you sign in, Google tells us your Google account ID and your email address. We do not receive or keep your name or photo. Your email address stays private: we use it only to run your account (and to recognise our own admin accounts), and we never show it to anyone.
- Your chat account: in our database we keep your Google account ID, your email address, your handle, how many times you changed it, when you joined, and whether the account is banned. When you pick your handle, you confirm you are 16 or older and accept the chat rules in our terms. Your browser keeps a sign-in token so you stay signed in; it lasts a year and is renewed each time you visit.
- Apps you sign in to with 67fm: an app (for example Mixtape) can ask to use your 67fm account. We show you what it would be able to do, and nothing happens unless you choose Allow. For each app you allow, we keep which app it is, what you allowed, when you connected it and when it was last used, and its sign-in keys in scrambled form (hashed, so they can't be read back). The app can only do what you allowed; it never gets your Google account, your email address or your browser's sign-in. "Connected apps" in your account menu lists them, and Disconnect signs an app out on all your devices at once. Deleting your account disconnects every app. What the app itself does with your data is up to its maker and its own privacy terms.
- Your handle and profile are public. Your @handle is shown next to what you write. Your profile page, 67fm.app/@yourhandle, shows your handle, the month you joined ("listening since"), your badges and the ring they unlock, how many songs you put on air on the main station and the total you bid, your rank this week, and the last 30 songs you paid for there (title, amount, date). Leaderboards for today, this week and all time show the top supporters' handles, pictures, rings, total bids and number of songs. A private room's leaderboard counts only bids in that room and is shown only to the people in it. When you bid while signed in, your @handle, picture and ring are shown with your song in the queue and on air.
- Badges and rings are worked out from 67fm's own records of what you do here: songs you put on air and what you bid, when they aired and how many in a row, how long you have had your account, private rooms you made, joined or bid in, and the chat counts below (for example Founding listener for the first 1.000 profiles, or Night owl for a song on air between midnight and 5 am UTC). Apart from those chat counts, we store nothing extra for them. Your badges and ring are public: on your profile, next to your messages and in the leaderboards. How close you are to the badges you don't have yet is shown only to you.
- Profile picture (optional): if you add one, we re-encode it, which removes hidden details such as location and camera data, crop it square and keep two small copies, in our database and in Cloudflare's storage, which delivers them. It is public next to your @handle and on your profile. You can change or remove it at any time, it is deleted with your account, and moderators may remove a picture that breaks the chat rules.
- Songs you pay for while signed in stay on your profile, under your @handle, until you delete your account. They are not switched to "anon" after 30 days like songs paid without an account.
- Paid shoutouts: if you pay for a shoutout, your message (up to 120 characters) is pinned at the top of the chat for one minute per dollar you paid, with your @handle and the amount, for everyone to see. We keep it in our database with your profile, handle, the amount, its status, the time and the Stripe reference for 30 days, then delete it. The payment record stays with Stripe, as for songs.
- Messages and reactions: your messages (up to 200 characters) are visible to everyone in the chat. They are kept only in the chat room's own rolling store at Cloudflare: the last 1.000 messages, with older ones deleted automatically. People who join see only the last 50 messages from the past 15 minutes. We do not copy messages into our database, unless one is reported or removed. Your reactions (๐ฅ ๐ ๐) to the song playing are kept in the same store, for the last 20 songs only.
- Keeping the chat safe: our own code checks every message before it is posted; no outside company receives your message to check it. In the chat room (at Cloudflare): one message every 3 seconds (one every 10 seconds in slow mode, when the chat is busy), up to 200 characters, no repeating your last message, and no links, email addresses or phone numbers. Then on our server (at FastAPI Cloud): a word list we keep (slurs and some spam words), matched even when disguised with capitals, accents, numbers or symbols for letters (like 0 for o), dots or spaces between letters, or stretched letters; messages that are mostly capitals; and long runs of the same character. Shoutouts go through the same checks before you pay. A held message is not posted, not stored and not shown to anyone; you see why (for example "That word isn't allowed in the chat"). A held shoutout is not posted and you are not charged.
- Chat badges: for the chat badges (First words, Chatterbox, Social, Popular) we count how many messages you have sent, how many times you tagged someone and how many times you were tagged. Only the numbers, never the messages. They are deleted with your account.
- Reports and moderation: anyone signed in can report a message; after 3 reports it is hidden until we review it. Our moderators can delete a message, time someone out for 10 minutes, ban an account (a ban hides their messages and blocks sign-in), or skip the song on air. For every report and every action we record who reported or acted, whose message or song it was, the message text or song title, the reason and our decision. We keep these records for 6 months, then delete them automatically. If you mute a handle, that is stored only in your own browser.
5. If you use private rooms or the wallet
- Rooms: for each room we keep its name, its owner, its join code (the secret in the link), who is in it and since when, the invites (who invited whom and whether it was accepted) and the room's playlist. Everyone in a room sees the @handles of the others. Invites reach you only inside the app (the bell); we send no emails.
- Chat in a room works like the main chat, in the room's own store at Cloudflare, and only people in the room can read it.
- Bids and shoutouts in rooms are kept like those on the main station, with the room they belong to. They are not shown on your public profile, but they count toward the room badges.
- Your wallet (usable everywhere on 67fm, not only in rooms): we keep every top-up (amount, time, Stripe reference) and every bid, shoutout, room or refund paid from it (amount, what for, time). Only you see your balance and history. Card payments go through Stripe, as for songs. For a card top-up, the receipt link in your wallet history takes you to Stripe's own receipt page. If you claim a voucher, we keep which code you claimed and when, so each code is used once per person, and the credit appears in your wallet history.
- When a room closes (the owner closes it, or deletes their account), its member list, invites and playlist are deleted at once, and so is its chat at Cloudflare. Its name and owner stay with the record of the $1 payment.
6. Why we use it, and on what legal basis
| What we do | Data | Legal basis (GDPR) |
|---|---|---|
| Queue and play your song, show your display name, confirm payment, refund when a song does not air | Song, bid, display name, times, Stripe reference and payment details | Contract, Art. 6(1)(b) |
| Keep payment and accounting records | Amount, date, Stripe reference, billing country, email on the receipt | Legal obligation, Art. 6(1)(c), Romanian accounting and tax law |
| Run your chat account, post your messages, reactions and paid shoutouts, show your handle, public profile and place on the leaderboard, link songs you pay for to your profile | Google account ID, email, handle, account details, messages, reactions, shoutouts, songs linked to your profile | Contract, Art. 6(1)(b): the chat terms you accept when you pick a handle |
| Keep the chat safe: rate limits, the automatic filter (links, contact details, word list, capitals, repeats), reports, timeouts and bans, and records of what we removed and why | Message text; reports and moderation records; banned flag | Legitimate interest in keeping the chat safe and free of abuse, Art. 6(1)(f); legal obligation under the EU Digital Services Act, Art. 6(1)(c) |
| Count listeners | The random code, for about 12 seconds | Legitimate interest in showing a live listener count, Art. 6(1)(f) |
| Keep the site running and safe, stop abuse and payment fraud | IP address, browser details, request logs, request counts per IP address (rate limits); Stripe's fraud checks | Legitimate interest in security, Art. 6(1)(f) |
| Answer your emails and handle reports, disputes and legal claims | What you write to us and your email address | Legitimate interest, Art. 6(1)(f); contract where it is about your payment |
The chat filter above is automatic: it can hold a message or shoutout back before it is posted. That is the only automatic decision on 67fm, and it has no legal or similarly significant effect on you: the worst it does is that one message is not posted (and a held shoutout is not charged). It decides nothing else about you, and a person decides reports and bans. Your public profile page only shows what you did on 67fm; we do not use it, or anything else, to profile you for advertising or any other purpose.
7. Who else receives data
These companies help us run 67fm and handle data only on our instructions, under data processing terms:
- Cloudflare serves the website, runs our domain, runs the chat room (where recent messages and reactions are kept), limits how many requests each IP address can make, passes song searches on to YouTube, and forwards email sent to contact@67fm.app. It keeps short-lived copies of public data in its cache: profiles and leaderboards for up to a minute, search results for an hour, video thumbnails for 30 days.
- FastAPI Cloud runs our server, which also runs the chat filter on message text.
- Supabase hosts our database, in the European Union (Ireland).
- Zoho hosts the mailbox our email is forwarded to, in the European Union.
These companies act for their own purposes too, as separate controllers, under their own privacy policies:
- Stripe processes your payment, and uses payment data for fraud prevention and its own legal duties: Stripe Privacy Policy.
- Google / YouTube runs the embedded player (loaded only when you tune in), supplies the video thumbnails (fetched through our own domain, so Google does not see your IP for them), the YouTube API Services we use to look up songs, and the YouTube search our server asks when you search for a song. When you use the player, YouTube's own terms apply: YouTube Terms of Service and Google Privacy Policy. We send YouTube only video IDs and the words you search for, never anything about you.
- Google sign-in (accounts.google.com) handles "Sign in with Google" for the chat, opened only when you click "Sign in with Google". Google sees that you sign in to 67fm and tells us your Google account ID and email address, under the Google Privacy Policy.
The full list, with what each receives and where, is on the sub-processors page. We may also share data with authorities when the law requires it.
8. Data outside the European Union
Some of these companies are based in, or can access data from, the United States. Where that happens, the transfer is protected by the EU-US Data Privacy Framework for companies certified under it, or by the European Commission's Standard Contractual Clauses. You can ask us for a copy of the safeguards at contact@67fm.app. Our server host, FastAPI Cloud, runs in the United States and does not yet provide a data processing agreement; we have asked for one with Standard Contractual Clauses, and will move the server to a provider that offers one if they don't.
9. How long we keep it
- Listener code: about 12 seconds, in memory only.
- Display name (songs paid without signing in): 30 days after your song airs, then it is replaced with "anon".
- Chat account and profile: until you delete your account ("Delete account" in your account menu) or ask us to. Then we delete it at once, with your picture and chat counts, unlink the songs you paid for, and show them as "anon". If the account was banned, we keep its Google account ID and the fact that it is banned, so the ban stays in place.
- Songs paid while signed in: shown on your profile until you delete your account; the payment record is kept as below.
- Chat messages: only the last 1.000 in the chat room; older ones are deleted automatically.
- Reactions: for the last 20 songs only.
- Paid shoutouts: 30 days, then deleted.
- Private rooms: members, invites and playlist until the room closes, then deleted at once; the room's name and owner stay with its payment record.
- Wallet top-ups, voucher credit and what you spent (including which vouchers you claimed): as part of the payment record, for as long as Romanian accounting law requires (up to 10 years), also after you delete your account. A top-up you started but did not pay for, or a room you never paid for, is deleted within 24 hours.
- Reports and moderation records (including the text of a reported or removed message, and skipped songs): 6 months, then deleted automatically.
- Song searches: not stored by us; Cloudflare's cache keeps the results for the same words for an hour.
- Sign-in token in your browser: a year, renewed each visit, or until you sign out.
- Apps you connected: until you disconnect them or delete your account, or a year after the app last signed in. A sign-in code an app never used is deleted within minutes.
- Song, bid, times and Stripe reference: as part of the payment record, for as long as Romanian accounting law requires (up to 10 years).
- A checkout you started but did not pay for: deleted within 24 hours.
- Stripe's records: kept by Stripe for the periods it sets and the law requires.
- Server logs: our hosting providers' standard period.
- Emails to us: as long as needed to deal with them, then deleted within 2 years, unless needed for a legal claim.
10. What you can ask for
You can ask to see the data we hold about you, get a copy, correct it, delete it, or limit how we use it. You can also object to anything we do based on legitimate interest. Write to contact@67fm.app. If you have a chat account, write from the email address of the Google account you sign in with and tell us your @handle; you can delete your account yourself at any time with "Delete account" in your account menu, or ask us to. If you paid without an account, we find your data through your payment: write from the email address you used at Stripe checkout, and tell us roughly when you paid and which song it was. We reply within one month.
Some things we cannot delete while the law requires us to keep them, such as payment records; we will tell you when that applies. Listeners and chat readers without an account: we hold nothing that could identify you, beyond the providers' short-lived server logs.
If you are unhappy with how we handled your data, you can complain to the Romanian data protection authority, ANSPDCP, at dataprotection.ro, or to the authority in the EU country where you live or work.
11. Keeping it safe
Everything travels over HTTPS, card details never reach us, our database is only reachable by our own server, and Cloudflare limits how many requests one IP address can make per minute. If you spot a security problem, please tell us at contact@67fm.app.
12. Children
Anyone can listen and read the chat. Writing in the chat, and having a chat account, is for people 16 or older. Paying is for people 18 or older, or with a parent's permission. We do not knowingly collect data about children beyond what the payment itself needs. If you think someone under 16 has a chat account, tell us at contact@67fm.app.
13. Changes to this page
If we change how we use your data, we update this page first and change the date at the top.