Personal Data Protection

The SafeSelf platform is built for handling personal information with care. We encrypt clients' personal data and confidential notes so that they cannot be read in plain text even with direct access to the database.

Decryption happens only on the application server, at the moment the data is actually needed: for signing in, booking a session, notifications, or a specialist working in their account.

Client profile: name, e-mail, phone, contact links, avatar, Telegram name and other personal account fields.

Booking data: the client's name and contacts, booking comments, and the psychologist's notes for a particular session.

Administrative notes about a client, available only to platform staff with the corresponding rights.

The psychologist's notes about a client (general case notes): the note text is encrypted with a separate specialist key; the client's e-mail in these records is also stored encrypted.

Symmetric AES-256-GCM encryption is used for the platform's personal data. Only ciphertext with a format version prefix is stored in the database — without the key, decryption is impossible.

A one-way index (HMAC) is used to search by e-mail when signing in and linking records: it allows finding a user, but the original address cannot be recovered from the index.

Psychologists' notes are additionally protected by an individual specialist data key wrapped with the platform master key — even if one record is compromised, the others remain isolated.

Data transfer between the browser and the server is protected by HTTPS (TLS).

Encryption keys are stored in protected server environment variables (PII_MASTER_SECRET / NOTES_MASTER_SECRET) and never end up in the repository code or the client application.

Only authorised users can access decrypted data, within their role: a client sees their own data, a psychologist sees their clients and their own notes, an administrator sees the service information needed to run the platform.

We do not pass decrypted personal data to third parties, except in the cases described in the Privacy Policy (for example, payment providers — only to the extent needed for payment).

Database backups contain the same encrypted values. Without the server key they give no access to the contents of notes or to personal fields.

We recommend that installation owners rotate secrets regularly, restrict access to the server and the database, and never store master keys in plain text.

You can request information about the data we store, its correction or deletion — write to us at safeself-platform@yandex.by. For more about the rights of a data subject, see the Privacy Policy.

When an account is deleted, personal data is deleted or anonymised in accordance with applicable legislation and the platform's internal procedures.

Encryption protects data if a database dump leaks or tables are read without authorisation, but it does not replace strong passwords, two-factor protection where it is available, and care when working with confidential information on your own device.

We keep improving our security measures and update this page whenever there are material changes.