1. Who We Are
1.1ZeroOne Beats ("we", "us"), Denmark, CVR 38227386, operates the ZeroOne Beats website, music submission service, live radio and ZeroOne Beats Premium apps. This policy explains how we handle information across these services. For privacy questions, email [email protected].
2. Data We Collect
| Data | Source | Purpose | Lawful Basis |
|---|---|---|---|
| OAuth display name | Your chosen sign-in provider (Twitch, Google, or Discord) | Shown to you as confirmation of who you're signed in as | Legitimate interest |
| OAuth provider & user ID | Your chosen sign-in provider | Identity verification; enforcing the 3-submissions-per-24h rate limit | Legitimate interest |
| Artist name, song title, track link, artist profile URL | You (submission form) | Processing and storing your music submission | Contractual necessity (you choose to submit) |
| Submission IP fingerprint | Your browser / network | Abuse and fraud prevention | Legitimate interest |
| Submission timestamp | Server | Record-keeping | Legitimate interest |
| Account email, display name, provider identifiers and profile picture | Your sign-in provider and account settings | Account management, linked sign-in and Premium access | Performance of the service you request; legitimate interests in account security |
| Favourites, playlist names, saved track IDs, banner choices and sync records | Your activity in supported apps | Save and synchronise your music library, including resolving conflicting edits | Performance of the service you request |
| Feedback messages, app version, account identity, request IP address and user-agent; website screenshots if you attach them | You and technical information sent with your request | Respond to feedback, troubleshoot and prevent abuse | Legitimate interests in supporting and securing the service |
| Network requests and technical service logs, which can include IP addresses and requested resources | Your app, browser and our service infrastructure | Deliver streams and artwork, diagnose faults and secure the service | Performance of the service; legitimate interests in service security |
2.1Music submissions use a keyed, pseudonymous IP fingerprint for abuse prevention. This is separate from raw IP addresses that may appear in feedback records and service or access logs. These records help us deliver the service, investigate faults and prevent abuse; their retention is described in section 5.
2.2Your favourites and playlists are stored with your account, including names, track identifiers, banner choices and the records needed to apply changes and recover from conflicting edits. Apps keep local copies and can queue library edits while offline. Deleting local app files does not delete the cloud library. Settings such as crossfade and app volume remain on the device.
2.3App feedback contains your message, account identifier, display name, selected category and app version. The server also records the request IP address and user-agent. Website feedback can include email, page context and screenshots you attach. Feedback is available to authorised staff, not displayed publicly by default.
2.4Our service records are hosted on our server in the United States. Streaming, artwork delivery and sign-in also involve our hosting, network and authentication providers. These providers may process data outside the EEA. Contact us for details of the recipients and applicable transfer safeguards. The independent providers' own privacy notices apply to their services.
2.5Cloudflare processes network request information, including IP addresses and approximate country inferred from those addresses, to deliver and protect the service and provide traffic analytics. This does not use your device’s GPS location.
3. Cloudflare Turnstile (CAPTCHA)
3.1The submission form uses Cloudflare Turnstile to prevent automated abuse. Cloudflare may process your IP address and browser signals to determine whether you are human. This is governed by Cloudflare's Privacy Policy.
4. Session Cookies
4.1When you sign in, we set a session cookie to keep you authenticated during your visit. This cookie:
- 4.2Is HttpOnly (not accessible by JavaScript)
- 4.3Is Secure (only transmitted over HTTPS)
- 4.4Expires after 24 hours
- 4.5Contains a random session identifier used to look up your sign-in session, not your provider password
5. Data Retention
5.1Submission files (WAV and metadata JSON) are retained for as long as they are relevant to our playlist management. We do not have a fixed automatic deletion schedule. You may request deletion at any time (see Section 7).
5.2Website sign-in sessions expire after 24 hours. Expired records are removed through session-store cleanup. Mobile apps use separate authentication tokens to keep you signed in; signing out clears the app's stored session credentials.
5.3We keep your active account profile and cloud music library while you use the account. Account deletion removes these records from the active service, including linked sign-in identities and saved favourites and playlists.
5.4Open feedback is retained while needed to investigate or resolve the report. Closed reports, their archived copies and attached screenshots become eligible for automatic deletion 90 days after closure; the cleanup runs hourly. Account-deletion requests also cover associated feedback unless a documented exception applies.
5.5Routine technical logs and routine backup copies are retained for up to 30 days. Backups are restricted recovery copies rather than an active account service. Recovery procedures must reapply recorded deletion requests before restored data is used. The account service also checks deletion records when reading accounts and feedback.
5.6Information needed for an unresolved security incident or a legal obligation may be retained separately for that purpose. We record the reason and a review date, restrict its use, and remove it when the reason no longer applies. Submission, competition and payment records are subject to the additional purposes described in this policy.
5.7We keep a restricted record of deleted sign-in identifiers and the deletion date for 91 days to reject previously issued sign-in tokens and prevent recovery copies from recreating deleted accounts. This record contains no password or feedback message. It is removed after the retention job confirms that routine recovery copies have expired. If cleanup fails, the record remains only until recovery safety is verified.
6. Third-Party OAuth Providers
6.1We use Twitch, Google and Discord for sign-in. Your chosen provider supplies an account identifier and display name and, depending on the provider and permissions, your email address and profile picture. We use these details to identify your account, support linked sign-in methods, display your profile and connect eligible Premium access. We do not receive your provider password. Each provider's privacy policy governs its own sign-in processing.
7. Your Rights (GDPR)
7.1If you are located in the European Economic Area or United Kingdom, you have the right to:
- 7.2Access - request a copy of the personal data we hold about you
- 7.3Rectification - request correction of inaccurate data
- 7.4Erasure - request deletion of your account and associated personal data, subject to any applicable legal exceptions.
- 7.5Restriction - request that we limit processing of your data
- 7.6Objection - object to processing based on legitimate interest
7.7To exercise these rights, email [email protected] or use the Contact page and choose "Privacy / GDPR data request". We will respond within 30 days. We may need to verify that the request concerns your account without asking for your provider password.
7.8You also have the right to lodge a complaint with your local data protection authority.
7.9To delete your account, open Account, then Settings, on the website and find Delete account at the bottom. Sign in with the same linked provider used in the app. Review the consequences and type DELETE to confirm. The Android app links to this route from its account page. See our account deletion instructions for help or an email request option. Signing out or uninstalling does not delete the account.
7.10If you have an active recurring subscription, cancel its renewal through Manage Billing before deleting your account. If cancellation or deletion fails, contact [email protected]. Deleting a ZeroOne Beats account does not delete your Google, Twitch or Discord account or the payment provider's independently held records.
7.11You can request deletion of specific data, such as cloud favourites, playlists or feedback, without deleting your ZeroOne Beats account. Email [email protected] or choose ‘Privacy / GDPR data request’ on our Contact page, and identify what you want removed. We may verify account ownership and will respond within 30 days. Routine backup copies expire within 30 days; any necessary security or legal retention follows section 5.
8. Payment Processing (ZOB Premium)
8.1If you subscribe to ZOB Premium, payment is processed by Lemon Squeezy (Lemon Squeezy, LLC), which acts as the merchant of record. We do not collect or store your payment card details. Lemon Squeezy shares the following information with us about each subscriber:
- 8.2The e-mail address you used to subscribe
- 8.3Your country of residence (for tax compliance)
- 8.4Your subscription status, renewal dates, and any cancellation
8.5We use this information solely to provide and support your subscription. Lemon Squeezy's own handling of your payment data is governed by its Privacy Policy.
9. Contact Form (Web3Forms)
9.1If you message us through the Contact page, your submission is processed by Web3Forms, which receives your name, email address, message, and the topic you selected, and forwards them to our inbox. We do not store your message on this website. Web3Forms may keep operational logs in accordance with its own Privacy Policy. If you prefer not to use a third-party processor, you can email us directly using any of the aliases referenced from the Contact page.
10. Automated Lyric Review (OpenAI)
10.1When you submit a track, we retrieve the lyrics from the public page you link on the AI music platform you name (for example your Suno track page) and send that lyric text to OpenAI, which returns an automated summary of the content it contains - for example profanity, violence or adult themes. We use this only to check that the Clean/Explicit rating on a submission looks right before a human reviews it. Our lawful basis is legitimate interest in classifying content we broadcast.
10.2Only the lyric text is sent to OpenAI. Nothing else from your submission goes to them - not your name, your email address, your account details, or the audio file you upload to us. Those stay on our own systems.
10.3The result is visible only to station staff - never publicly, and never on your own submissions page. It is advisory: it can flag a submission for closer review, but it never approves, rejects or re-rates a track on its own. A human makes every decision.
10.4We use the OpenAI API for this review, with response storage disabled in our request. OpenAI handles API content under its business terms and Data Processing Addendum; disabling response storage does not itself disable provider abuse-monitoring logs. The lyrics come from the linked Suno page. Contact us if you need a human-only review or want the stored result removed.
11. Social Campaign Reporting
11.1If you arrive through one of our campaign links, we count page opens, web-player playback starts, playback reaching 60 seconds, and completed music submissions. This helps us understand which posts bring people to the radio or encourage submissions.
11.2The campaign database uses a random visit reference, which expires after 24 hours and is removed by scheduled cleanup. It does not store visitor names, account IDs or IP addresses. Daily totals are retained for up to 366 days. Campaign reporting does not create a persistent browser identifier or use local storage. The normal sign-in cookies described above still apply.
11.3Campaign measurement is skipped when your browser sends Do Not Track or Global Privacy Control. You can also open the web player or submission form without a campaign link. We use our own server for these counts, with no advertising pixels or third-party analytics service.
12. Seasonal competitions and prizes
ZeroOne Beats, Denmark, CVR 38227386, is responsible for the event information described here. Contact us through the website's Privacy / GDPR data request contact option.
Country eligibility and verification
The event rules set the age, residence and prize eligibility requirements. Residents of the following countries and territories are excluded from participation and both prize types:
- Countries: Belarus, Belgium, Brazil, Cuba, Iran, Italy, Mexico, North Korea, Russia and Syria.
- Canadian province: Quebec.
- Ukrainian territories: Crimea and Sevastopol, and the non-government-controlled areas of Donetsk, Luhansk, Kherson and Zaporizhzhia.
At entry we record your eligibility declaration, the version of the rules you accepted and the time of acceptance. We do not automatically verify your location through this declaration. If verification is necessary, we may ask privately for your country of legal residence and the minimum supporting information needed to check eligibility or a payment restriction. We do not require every listener to upload identity documents. We will explain any specific evidence request and how to provide it privately.
Residence information and supporting evidence are used for eligibility, prize administration and any applicable legal obligations, on the lawful bases below. They are not public leaderboard fields or marketing information. Access is limited to the people administering the event and any recipient necessary for payment or a legal obligation. Once a verification issue is resolved, we delete or redact supporting material that is no longer necessary; minimum decision records and legally required payment records follow the retention rules below. Contact us to correct an inaccurate declaration or ask for a human review.
Suno Premier prize eligibility also requires lawful access to Suno Premier and a PayPal account able to receive the prize payment from Denmark. These prizes are void where PayPal services are legally restricted or unavailable for receiving that payment. We use your separate Suno/PayPal eligibility confirmation to determine whether you may qualify for a main-prize place. It does not prevent otherwise eligible participants from collecting songs or winning ZeroOne Beats Premium rewards.
Information and purposes
We use your linked account identifiers and display name, your rules and eligibility confirmations, claim times and outcomes, collected songs, reward records and delivery status to run the competition and provide your prizes. Linking Twitch and Discord is required; Kick participation also requires a linked Kick account. You cannot enter without the necessary linked identities and eligibility confirmations.
Your display name, collection total and first-finder total may appear on the public event leaderboard. Your individual saved collection and prize details are available through your signed-in account. Claim ordering and limits are calculated automatically under the event rules. You can ask the ZeroOne Beats Owner to review an error or disputed result through our support routes.
If you earn a main-prize place, we ask privately for your PayPal email and confirmation that your account can receive the prize. We use this to check and arrange delivery, record its outcome and handle related support. Without suitable payout details we cannot deliver a PayPal prize. We never ask for your PayPal password or login code. Gift keys must be kept private by you and anyone you give them to.
We process information necessary to administer your entry and deliver an earned prize to perform the event agreement. Our legitimate interests in fair competition, account security, preventing abuse and resolving disputes support the necessary verification and audit records. Records required by applicable accounting or other law are retained to meet those legal obligations. Entry does not subscribe you to marketing.
Access, recipients and hosting
PayPal emails, prize keys and payment references are not public leaderboard information. Private payout details are restricted to the owner and the access needed to administer the payment. Discord processes direct messages used to deliver Premium keys. PayPal receives the recipient and transaction information necessary to process a payment and handles it under its own privacy notice. We will explain any additional information or recipient before using a different prize-delivery arrangement.
Our event records are hosted on our server in the United States. Linked platforms and delivery providers may also process data outside the EEA. Their own privacy notices describe their processing and international-transfer arrangements. Contact us for information about our hosting arrangements and the applicable safeguards. See the Discord and PayPal privacy notices linked in the full policy.
Retention and rights
We retain entry and claim records for the event and for as long as necessary to complete prize delivery and resolve an outstanding dispute, delivery fault or suspected abuse. After those purposes have ended, we review the records and delete or anonymise information no longer needed.
Saved collections and the minimum records needed to show earned achievements remain linked to your account while you keep that history. You may request its deletion. Payment evidence required for accounting or a specific legal claim is kept separately for the applicable requirement; only information necessary for those requirements is retained.
You may request access, correction, deletion, restriction and, where applicable, portability, or object to processing based on legitimate interests. Some records may need to be retained for an outstanding legal obligation or claim. Contact us using Privacy / GDPR data request on the contact page. You can complain to Datatilsynet or another competent supervisory authority.
Provider notices: Discord and PayPal.
13. Changes to This Policy
13.1We may update this policy from time to time. The "Last updated" date at the top of this page reflects the most recent revision.