C you,Ya.Music.*Reads as "See you, Ya.Music" — a goodbye to Yandex Music, until better times.
ENRU
← Back to home

Privacy Policy

Effective: 12 August 2026

yamusic.cyou processes a public Yandex Music playlist when you ask the service to create an export. We do not create visitor accounts or build profiles of individual listeners. Denis Semenov, at the address shown in the Imprint, is the data controller.

Cookies and tracking

We use no advertising cookies, client-side analytics, fingerprinting or cross-site tracking. The public exporter does not set an application cookie, so no consent banner is needed. A staff-only administration area uses an essential sign-in cookie. Infrastructure providers may set a strictly necessary security cookie when responding to abuse.

Data we intentionally avoid

  • No visitor name, email, password or public user account.
  • No raw IP address in our application database.
  • No long-term link between request telemetry and music metadata.
  • No listener profile or analysis of an individual's preferences.
  • No stored audio, lyrics or binary copies of album artwork.
  • No sale of visitor or playlist data.

Public playlist processing

For the export you request, we process the playlist title, revision and ordered track list; public owner identifiers, login, name and playlist kind supplied by Yandex Music; and provider track, artist and album identifiers, names, genres, availability and durations. We do not store owner avatars or image bytes.

Normalised playlist snapshots, public playlist and owner metadata, and their history are retained as private service history. The latest full source URL that successfully fetched the playlist is retained with the playlist for recovery and export compatibility. These records are not exposed through a public catalogue or owner search.

Technical telemetry and statistics

For up to 90 days, legacy request telemetry may retain a salted IP hash, a normalised playlist link, country code, browser user-agent and language, response status, processing time and bounded error details. A salted hash is pseudonymous data, not a claim that the visitor is anonymous. It is used for abuse prevention, reliability and short-term operational analysis. A self-hosted export event contains no visitor IP address or IP hash.

Separately, we may retain the complete text you submit, up to 1,000 characters including its query and fragment, in private operational data for up to one year. After one year only the submitted input is cleared; the export event and its old, new or invalid link-format classification remain. The submitted input is not written to application logs and is shown to staff only as non-clickable text.

A two-letter country code confirmed by the hosting platform is retained indefinitely on each export event. It describes the network exit point, not a person's residence, and we do not try to determine VPN use. The same playlist snapshot may therefore have export events with different country codes.

Long-term statistics contain daily or monthly totals such as exports, errors, tracks and countries. They do not contain an IP hash or a link to an individual playlist request. Small public country groups may be combined rather than displayed separately.

Legal basis: performing the export you requested (Art. 6(1)(b) GDPR), and our legitimate interests in service security, reliability, deduplication and aggregate product statistics (Art. 6(1)(f) GDPR).

Post-export feedback and donations

After a successful export you may voluntarily tell us whether the transfer worked, which services you are moving to, how you found this service, why you are leaving Yandex Music, and any additional wishes. We store the selected answers, free-text details and interface locale with the specific export event. The feedback record contains no IP address or IP hash, and one export event accepts at most one response.

Donation links are independent of the feedback form. They open T-Bank or Stripe in a new page; yamusic.cyou does not create a database record when you use either link. The payment provider processes the payment under its own privacy terms.

Service providers and transfers

The service uses Cloudflare for network security, Vercel for application hosting and a dedicated self-hosted PostgreSQL/PostgREST service for the active database. A restricted legacy Supabase project temporarily keeps pre-cutover data and recovery backups during the migration rollback window; the active application does not read or write it. Infrastructure providers and their subprocessors may process limited technical data outside the EEA under their applicable contractual safeguards.

To perform the requested export, our server asks Yandex Music for the public playlist identified by the submitted link. Yandex receives the server-side request and its own playlist identifier, not the raw visitor IP from our application. Yandex is an independent service with its own terms and privacy policy.

Legacy recovery and backups

Historical export files are kept in a restricted recovery archive while the old service history is reconciled. Only the music fields needed for recovery are imported into the active model. Encrypted operational backups expire on a documented rotation; data deleted from production disappears from those backups as they rotate.

Your rights

Under the GDPR you may request access, correction, restriction or deletion of personal data, object to legitimate-interest processing, and complain to a supervisory authority. Because we do not create visitor accounts, include the relevant public playlist link and approximate date when contacting us; we may be unable to identify a record from an IP address alone. Privacy and takedown contact: [email protected].