Privacy Policy

• > Account data — when you sign in with Google OAuth we receive your email address, display name, and avatar image. We never see your Google password.
• > Generation data — the lyrics, style tags, duration, and settings you submit, plus the audio, video, and artwork files the platform produces for you, and quality/engagement metrics about those tracks (plays, downloads, shares, automated quality scores).
• > Payment data— purchases are processed by Stripe. We store the amount, timestamp, and Stripe's reference IDs. We never store card numbers.
• > Technical data — standard server logs (IP address, user agent, timestamps) used for rate limiting, abuse prevention, and debugging.

We set exactly two kinds of cookies:

• > Session cookies — keep you signed in (NextAuth). Essential; removed when you sign out.
• > az_ref— set when you arrive through a creator's affiliate link, so the referring creator gets credit if you make your first purchase. It stores only the referral code, not your identity.

No third-party advertising or cross-site tracking cookies. None.

• > run the service: generate tracks, store them, and serve them back to you;
• > process credit purchases and affiliate payouts;
• > improve generation quality (e.g. the A/B preference picks you submit train ranking for your account);
• > prevent abuse (rate limiting, fraud detection);
• > send transactional email (receipts, security notices). No marketing spam.

The songs and lyrics you generate on Azrael Music may be used to train and improve Azrael's AI models — for example, to make generated tracks sound better and follow prompts more closely. Training use covers the generated audio, the lyrics, and the style tags and settings attached to them.

You can opt out at any time in Settings. When you opt out, your tracks are excluded from future training datasets. Opting out does not affect your ability to use the platform.

Account and generation records live in a PostgreSQL database on infrastructure we operate. Audio, video, and artwork files are stored in Backblaze B2 object storage. Traffic is routed through Cloudflare (DNS/TLS). Backups are encrypted and stored in B2.

Only processors that are required to run the service:

• > Stripe — payment processing;
• > Google — OAuth sign-in;
• > Backblaze — file storage;
• > Model inference providers — the lyrics and prompts you submit are sent to the AI providers that run generation (music models and, when you use the ghostwriter, LLM providers). They process the content to produce your output.

We do not sell your personal data. We disclose data beyond the above only if legally compelled, and we will tell you when the law allows us to.

Tracks you make public appear in the community feed and on shareable track pages, along with your display name. Anyone can listen to and link to them. You can flip a track back to private at any time; copies others already downloaded are outside our control. Everything else — private tracks, your history, your credit balance — is visible only to you (and to you-authorized agents via the Agent API).

We keep your data while your account exists. Ask us to delete your account and we will remove your personal data, private generations, and stored files within 30 days, except records we must keep (e.g. payment records for tax law) and content subject to a legal hold. Public tracks are removed from the feed on deletion.

Wherever you live, we honor the core rights: access a copy of your data, correct it, delete it, export it, and object to processing. California residents: we do not sell or "share" personal information as defined by the CCPA/CPRA, so there is nothing to opt out of. EU/UK residents: our lawful bases are contract (running the service you signed up for) and legitimate interest (abuse prevention).

Exercise any of these by emailing [email protected] from your account email.

The service is for adults (18+). We do not knowingly collect data from minors; if we learn an account belongs to someone under 18, we delete it.

Material changes to this policy will be announced on the site before they take effect. Questions: [email protected]. Related reading: Terms of Service and Content Policy.