Privacy Policy
Last updated: October 12, 2026
Beat Protector is operated by BEAT PROTECTOR LLC, a New York limited liability company ("Beat Protector", "we" or "us"), which is responsible for the information described here. This policy explains what information Beat Protector collects, why, who can see it, how long it's kept, and the choices you have. Beat Protector lets music producers share beats behind their own license terms: artists agree to the terms before they can preview or download the producer's files, and the agreement is recorded for the producer.
Questions or requests: admin@beatprotector.com.
Who this covers
- Producers — people who create an account, connect Dropbox and publish license pages.
- Artists — people who open a producer's page, agree to the terms and get the files. Artists don't need an account.
What we collect
From producers
- Account details: your display name and email address. If you sign up with email and password, your password is handled by Google Firebase Authentication and is never visible to us. If you sign in with Google, we receive your name and email address from Google. If you turn on 2-step verification, Firebase Authentication keeps the secret key your authenticator app uses and the date you turned it on; codes are checked by Google and never stored.
- Your landing pages: the producer name, license terms and Dropbox folder you choose for each page.
- Your Dropbox connection: when you connect Dropbox, we store an access token (encrypted) and your Dropbox account ID so we can list the folder you choose and deliver its files to artists who agree to your terms. Beat Protector only has access to its own app folder in your Dropbox, not the rest of your Dropbox.
- A rate-limit marker: the time you last created a page, used to prevent spam.
- Beta access: while Beat Protector is in beta, a note that your account entered a valid invite code, and when.
From artists
- The agreement: your legal name, artist or stage name, email address, the exact license terms you agreed to, and the date and time you agreed.
- A signing code: to confirm your email address, we email you a 6-digit code before the agreement is recorded. Until you enter it (for up to 10 minutes), we keep what you typed into the form and a scrambled (hashed) copy of the code; then they're deleted. The agreement notes that your address was confirmed this way.
- The licensed files: the names, folders and sizes of the files in the producer's folder at the moment you agreed, and a fingerprint of each file provided by Dropbox, so there's a record of exactly what was licensed.
- Downloads and plays: which file you downloaded or played in the player, and when. Repeat plays or downloads of the same file within the same hour are recorded once. Playing a file streams the full file to your browser.
- A download pass: a private link that lets you get the files for the time the producer set for that page (from 1 day to 1 year; 7 days unless they chose otherwise), counted from when you agreed.
Collected automatically
- Bot protection: we use Google reCAPTCHA Enterprise through Firebase App Check to make sure requests come from our real website and not from bots. It runs on the pages where you sign up, log in, sign an agreement, get your files or use your producer account, and loads from Google, which receives your IP address and information about your browser and device for this purpose, under Google's Privacy Policy. It doesn't run on our home page, or on this page or the Terms of Service unless you're signed in.
- Google Sign-In: the login, sign-up and account pages load Google's sign-in helper so the "Continue with Google" button works, which means Google receives your IP address and browser details when those pages open.
- File delivery: when an artist plays or downloads a file, their browser gets it directly from Dropbox, so Dropbox receives their IP address and browser details.
- Rate limits: to stop people from flooding the site with signing codes, emails or beta-code guesses, we count recent attempts per email address, IP address or account. The counters store only a scrambled (hashed) form of the address and are deleted within two days.
- Server logs: our hosting and cloud providers keep standard technical logs (such as IP address, browser type and time of request) to run and secure their services.
Cookies and browser storage
Beat Protector doesn't set cookies. If you're a producer, your browser stores your sign-in session (in its local storage) so you stay logged in; this is needed for the site to work. Google's reCAPTCHA and Sign-In may store their own data in your browser on the pages where they run, to do the jobs described above. We don't use analytics, advertising or tracking cookies, and we don't collect payment information.
How we use it
- To run the service: create accounts, publish pages, record agreements and deliver files.
- To show producers who agreed to their terms, which files were licensed and which were downloaded.
- To send account emails, such as email verification and password resets; to email artists their signing code; to email a PDF copy of each signed agreement to the artist and the producer, with the artist's files link in the artist's copy; and to email artists their files link again when they ask for it.
- To keep the service secure and prevent abuse and spam.
- To comply with the law and respond to valid legal requests.
We don't sell your personal information, and we don't share it for advertising. We don't make decisions about you based only on automated processing.
Giving us this information is up to you, but without it we can't provide the service: producers need an account to publish pages, and artists need to give their name and email address and confirm the code to sign an agreement and get the files.
Legal bases (EEA, UK and Switzerland)
If data protection law such as the GDPR applies to you, we rely on these legal bases:
- Performing a contract (Article 6(1)(b) GDPR): running your producer account and pages, recording an artist's agreement, delivering the files and sending the related emails.
- Legitimate interests (Article 6(1)(f) GDPR): keeping the agreement as the producer's record of who licensed their work and which files they got; protecting the service from bots, spam and abuse (reCAPTCHA, rate limits and logs); and handling legal claims. You can object to processing based on legitimate interests (see "Your choices and rights").
- Legal obligations (Article 6(1)(c) GDPR): when the law requires us to keep or disclose information.
Who can see it
- The producer whose page you signed sees your agreement (legal name, artist name, email, terms, time, licensed files) and your downloads and plays. That's the purpose of the agreement: it's the producer's record of who licensed their work. No other producer can see it.
- Service providers who run parts of Beat Protector for us, only to provide their service:
- Google (Firebase Authentication, which also sends account emails such as email verification, email changes and password resets; Cloud Firestore database; Cloud Functions; Secret Manager; App Check and reCAPTCHA Enterprise; and Google Sign-In)
- Dropbox (stores the producer's files and delivers them to artists)
- Vercel (hosts the website)
- Resend (sends signing codes, files links and the signed-agreement emails)
- Legal requirements: if we're required to by law, or to protect the rights, safety or property of our users or others.
How we protect it
- All connections use HTTPS, and our providers encrypt stored data.
- Dropbox access tokens are additionally encrypted with a separate key, so a copy of the database alone can't be used to open anyone's Dropbox.
- Database rules make sure producers can only see their own pages, agreements, downloads and plays. Agreements can't be edited after they're made.
- Anyone with a landing page's link can see what's on it: the producer name and license terms. The producer's account details and Dropbox folder are never shown to artists.
- Files go directly from the producer's Dropbox to the artist; Beat Protector doesn't store copies of them.
No system is perfectly secure, but we work to protect your information and will notify affected users if a breach affects their personal information, as required by law, including New York's SHIELD Act.
How long we keep it
- Producer accounts, pages, agreements, and download and play records are kept while the producer's account exists, because they're the producer's licensing records.
- Download passes are deleted automatically after they expire.
- Signing codes that were never entered are deleted automatically once they expire (after 10 minutes), at the latest within a day.
- Unfinished Dropbox connections, spam-prevention markers, and email, signing-code and beta-code counters are deleted automatically within two days. The counters store only a scrambled (hashed) form of the email or IP address they count.
- When a producer deletes their account, their login, pages, every agreement signed on their pages, download and play records, beta access and Dropbox connection are permanently deleted, and our access to their Dropbox is revoked.
- Our providers may keep technical logs for a limited time under their own policies.
Your choices and rights
Producers
- See your data on your Dashboard, My Pages, Agreements and Downloads pages.
- Download your data as a spreadsheet from the Account page.
- Delete your account and all its data from the Account page.
- Disconnect Dropbox at any time from the create page, or from Dropbox's own settings.
Artists
Email admin@beatprotector.com to ask for a copy of your information, or to have it corrected or deleted. We may need to confirm your identity first. Because an agreement is also the producer's record of a license, we may let the producer know about a deletion request before acting on it.
Everyone
Depending on where you live, you may have additional rights under privacy laws. If you're in the EEA, the UK or Switzerland, you have the right to:
- access your personal information and get a copy of it;
- have it corrected if it's wrong, or deleted;
- restrict how we use it;
- get the information you gave us in a machine-readable format, or have it sent to another service (portability);
- object to our use of it based on legitimate interests;
- complain to a data protection authority, for example the one where you live or work.
Some of these rights have limits: for example, we may keep an agreement when it's needed to establish or defend a legal claim. Wherever you live, you have the right not to be discriminated against for using your rights. You can use them by emailing admin@beatprotector.com. We aim to respond within 30 days, and within one month where the GDPR applies.
Age requirement
Beat Protector is for people 18 and older. We don't knowingly collect information from anyone under 18. If you believe someone under 18 has used the service, contact us and we'll delete their information.
Where data is processed
BEAT PROTECTOR LLC is based in New York, United States, and our providers store and process information in the United States and may also do so in other countries. If you're in the EEA, the UK or Switzerland, this means your information is transferred outside your home country. Where the law requires a safeguard for these transfers, we rely on the provider's certification under the EU-U.S. Data Privacy Framework (and its UK and Swiss extensions) or on the European Commission's Standard Contractual Clauses in our agreements with them. Email us for more about the safeguard for a particular provider.
Changes to this policy
We may update this policy as the service changes. We'll change the "Last updated" date above, and for significant changes we'll give notice on the site or by email.
Contact
BEAT PROTECTOR LLC
c/o Northwest Registered Agent LLC
418 Broadway, STE N, Albany, NY 12207, United States
admin@beatprotector.com