Privacy and Security

The platform is built for quick collaboration. It is still important to follow basic privacy rules and handle invite links carefully.

What it is

Access to a session is shared via a link or a 6-character code; the host can close it off with private mode and a password.
Only the host manages session settings and can end the session.
Persistent sessions are available for Premium and PRO users (see Rooms and persistent sessions); an ordinary session is not kept.
Your display name is stored in the browser and can be changed.

Signing up is optional, so an anonymous user is recognised by a device key rather than by a login.

On first visit the browser generates a key pair of its own and signs requests with it.
The private key lives in the browser's IndexedDB, never leaves the device, and is not readable by us or by page scripts.
We do not fingerprint the browser to identify people: what is recognised is a device, not a person.
The consequence: clearing site data wipes the key, and to the platform you become a new device. Anonymous preferences and device-bound persistent sessions are lost with it. Signing in with Google or Yandex removes that dependency.

The state of an active session: cards, notes, tokens, the die and items on the table. It is deleted when the session ends, unless the session was persistent.
Session chat history, the last 100 messages.
For an account: email and avatar from Google or Yandex, badges, Premium status, pearl balance, notifications, your decks and rooms.
Private notes never reach the server at all: they are visible only to you and are not synced.

We do not record Air audio or video. There is no recording service in the deployment; that is an architectural decision, not a setting. All that remains of a call is participation metadata used for the weekly limits.
We do not read your notes for advertising and do not sell data.
We do not hand out cards without a watermark through the API.

Account data can be exported or deleted on request; deleting an account removes the related records, Air metadata included.
The request procedure and contacts are in the privacy policy and the terms of use, both linked in the app footer.

Do not post session links in public channels; for sensitive topics turn on private mode and a password.
For sensitive topics, use private or anonymous notes.
End the session after finishing to disconnect participants.
Do not put client's personal data into notes: every participant sees a public note.

Copy the link or code and share it only with trusted participants.
For client work turn on private mode, and add a password if you have PRO or Premium.
Use anonymous notes when the author should be hidden.
After finishing, click "End session".
Save a table screenshot if you need a record.

Sensitive topic: private mode, a password, private notes, and the code shared with the client only.
Group practice: agree in advance who is the host and controls settings.
Shared computer: sign out when you are done - the app returns to anonymous mode.

If a link is shared with the wrong people, create a new session and use a new code.
In public places, avoid showing personal data on screen.
Clearing site data wipes the device key: anonymous preferences and bindings do not come back.

Screenshot 12.1

Screenshot 12.1 - Privacy policy link

Elements on the screenshot: 1. Privacy policy link 2. Terms of service link 3. Documentation version info