Privacy Policy
Last updated
This notice is provided under Articles 13 and 14 of the EU General Data Protection Regulation (GDPR). It describes how Classikal processes personal data when you browse, search, create an account or use logged-in features.
Controller
The controller is Alin. For questions or GDPR requests, use the public feedback board.
What we process
- Account data: email address and optional display name. If you use email and password, your password is stored as a bcrypt hash; we never store the plaintext password.
- If you choose Google sign-in, we receive your Google account identifier, verified email address, and available display name and profile image. We store the linked identity and authentication tokens needed for that sign-in. We request only identity, email and profile permissions. A Google-only account does not require a password.
- Account content: favorites, playlists and their public/private setting, manually recorded listening states, and private listening notes. Notes and listening states are not included in public playlists or catalog pages.
- If you request password recovery or optional email verification, we process your email address and a single-use action link. We store a hash of its token, expiry and issuing account version. Registration does not automatically send a verification email.
- Technical data needed to operate the site: IP address used for short-lived rate limiting, session cookie, and standard server logs.
- Search diagnostics: eligible search text of up to 200 characters, autocomplete or full-search mode, requested entity type, interpretation, result counts, preferred result type and timestamp. These records do not include an account identifier, email field, IP address or session identifier. We filter recognizable email addresses, URLs, phone numbers, credentials and contact messages before saving search text. This filter cannot recognize every kind of personal information; please keep personal details out of searches.
The public encyclopedia (composers, works, recordings, performers, releases) is catalog data, not your personal data.
Mobile app
The Classikal mobile app has no sign-in or account. Favorites, playlists, listening states, notes and preferences stay on your device, are not sent to us, and are removed when you delete the app. The app contains no advertising, analytics SDK or third-party tracking.
To show the catalogue, the app requests public data from classikal.org. Our server receives your IP address for short-lived rate limiting and standard server logs. Text you type in search is processed to return results and may be kept as the search diagnostics described above, for the same period and without an account identifier, IP address or session identifier. Opening a source or listening link sends a request to that website under its own privacy policy.
Purposes and legal bases
- Creating and operating your account, library, recovery and requested verification — contract (GDPR Art. 6(1)(b)).
- Securing the service (rate limits, abuse prevention, session integrity) — legitimate interests (Art. 6(1)(f)).
- Diagnosing search quality and reviewing possible catalog omissions using search diagnostics — legitimate interests (Art. 6(1)(f)). A search with no results is a review signal, not proof that a work is missing.
- Loading third-party players (Spotify embeds) only after you click to load them — your request to receive that content (Art. 6(1)(b)) / consent to communicate with Spotify (Art. 6(1)(a)). Until you click, we do not load Spotify cookies or trackers.
Classikal uses privacy-friendly, self-hosted analytics (Umami) for all visitors so we can understand how the catalogue is used. Umami does not set advertising cookies and we do not use Google Analytics, Google Tag Manager, or advertising pixels. Legal basis: legitimate interests (Art. 6(1)(f)).
Umami usage events describe searches that lead to a selected result, recording views, listening-link clicks and library saves. They exclude search text, email addresses, account identifiers, private notes, action tokens, query strings and URL fragments. Account and playlist paths and page titles are generalized before being sent. A listening-link click does not establish that music was played or completed.
Personal suggestions use recent saved catalog references and editorial listening guides, with the reason shown on each suggestion. Private note text is not used to rank them. Without an account, library data stays in your browser until you remove it or clear browser storage; signing in does not automatically import it.
Recipients
Hosting and database providers that store this site process account data on our instructions. Tuelia (our consent platform) processes consent choices; Umami (self-hosted at analytics.classikal.org) processes technical usage data for site analytics. The public feedback board at feedback.classikal.org is a separate self-hosted Fider instance: if you post there, Fider stores the name and email you use to sign in, plus your posts and votes. If you load a Spotify embed, Spotify (Spotify AB) receives the request from your browser according to Spotify's own privacy policy. We do not sell personal data.
Requested account emails are sent through Postmark, which receives the recipient address, message content and action link to deliver the message. Open and link tracking are disabled for these messages. See Postmark's privacy policy. Opening a link to Apple Music, Qobuz, IDAGIO or Presto sends a request to that service under its own privacy policy; Classikal does not give it your private library or notes.
If you choose Google sign-in, Google handles authentication and provides the identity data listed above. Google processes data under its own privacy policy.
Retention
Account data is kept until you delete the account. Session cookies expire after 7 days of inactivity at most. Password-reset links expire after 30 minutes and verification links after 24 hours; used or replaced tokens are removed or superseded. Account deletion removes account tokens and private listening entries. Recovery rate limits use keyed hashes in the database, with windows of 15 minutes or one hour; cleanup removes expired buckets more than a day old as requests run. Other short-lived limits use memory. Server logs are rotated by the host.
Search diagnostics are stored separately in the site database. Their target retention period is 30 days. As eligible searches are logged, each application process attempts to remove up to 500 older records at most once per hour. This is request-driven cleanup, not a scheduled deletion job: older records may remain during inactivity, cleanup failures or a backlog.
Your rights
You may request access, rectification, erasure, restriction, and portability of your personal data, and you may object to processing based on legitimate interests. You can delete your account yourself at Account when signed in. To exercise other rights, use the public feedback board. You may lodge a complaint with the Garante per la protezione dei dati personali (Italy) or with the supervisory authority of your EU/EEA country of residence.
Cookies
We set an HTTP-only session cookie after you sign in, strictly necessary to keep you authenticated. We also set a cookie named clk_f, which contains no identifier and only tells our server that your browser runs JavaScript, so recording filters work while automated crawlers are kept off them. A consent banner (Tuelia) lets you accept or reject optional cookie categories. Umami analytics loads for all visitors and does not depend on that choice. Optional third-party cookies from Spotify are set only if you choose to load an embed. You can reopen cookie settings from the site footer at any time.
Children
The service is not directed at children under 16. Do not create an account if you are under 16.
Changes
Material changes to this notice will be reflected on this page with an updated date. Continued use of an account after an update constitutes notice of the new text; we do not use this as a substitute for consent where consent is required.