Your listening room

Privacy policy.

Updated November 20, 2026

Cadenza is developed by Zhaonian Luan. This policy describes the information used by the iPhone and iPad app and this support website. Contact lzn0830@gmail.com for privacy questions or requests.

Cadenza is in a limited internal beta. Apple and Google sign-in, cloud storage, composition, and listening links are enabled for testing. Google sign-in is limited to approved test accounts; Facebook sign-in remains disabled. Subscription testing uses Apple’s sandbox. The sections below describe enabled features and the upcoming Facebook integration. The bundled piano preview plays locally.

Your device and cloud library.

Your saved audio, titles, musical notes, favorites, and library metadata are stored in the app’s local files. Your sign-in session and unfinished request identifier, musical draft, and acceptance state are kept in the iOS Keychain. Generated recordings and their titles, musical notes, styles, durations, and creation dates are also saved privately on Cadenza’s backend so you can restore your collection on another device. Favorites remain local. You can remove a device download while retaining the cloud copy. Device backups may include app files according to your Apple backup settings.

Cadenza does not request access to your microphone, contacts, photos, or precise location. Cadenza does not use your information for advertising tracking. Facebook sign-in uses Limited Login, with automatic app-event logging, product-improvement logging, and advertiser-identifier collection disabled.

When you sign in.

Sign-in is required to enter the app after the introduction. Your first sign-in creates your account automatically. Saved sessions let you return without signing in each time; signing out or a rejected session returns you to the account screen. Public listening links do not require an account.

You can choose Apple, Google, or Facebook when each option becomes available. The provider verifies your identity and sends Cadenza a signed identity token. Apple and Google also provide a one-time authorization code. We validate these to create a Cadenza account and keep session credentials in the iOS Keychain. Use the same provider to return to the same collection; accounts are not automatically linked by email.

The backend stores a provider-specific account-identifier hash, a random Cadenza account identifier, session-token hashes, and encrypted credentials needed to revoke the provider connection on account deletion. For Apple and Google this is a refresh token; for Facebook it is the app-specific user identifier used with our server credentials. Apple is not asked for your name or email. Google’s basic sign-in and Facebook’s public-profile login may supply profile information in their sign-in response, but Cadenza does not persist your profile name, photo, or email in its account database or publish them on listening pages. The sign-in providers process login and device information under their own policies.

When you compose.

After you enable permission to send prompts, your musical description, mood, ensemble, tempo, and approximate duration are sent through Cadenza’s server to Google Lyria. After the server accepts a request, generation can continue while the app is closed or disconnected. The cloud stores the finished audio, and the app downloads it when you return with a connection. Your chosen library title is not included in the generation prompt.

The server temporarily stores the full generation prompt in a durable job record until the job completes, fails, or expires. Queue messages contain only the request identifier. The server keeps request identifiers, prompt hashes, timestamps, completion status, and account allowance records to deliver recordings, recover interrupted downloads, and prevent duplicate requests. The cloud library stores your original musical note and chosen settings along with the recording. Complete cloud recordings remain until you delete the piece or account. Incomplete uploads are queued for cleanup after about ten minutes.

Google processes the prompt and output under its Gemini API terms and privacy policy. Unpaid API services may use inputs and outputs to improve Google’s products and may involve human review. Paid API services have different data-use terms. Avoid sensitive, confidential, or personal information in musical descriptions. Cadenza’s current experimental generation service uses the unpaid API. The in-app consent explains this before you send a musical description.

Sharing your music.

Recordings are private until you choose Create listening link. Anyone who has that link can see its title, artwork, mood, ensemble, composer inspiration, and duration, and play its audio in a browser without an account or the app. Your musical note, account identifier, and sign-in profile are not shown. Link previews may display the title and artwork in the service where you share the URL. Listening pages ask search engines not to index them; possession of the link grants access.

Stop sharing disables future access through that link. Deleting the cloud piece or account also disables its links. Previously saved or exported copies, and previews cached by another service, are outside Cadenza’s control. Exporting an audio file uses your device’s share sheet and the destination you choose.

Subscriptions.

Apple processes payments. Cadenza uses RevenueCat to validate purchases and provide subscription access. RevenueCat receives a pseudonymous app user identifier, purchase and receipt information, subscription status, and technical information such as app and operating-system versions. An anonymous RevenueCat identifier may be created before you sign in; it is associated with your Cadenza identifier when you sign in. Cadenza does not receive your payment-card number.

See RevenueCat’s privacy policy and Apple’s privacy policy for their practices.

Hosting, security, and support.

Cloudflare hosts the Cadenza API, listening pages, library metadata, and private cloud audio. Network providers process IP addresses and request information to deliver and protect the service. The app server temporarily uses a hash of an IP address to limit sign-in and public listening requests. Our support website is hosted with GitHub Pages; we do not add analytics scripts, tracking cookies, or advertising to these pages.

If you email support, we receive your email address and the information you choose to include. We use it to respond and resolve the issue. Service providers may process information in countries other than your own, including the United States.

Retention and deletion.

Local recordings remain until you delete them or remove the app. Exported copies and device backups are under your control. Sessions expire after 30 days. Server account and allowance records remain while your account exists; temporary security records expire automatically. An anonymous generation ledger, containing request identifiers and timestamps without your account identifier or prompt, remains to track total service usage.

Use Settings → Delete account to remove the server account, sessions, generation records, cloud-library metadata, and listening links, and queue cloud audio for deletion. The server also requests revocation of the selected sign-in provider connection and RevenueCat customer deletion. If a provider is unavailable, a minimal cleanup record is retained and retried; encrypted provider credentials are erased after revocation, and the cleanup record is erased after provider cleanup finishes. Recreating an account may be temporarily unavailable while this finishes.

Account deletion leaves local recordings on the device and does not cancel a subscription. Cancel separately in Apple Account subscription settings. Apple and other providers may retain transaction or security records under their own policies and legal obligations. Contact support if you cannot access the in-app deletion control or need help with a data request.

Facebook data deletion.

Once Facebook sign-in is enabled, sign in to Cadenza using the same Facebook account, open Settings → Delete account, and confirm. This removes your Cadenza server data and requests removal of the Facebook app connection as described above. If you cannot sign in, email lzn0830@gmail.com with the subject “Cadenza Facebook data deletion”; we will help verify ownership and process the request. Never send a password or authentication token. Removing the connection in Facebook settings alone is separate from deleting your Cadenza account.

Your choices.

You can turn off Allow sending musical prompts to Google in Settings at any time to stop new prompt submissions. This does not withdraw a request already sent. You can sign out, remove downloads, delete cloud recordings, revoke listening links, export your music, manage your subscription, or request account deletion separately. Depending on where you live, you may have rights to access, correct, delete, or restrict use of personal information. Contact us to make a request; we may need to verify account ownership.

Age and changes.

Cadenza’s cloud composition service is intended for adults aged 18 and over. We do not knowingly collect personal information from children. Contact us if you believe a child has supplied personal information.

We may update this policy as the app changes. The date above identifies the latest revision; material changes to data handling will be disclosed in the app before the affected feature is used.