Privacy Policy
Last updated: September 7, 2026
This policy explains how LyriaX handles information when you use www.lyriax.ai.
Information we process
We process the account information supplied by your sign-in provider, including your name, email address, and profile image. We also store the music briefs, titles, lyrics, instrumental choice, generation status, and completed audio associated with your account.
Technical records may include timestamps, request identifiers, error details, and security logs needed to operate and protect the service. If you enable browser notifications, we store the Web Push subscription endpoint and encryption keys issued by your browser.
When you use a paid plan, we store Stripe customer, subscription, product, price, invoice, order, credit-balance, and credit-ledger identifiers and status. Billing contact details may include your name, phone number, company, tax ID, and billing address. Payment-card details are collected and processed by Stripe and are not stored in LyriaX's database.
How generation data moves
Your combined production brief and lyrics are sent to our model-inference provider to run Google Lyria. The provider returns the generated audio and related model output. Completed MP3 files are copied to our Cloudflare R2 storage so they remain available in your account.
If you leave the title blank, the music description and a lyrics excerpt are sent to a text-model service through OpenRouter to suggest a title. The description, title when available, and a lyrics excerpt are also sent to an image-generation service to create the song’s cover art. Generated titles and covers are saved with the song; covers are stored in Cloudflare R2 alongside the audio.
The product is limited to its website, account library, and the Lyria generation workflow described here.
Service providers
We use service providers only to deliver LyriaX:
- Google for optional account sign-in and the underlying Lyria model.
- A model-inference provider for queued Lyria generation and signed completion webhooks.
- Cloudflare R2 for durable generated-audio storage and delivery.
- A managed PostgreSQL provider for account and project records.
- Stripe for hosted subscription checkout, recurring billing, invoices, and the customer billing portal.
- Browser push infrastructure when you opt into notifications.
- OpenRouter and its selected text-model provider for automatic song titles, and an image-generation provider for song cover art.
Each provider processes data under its own terms and privacy commitments.
Retention and deletion
Removing a song from the library hides it from your account view; it does not immediately delete the stored audio, cover, or associated records. To request deletion of stored song data or closure of your account, contact [email protected] from your account email. Limited records may be retained for security, billing, dispute resolution, tax, accounting, or legal obligations. Temporary files held by a provider follow that provider’s retention practices.
To request access, correction, export, or deletion, email [email protected] from the address associated with your account.
Security
We use signed webhook verification, request-ID matching, bounded media downloads, encrypted transport, access controls, and isolated credentials. No internet service can guarantee absolute security.
Children
LyriaX is not directed to children under 13, or the higher minimum age required in their jurisdiction.
Changes
We may update this policy as the focused Lyria product or its service providers change. The date above identifies the current version.
Contact
Privacy questions: [email protected]