Personal Data Processing Policy

This version applies to the Russian Vibe Piano web service at https://vibepiano.ru. Changing the interface language does not change the operator or the applicable rules. The English and Chinese texts are translations of this version. The standalone iOS application has separate terms.

1. Operator and scope

Индивидуальный предприниматель Соболев Дмитрий Павлович, ОГРНИП 326508100266477, ИНН 501502113878 determines the purposes and methods of processing data concerning users, website visitors, people who contact us and participants in partner programmes. Contact: privacy@vibepiano.ru. This policy describes data processing; it does not in itself constitute consent to advertising, publication of a recording or automatic charges.

2. Data, purposes and grounds for processing

• Account: name or display name, email if provided, avatar URL, the identifier and name of the chosen sign-in provider, an internal account identifier and session information. These are needed for sign-in, access management and saving preferences. The external account password and its OAuth tokens are not stored in the Vibe Piano database. The grounds are performance of the agreement and separately requested consent where applicable.
• Learning: selected pieces, exercise results, questions, answers and response times, mistakes, streaks, achievements and practice history. These are used to track progress, provide feedback and adapt exercise selection. The principal ground is provision of the requested service features.
• Spark session history: piece title and selected hands, practice mode, relative elapsed time, changes in Spark level and energy, and cumulative counts of hits, mistakes, delayed steps and completed steps. This private history lets you review how a real practice session developed. Automatic playback is excluded. It is visible only to you, is included in your account export and is deleted with the account; opening your profile or showing piece progress does not publish these session curves.
• Piece progress: for a signed-in user, for each catalogue piece and selected hands, the score steps played correctly at least once in a lesson, a signature of the score version, counters derived from them and the time of the last update are stored. Steps count when playing with a MIDI keyboard, the on-screen keyboard or the microphone; sound is not sent to the server and automatic playback is excluded. Progress syncs with the account so that it is visible on other devices, is included in the account export and is deleted with the account. Progress on your own imported pieces is not sent to the server. The basis is providing the function you requested.
• Practice history on the device: attempts at pieces with their conditions (hands, passage, mode, input source, set tempo), counts of correct, wrong, missed and extra key presses and of stops, including per bar, accuracy, the estimated played tempo, counts of rhythm warnings and of wrong key presses at ornamented notes, the confidence of the measurement and playing time; daily totals; personal tasks and control attempts; short “what next time?” notes on pieces. These data stay in the browser's local storage, separately for each account and for the guest, and are not sent to the Vibe Piano server. Signing out hides the history until the next sign-in and does not delete it. Apart from the volume limits in section 6, only explicit actions delete it: deleting a piece's history, the profile's whole practice history or all practice data from the device, the deletion option ticked when signing out, deleting the account on the device where this is done, and clearing site data in the browser. The history can be downloaded as a JSON file, which is created on the device. The operator cannot read, restore or delete these data remotely.
• Personal piece list: the pieces you marked “want to learn” and your free-form notes on them (up to 500 characters). They are needed to open saved pieces from your profile. Only you can see the notes; do not put health information or other people's data into them. The basis is providing the function you requested.
• Open profile, if you opened it: the nickname you chose, the profile code, your level and accumulated points, the date it was opened and, if separately enabled, the titles of pieces from your personal list and piece progress: catalogue piece titles with their composer, selected hands and the share of score steps played correctly at least once (the number of such steps, the total number of steps and the percentage). If the practice summary is separately enabled, only three numbers are published: the number of calendar weeks with playing at the instrument, the number of catalogue pieces played through without a mistake at least once on a MIDI or Bluetooth keyboard, and the total hours of playing at the instrument rounded down to a whole hour. The purpose is to show your progress to other users at your own wish. The basis is a separate consent to distribution of open profile data.
• Teacher access, if you granted it: the teacher whose profile code you entered sees your name from the sign-in service and your profile code and, for each catalogue piece you chose, minutes of playing at the instrument per week, the number of days with playing, the number of attempts and passes, mistakes and stops per bar, the learning stages of passages and how their own assignments were done. The teacher may add an assignment to a piece: bars, hands, tempo, minutes per day, the lesson date and a text of up to 280 characters. The time of day, the start time and length of individual sessions, notes, recordings, sound and other pieces are not shown to the teacher. Access is granted by a separate action on the “My profile” page after a separate consent to provide practice data to a teacher, and for a student under 18 only by their legal representative. It can be closed at any time: the teacher stops seeing the data at once and their assignments are deleted. The purpose is learning work with the teacher you chose. The basis is that consent.
• Subscription and access codes, if these features are enabled: plan, payment amounts, currencies, statuses and identifiers, access period, saved payment method token, promo code and information about credited amounts. These are needed for access, payments and settlements, refunds and compliance with legal obligations. The service does not receive the full card number or CVV; these are processed by the payment organisation.
• Consent and abuse prevention: document type and version, the action and time of consent or withdrawal, source, account or consent-correlation identifier, IP address and browser information in the consent log. Certain evidence records use cryptographic derivatives instead of the original request details. These are needed to demonstrate the person's expressed choice, maintain security and protect legitimate interests.
• Feedback: text of up to 2,000 characters, enquiry type, page path without parameters, application version and technical information shown before submission: window size, browser and operating system, language, MIDI devices and the current piece or lesson. An account identifier or a permitted analytics identifier is added where available. The feedback record does not include the IP address, full User-Agent, cookies or the contents of other screens. The purpose is to respond and resolve problems. An email enquiry also includes the sender's address and the information they provide.
• Technical security: the connection IP address, time, HTTP request method and path, response code and processing duration may appear in server logs. These are needed for diagnostics, attack prevention and website operation; they are not advertising analytics.

Do not provide health information, biometric data or third-party data unless needed for your enquiry. The service does not use voice or performance to establish identity.

3. Cookies, local storage and analytics

Necessary cookies support sessions, remembering choices and evidence of consent. A random consent-correlation identifier in an HttpOnly cookie is not used for advertising and is valid for no more than 180 days. You can change your analytics choice in “Cookie settings”. Declining does not block the core features.

Language, theme, sound, metronome and some learning results are stored locally in your browser. These preferences have no automatic deletion period; you can delete them using your browser's controls. Deleting a web account does not clear the rest of local storage on your devices; it deletes that account's practice history only on the device where the deletion is performed.

Without analytics permission, the service maintains aggregate counters using a predefined, limited set of metrics. To estimate daily visitor numbers, network data is processed in memory using a key that changes daily; the individual result is not stored as a visit record. This does not mean that technical server logs do not exist.

After separate permission, processing may include an analytics identifier, referral source and UTM tags, permitted interaction events and, for signed-in users, a link to their account. Yandex Metrica is connected only after this choice. Withdrawal disables further optional analytics; deletion of previously collected data is considered separately upon request. The practice history features additionally send from the website facts of actions from a closed list: practice history opened, list of difficulties shown, task created, retry started, task practised for the day, control attempt played with an outcome from a fixed set of words. Piece titles, bars, notes, mistakes, tempo, playing time and note texts are not included in these facts. Events of the lesson itself are sent separately: lesson start and active playing with the catalogue piece identifier, and piece completion with the piece identifier and, after analytics permission, also with counts of correct and wrong key presses, accuracy and duration. Without analytics permission all these events are counted only in aggregate counters. Aggregate counters are not used for personalised advertising.

4. Microphone, MIDI, performance recordings and the open profile

The microphone is enabled at your request for local note recognition. Its stream is not uploaded to the server as an audio recording. MIDI transmits note events; device information may be included in an error report shown to you.

The recording feature captures the application's synthesised audio. Until publication, the recording stays on your device. Uploading and creating a public link occur only after a separate command. Publication requires separate consent to distribution.

The performance page contains audio, the piece title, composer and publication date. It does not display the account name, avatar or email. Anyone with the link can listen to, download and forward the recording; blocking search engine indexing does not make the link private.

A profile is closed by default: nobody but you can see its page. It can be opened only by a separate action on the “My profile” page after a separate consent; silence and inaction do not count as consent. The open profile page is available to anyone who knows its address (by profile code or by nickname) and contains only the nickname, the profile code, the level, the points and the opening date, and, if separately enabled, the titles of pieces from the personal list and practice totals from the trainer and, when separately enabled, piece progress: catalogue piece titles with their composer, selected hands and the share of score steps played correctly at least once (the number of such steps, the total number of steps and the percentage). Piece progress is shown only after the consent version describing it in these terms has been accepted; practice time and mistakes, sound, microphone data and practice history are not published. The practice summary is shown only after the consent version describing its three numbers has been accepted; dates, the time of day and piece titles are not part of it. Individual answers and their note-by-note breakdown are never published. The name, avatar and email from the sign-in service, notes on pieces, trainer answers and payment details are not displayed on it. Closing the profile immediately ends access to the page and counts as withdrawal of consent; blocking search engine indexing does not make the address private, and the operator cannot remove copies already made by third parties.

5. Recipients and processing locations

The operator and persons authorised by the operator receive access to the extent needed for their tasks. A teacher you granted access receives only the details listed in the consent to provide practice data to a teacher, and only while the access is open. Sign-in involves your chosen service: VK ID, Одноклассники, Mail.ru or Yandex ID. Loading an external avatar sends a request to the provider's infrastructure. Yandex Metrica is involved when analytics is permitted, and YooKassa when payments are enabled. These organisations have their own processing rules. Disclosure to public authorities is possible where there is a lawful ground.

When collecting Russian citizens' personal data over the Internet, the operator must comply with requirements for recording and storage in databases located in the Russian Federation. Cross-border transfers require a separate lawful ground and compliance with the statutory procedure. This policy does not declare all external services to be Russian and does not replace verification of the locations of hosting, backups, email and engaged processors. The actual list and processing locations must be confirmed by the operator before this version is approved.

6. Retention and deletion

• The main profile, linked progress, enquiries and recordings are retained to operate the account; when it is deleted, associated user data is deleted subject to statutory exceptions. Access granted to a teacher and the teacher's assignments are kept while the access is open and are deleted when it is closed or when the student's or the teacher's account is deleted.
• Practice history on the device has no time-based retention period and is kept until you delete it, within volume limits. At most the latest 200 attempts per piece and 450 in total are kept in detail, fewer if the allotted space runs low; older attempts are folded into daily totals, which keep time and counters but not per-bar details. At most 5000 daily totals, 200 personal tasks with the latest 20 control attempts each and 500 notes on pieces are kept; beyond these limits the oldest records are deleted automatically.
• Unlinked trainer history is deleted after 180 days; unlinked enquiries and old recordings without an owner after 365 days; aggregate counters and statistical structures after 400 days. Periodic deletion requires a functioning server job.
• Unlinked request details in the consent log are cleared after 180 days. The event, choice, time and document version may be retained as evidence of lawful processing.
• Payment documents, evidence of the accepted offer, obligations concerning partner settlements and cryptographic identifiers used to prevent repeated use of benefits may remain after account deletion if an independent lawful ground still exists. Pseudonymisation and unlinking from the account are not equivalent to complete destruction.
• Detailed analytics events, retained anti-fraud registers, server logs and backups require separately approved retention periods and deletion procedures. A single rule that “everything is deleted with the account” does not apply to them; these periods must be agreed before this version is approved.

Deletion from the live system does not mean that previously created backups disappear immediately. Backups must have limited retention, protected access and a procedure for repeating deletions after restoration. Policy wording cannot replace these organisational measures.

7. Rights and enquiries

You may request information about processing, correction, blocking or destruction of data where statutory grounds apply, withdraw consent and challenge the operator's actions before Roskomnadzor or a court. Account settings provide server-data export, account deletion, management of published recordings and withdrawal of advertising consent. Export does not include files that remain only on your device. Practice history on the device can be downloaded separately as a JSON file in the practice history window.

Send your enquiry to privacy@vibepiano.ru, identify your account and describe your request. To protect against unauthorised requests, proportionate verification of identity or a representative's authority may be required; do not send a passport in advance. For enquiries without an account, provide enough information to locate your record.

Information requested is provided within 10 working days; the law permits a reasoned extension of no more than 5 working days. Requests to cease processing, correct or destroy data are fulfilled within the periods specified for the relevant ground in Articles 20 and 21 of Federal Law No. 152-FZ. Withdrawal of consent does not stop processing necessary under a contract or expressly required by law; the ground for retaining data is explained to the applicant.

8. Minors and security

An adult user, including a student's legal representative, sets up the account, gives consent and arranges payment. A separate verified system of child accounts is not provided. Acting as a representative does not grant the right to publish any other person's personal data without checking the necessary grounds. Only a student's legal representative may open the student's profile and choose a nickname for them; the child's real first name and surname are not used in the nickname. Teacher access to the practice of a student under 18 is granted only by their legal representative, and this is stated when the access is granted.

Access restrictions, a secure connection, sign-in verification, data minimisation and logging of significant actions are used. Absolute security is not guaranteed; in the event of an incident, the operator fulfils response and notification duties within the statutory periods.

9. Changes to this policy

The version and date appear above the text. The archive provides access to previous texts. A new publication does not turn an old consent into consent to new purposes; a new expression of consent is requested where needed.

Operator details and contact

Индивидуальный предприниматель Соболев Дмитрий Павлович, ОГРНИП 326508100266477, ИНН 501502113878.

Address for written correspondence: 143180, Московская обл., г. Звенигород, Шиховский проезд, д. 1. Sole proprietor registration date: 29.04.2026.

For enquiries about data, access, payments and rights to materials: privacy@vibepiano.ru. Do not send your full card number, CVV, passwords or sign-in codes.