Privacy

This page describes what actually happens in the software, not what would be convenient to claim. Where a protection comes from the architecture, it says so; where it comes from a policy, it says that instead.

The short version

Your song is not public unless you make it public. Coroas never creates a public URL for your work on its own.

What is stored, and where

• Drafts live in your browser. Songs you write are kept in this device's local storage. Clearing your site data deletes them, and we cannot recover them.
• Cloud storage is opt-in. A song is only copied to our database when you explicitly save it to your library.
• Your account. Authentication is handled by Clerk, which stores your email and sign-in credentials. We never see or store your password.
• Subscriptions. A paid plan is recorded against the Solana wallet address that paid for it, together with the transaction signature and the period end. There are no card payments, so no card details exist anywhere in this system.

What we send to model providers

Generating a Song Room sends the text you submitted, and your tone settings, to OpenAI for processing. Editing a line sends that line and a short context. Cover art is generated from a structured scene summary — place, objects, season, mood — and never from your lyrics or your source story.

Voice notes

Audio is transcribed in memory on our server and then discarded. It is not written to disk, not written to object storage, and not retained after the request completes. Source audio is only kept if you explicitly choose to save the original recording, and you can delete it afterwards.

What is never put onchain

A Songprint publishes a SHA-256 hash and nothing else. Lyrics, story text, private notes and audio are never written to a blockchain by this application. If you include an audio file, its bytes are hashed on your device and only that hash is included in the fingerprint.

Analytics

We record product events — a song was generated, a cover was made, checkout was started — with no creative content attached. The analytics layer strips any property whose name suggests it might carry lyrics, story text, transcripts or titles. If no analytics provider is configured on a deployment, nothing is sent at all.

Addresses and abuse prevention

Rate limiting needs to tell requesters apart. We do not store raw IP addresses: the forwarded address is combined with a server-side secret and hashed with HMAC-SHA256, and only that digest is held in memory for the length of the rate-limit window.

Deletion

Local songs are deleted from your library page and are gone immediately. Cloud-saved songs, their versions, assets and any saved audio are deleted from your account settings, and the deletion is performed against the database rather than flagged. Songprints are an exception we cannot fix: a public blockchain record cannot be withdrawn, which is why only a hash is ever written to it.

Contact

Privacy questions can be sent to the address published at coroas.blog.