1. About this policy
This draft describes data handling in the Cadenza application and this public website. Contact cadenzaclassicalmusic@gmail.com with privacy questions.
Confirmation needed: the legal name and address of the person or organisation responsible for Cadenza, applicable jurisdictions and the final effective date.
2. Accounts and authentication
Cadenza uses Supabase Auth for email and password authentication, account confirmation and password resets. Account information can include your email address, account identifier and a display name supplied during registration. Sign-in creates session credentials so the application can keep you signed in.
The web application stores its session in browser local storage. Android stores its session in native application storage. This public website has no sign-in form and does not receive your Cadenza password.
3. Your library and listening data
Your library can include works, artists, recordings, releases, collections, ratings, favourites, notes, tags, saved links, listening events and selected movements. These records support library management, your listening journal and related application features.
On Android, the working library is held in a local SQLite database. A local library can be used without an account. When cloud sync is enabled and your account has access, library records and preferences are replicated to Supabase. The web application uses the account’s cloud library directly.
Signing in does not automatically add a separate local library to an account; the application asks before importing it. Signing out normally leaves a device copy in place. Local data and exported backup files can remain after account deletion.
4. Pins, links and images
Pins can contain a page address, title, description, image, your note, tags and links to relevant music. They are stored with your library and can sync with it.
When you ask Cadenza to read a page, its metadata service receives the URL and contacts the source website or its metadata service. Selected page details are cached across users. Image processing may use a server-side browser to create a screenshot or a card image. Stored Pin images are held in a public Supabase Storage bucket and may be reused for the same source page; they are not private attachments. Your personal Pin notes and library associations are separate from that shared metadata.
Custom library covers use a private storage bucket. New cloud uploads of custom covers and server-created Pin images are subject to the account’s Forte entitlement. Original website images and local caches may also be used.
5. Encore search and personalisation
Encore sends your search terms to the configured Cadenza search service. Catalogue and related-reading requests use search terms, public music identifiers or result URLs. The inspected clients do not send your private notes, ratings or entire library with these search requests.
Recent search text and timestamps are saved locally. For eligible Forte accounts, recent searches can also be stored in account preferences and shared across devices. Clearing the visible history propagates removal records; it should not be understood as immediate erasure of all copies of the search text.
Personalisation stores choices you make about websites: site ratings, blocked sites and hidden-result URLs, including titles and dates. These records are held directly in Supabase for the account, outside library sync and library backups. Current ranking uses these explicit preferences. Older feedback records from a retired personalisation system may remain.
Optional model-assisted query interpretation exists in development and explicit test builds. It is not enabled by the ordinary production access path reviewed for this draft.
Confirmation needed: the deployed search configuration, any test-build model provider and its processing terms, and the removal or retention of legacy feedback.
6. Services and external content
Supabase provides authentication, cloud database storage, file storage and backend functions. Cadenza also uses its Opus catalogue and graph services and its search services to return music information and related reading. The page-image service has a Vercel implementation.
Depending on the feature and configuration, catalogue data and enrichment involve MusicBrainz, Cover Art Archive, Wikimedia, Open Opus and Discogs. Video search has a Brave Search integration; podcast discovery has a Podcast Index integration. Search providers receive the terms needed for those requests.
Playing YouTube videos loads Google’s player services, including a privacy-enhanced embed. Playing podcast audio contacts the publisher’s media host. External images and links can also contact third-party services. Those services have their own data practices.
Confirmation needed: the providers actually enabled in production, their roles and agreements, hosting regions, subprocessors and any international transfer arrangements. No particular location or transfer safeguard is asserted by this draft.
7. Forte and future subscriptions
Forte access is recorded as an account entitlement, with status and lifecycle information such as an end date. The inspected code associates this entitlement with cloud backup, sync and enhanced discovery. The discovery preference can be switched off without cancelling that entitlement.
The reviewed application has no completed store or web billing integration. This website does not collect card information or sell subscriptions. Any future purchase flow will need to identify the payment provider and explain what transaction or subscription information Cadenza receives before it is offered.
8. Local storage, website hosting and logs
The application uses device files, SQLite, local storage and IndexedDB for sessions, preferences, artwork, recent searches, media progress and caches, depending on platform. Playback progress and other preferences can also be saved through the account’s cloud data.
This public website is static HTML and CSS hosted through Cloudflare Pages. Its own code sets no cookies, loads no analytics or trackers, and runs no JavaScript. It uses locally hosted branding assets and system fonts. Visiting it still involves network requests to Cloudflare, which can process connection information such as an IP address and request details to deliver the pages.
Cadenza backend services include error and operational logging; the inspected search service also uses request IP addresses for rate limiting. No dedicated analytics SDK was identified in the inspected application client.
Confirmation needed: Cloudflare security and logging settings, application hosting logs and retention. The website code’s lack of cookies is not a claim that every hosting or external service is cookie-free.
9. Retention and deletion
Retention depends on the type of record. Library data remains on the device until removed there. Cancelling sync does not delete the device library or immediately delete the cloud copy. The code supports a configurable cloud retention period and a separate purge operation; a source-code default does not establish the live retention schedule.
Page metadata and public Pin images have separate cache and cleanup lifecycles. Shared images can remain while another Pin or live cache references them. Deleting a Pin or account does not necessarily remove shared source-page metadata or images immediately.
Account deletion is available in application settings. The implemented process removes account-related cloud records, enumerated user files and the authentication account. Android retains its working library for local use; on the web, export first if you want your own copy. See account deletion information.
Confirmation needed: actual retention periods or decision criteria for cloud data, support email, logs, security backups, legacy feedback and shared content; cleanup schedules; any specific records retained after deletion and why; and the live deletion process. No fixed deletion deadline is promised here.
10. Your choices and privacy requests
You can manage library records, change discovery and site preferences, export a library backup and request account deletion. A library backup does not necessarily include every separate account record, such as search preferences.
For questions or requests to access, correct, export or delete personal information, contact cadenzaclassicalmusic@gmail.com. Do not send passwords, session tokens or payment details. Sending an email also shares its contents and your email address with the recipient’s email service.
Confirmation needed: the legal basis for each processing purpose, applicable privacy rights and complaint route, identity checks, request handling, intended age group and arrangements for children’s information. This draft does not assign a jurisdiction or invent an age threshold.
11. Changes to this document
This page will be updated as the remaining details are confirmed. A final policy needs an effective date and must match the application and services actually made available.
A question about Cadenza?