Privacy Policy

1. Who operates the service

BeatLark is an independently operated website that provides AI song and instrumental music generation. The service is operated by an individual based in China under the BeatLark brand. For questions about your information or to exercise a privacy right, email [email protected].

2. Information handled by the BeatLark website

Depending on how you use the website, we handle account details such as your email address, username, profile image, login-provider information, and verification records; music descriptions, lyrics, song settings, creation history, generated audio, and song metadata; subscription, credit, payment-session, and activity records; and technical or security information such as request logs, IP addresses, browser information, and authentication identifiers. Password sign-in uses a stored password hash rather than a readable copy of your password. Stripe collects payment details through its checkout.

Your browser also stores the identifier of your last opened creation so it can be restored later. If you fill in the song form before signing in, the current tab temporarily saves your description, lyrics, and settings so you can continue after sign-in. The Cookie Policy describes these storage items and how to clear them.

For traffic measurement, the browser sends only a broad channel category and one of the public page categories. The server increments a shared counter for that channel, page, and UTC date. Raw campaign parameters, referring URLs, visitor identifiers, and private page paths are not included. The collector does not write analytics cookies or associate page views with an account, song, or payment. It does not store IP addresses, device details, or individual visit timestamps in these statistics. Hosting and security logs are separate and may contain technical information needed to operate the service.

3. How website information is used

We use this information to create and secure accounts; generate and deliver songs; save creation history; manage credits and subscriptions; process payments and refund requests; prevent fraud and abuse; troubleshoot errors; meet legal obligations; and respond to service or support requests. The current generation flow sends your song inputs to external providers for processing. Each provider has its own terms governing processing, retention, and any use of inputs or outputs; this policy does not promise that every provider offers the same data controls.

4. Legal bases

Where data-protection law requires a legal basis, we rely on performance of a contract to provide accounts, music generation, and paid services; legitimate interests to secure the service, prevent abuse, and resolve support issues; and legal obligations for records we must retain. Where processing requires consent, it must have a separate valid basis in consent. Agreeing to the Terms of Service is not consent to optional tracking. You may withdraw consent for processing that relies on it.

5. Service providers and international transfers

Providers receive information needed for their role. Replicate and MiniMax process the descriptions, lyrics, and settings submitted for music generation. Cloudflare R2 stores generated audio and supports playback and download. Stripe processes checkout, payment, subscription, and refund information. Google supplies account information when you choose Google sign-in, and Resend processes recipient details and service-email content. OpenRouter is integrated for conversational songwriting requests; the standard song form submits directly to the music-generation flow.

Website hosting, database, security, and network providers also process information needed to operate the website. Depending on the provider and its infrastructure, information may be processed outside your country. Provider privacy notices and contractual arrangements determine the applicable locations and transfer protections. You can contact us for details relevant to your information. We do not represent that all information stays in one country or that all providers have identical retention practices.

Provider information: Replicate privacy policy, MiniMax terms, Stripe privacy policy, Cloudflare privacy policy, OpenRouter privacy policy, Resend privacy policy, and Google privacy policy.

6. Storage and retention

Account, creation, credit, subscription, and payment records are kept in the service database. Creation records and generated audio do not currently have an automatic deletion schedule. Retention depends on whether the information is needed to provide your account and saved songs, resolve a support or refund request, prevent abuse, or meet accounting and other legal obligations. These criteria are not a promise to keep every recording permanently. Download songs you want to keep independently.

Generated audio is stored separately from its creation record, so a history entry may remain after its audio is unavailable. Provider logs and backups may follow separate retention schedules. You can request deletion by email; we may retain limited records where required by law or needed to resolve a dispute or prevent fraud. Clearing browser storage does not delete server-side creation or payment records.

Traffic statistics retain daily totals without visitor or account identifiers. Older records from the former account-linked attribution system may still be held, but the current collector does not add to those profiles or conversion records. Removing the old browser cookie does not erase those server-side records; contact us to request deletion of information associated with your account.

7. Your choices and rights

For website personal information, subject to applicable law, you may request access, correction, deletion, restriction, or a copy, or object to certain processing. Email [email protected] with your request. We may verify your identity before responding and may retain limited information where required by law or needed to protect the service. A deletion request for BeatLark website data does not itself remove browser-history entries or independently held provider records. You may also complain to the data-protection authority in your place of residence.

The traffic collector skips statistics requests when your browser signals Do Not Track or Global Privacy Control. It does not rely on a consent popup or store a separate tracking preference cookie. Necessary sign-in and song-form storage continues to work independently.

8. Security and children

We use reasonable technical and organisational measures to protect information, but no online service can guarantee absolute security. The service is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

9. Updates

We may update this policy when our service or legal obligations change. The latest version will be posted on this page with a new “Last updated” date.