1. Data covered by this consent
Telephone number or email address, user profile data and settings, an uploaded photograph, and information about organizations, roles, access rights, and actions performed in the dashboard.
For external sign-in with Google, Yandex, or VK ID, this consent also covers the stable account identifier, email, available email verification attributes, first name, last name, and photo URL received from the selected provider.
The Operator also processes the IP address, User-Agent, verification and session identifiers, essential cookies, the date and time of actions, and information required to protect the account.
2. Purposes of processing
Data is used for registration, authentication, and provision of dashboard functionality; management of the profile, organizations, schedules, and access rights; sending one-time codes and service notifications; support; and security.
This consent does not cover data from other clients’ bookings unless the user is granted access to that data under their authority in the selected organization.
3. Actions involving data
The Operator may collect, record, organize, store, update, retrieve, use, disclose to the recipients specified in this document, anonymize, restrict, and delete data by automated and non-automated means.
4. Data recipients
Profile data and role information may be available to other authorized users of the organizations to which the data subject belongs. Technical processing may be entrusted to infrastructure, security, and communications providers to the extent necessary.
This consent does not authorize disclosure of data for marketing purposes.
5. External sign-in details
The persistent link stores the provider code and stable external account identifier; the provider email is not stored in that link. For a new user, the received email becomes the email in their NaKogda account profile.
Before matching, an email is normalized by trimming surrounding whitespace and converting it to lowercase. A user email is globally unique in NaKogda, so an external account is linked to an existing profile only on an exact match between normalized addresses.
If the provider returns a first name, last name, or photo, they may be copied only into a new user’s profile; an existing profile is not overwritten. Photo import is best-effort and an import failure does not block sign-in. The provider photo URL is not stored: after a successful check and import, only a verified local copy remains.
Google sign-in uses only the openid, email, and profile scopes; Yandex sign-in uses login:email, login:info, and login:avatar; VK ID sign-in uses email. Calendar access is not covered by this consent and may be granted later only through a separate explicit action to obtain busy intervals with start and end and no event content.
For ordinary email sign-in, consent is confirmed with a separate checkbox and one-time code. For external sign-in, it is confirmed with a separate checkbox and a successful provider callback.
An active link identified by the “provider + stable identifier” pair takes priority: a provider email change does not move the link to another user. Without such a link, a matching email is associated only with an active user and only when there is no conflicting link for that provider; if there is a conflict, sign-in is rejected.
For a linked account and a new user, no additional code is required. For a permitted match to an active user’s email, the code is also unnecessary only if Google returns email_verified=true and the address is Gmail or Google Workspace with a non-empty hd that exactly matches the normalized email domain. A permitted match through Yandex or VK ID always requires a NaKogda one-time email code; Google requires the same code in every other case.
6. Security and essential cookies
The Operator applies access controls, action logging, secure connections, and other legal, organizational, and technical safeguards. Essential cookies are used for authentication, session protection, language selection, and operation of the interface.
Detailed rules governing data processing and deletion are set out in the Personal Data Processing Policy.
7. Duration and withdrawal
This consent remains valid until the purposes of processing are achieved or it is withdrawn, unless a different period is required by law. Consent may be withdrawn by contacting the Operator at the email address shown below.
Revoking access in an external provider’s settings is not withdrawing consent from the Operator. NaKogda’s authorization to receive data from Google, Yandex, or VK ID and consent to the Operator are ended through separate actions.
Withdrawal does not end processing for which an independent legal basis remains.
8. Confirmation of consent
For ordinary sign-in, consent is confirmed by selecting a separate checkbox and successfully verifying a one-time code. For external sign-in, the confirmation method is a provider callback or a callback combined with a separate NaKogda email code in the cases described above.
Of the identifying data, a confirmed consent record for external sign-in retains only the user identifier, provider, confirmation method, document code and version, and creation and confirmation timestamps. The technical UID, contact hash, IP address, and User-Agent are removed.
Personal data operator
- Name
- Email for requests and withdrawal of consent
- support@nakogda.ru
- Phone
- Taxpayer ID (INN)
- 563500962846
- Sole proprietor registration number (OGRNIP)
- 326565800088148
- Registration address
- Registration date
- 25.08.2026
- Registration authority
- Межрайонная инспекция Федеральной налоговой службы № 10 по Оренбургской области