1. General provisions
The Operator processes the personal data of clients who make bookings through NaKogda and dashboard users who manage organizations, schedules, and bookings.
Processing is carried out in accordance with the laws of the Russian Federation, this Policy, and the separate consent of the relevant data subject.
2. Data subjects and categories of data
For clients, the Operator processes their name, telephone number, comment, details of the selected organization, service, specialist, booking date and time, as well as confirmation and reminder settings.
For dashboard users, the Operator processes their telephone number or email address, profile data, an uploaded photograph, settings, information about organizations, and actions performed in the dashboard.
When AI-assisted form filling is used, the Operator processes the description entered by the user, attached files and photographs, an audio recording made by the user, its text transcript, technical file metadata, the prepared request, and the AI service response. Microphone recording starts only after the user explicitly presses the microphone button. Voice data is not used to establish identity or for biometric identification.
When a user signs in with Google, Yandex, or VK ID, the Operator receives a stable external account identifier, email, available email verification attributes, first name, last name, and photo URL from the selected provider. The fields actually received depend on the provider response.
When Google Calendar is connected, the Operator processes the Google profile name; calendar identifiers, names, time zones, and available permissions; the user’s selected read and write settings; the OAuth scopes actually granted; and encrypted access tokens. For external events, the Operator processes the start and end, all-day status, busy and self-declined indicators, and technical identifiers needed to exclude NaKogda’s own copies.
For all data subjects, technical session data may be processed, including the IP address, User-Agent, authentication identifiers, essential cookies, the date and time of actions, and information required to keep the service secure.
3. Purposes of processing
Personal data is not used for marketing, profiling, or bulk messaging without a separate legal basis.
- Registration, authentication, and maintenance of a secure session.
- Creation, management, confirmation, modification, and cancellation of a client booking.
- Sending one-time codes, service confirmations, and reminders through the selected channels.
- Providing dashboard functionality, maintaining schedules, and interacting with the selected organization.
- Accounting for busy time from selected external calendars and synchronizing NaKogda events with calendars selected by the user.
- Speech recognition and preparation of form-filling suggestions following an explicit user request.
- Responding to requests, maintaining security, preventing misuse, and complying with legal requirements.
4. Legal grounds and methods of processing
The legal grounds for processing include the data subject’s consent, performance of a contract with the data subject or steps taken at their request before entering into a contract, the Operator’s legal obligations, and other grounds provided by law.
The Operator may collect, record, organize, accumulate, store, update, retrieve, use, disclose in the cases provided for by this Policy, anonymize, restrict, and delete data by automated or non-automated means.
5. Recipients and processing on behalf of the Operator
Client booking details are disclosed to the selected organization and its authorized users to the extent necessary to provide the service and manage the booking.
To operate the service, the Operator may engage hosting, infrastructure, security analytics, and communications providers to process data. A telephone number or Telegram identifier is used by the relevant provider only when that channel has been selected and enabled.
If the user enables writing events to an external calendar, Google receives an event title in the format “NaKogda: organization, client, service”, its time, recurrence rules, and NaKogda technical identifiers. Data is sent only to calendars selected by the user and only to provide the synchronization requested by that user.
For AI features, NaKogda sends OpenAI the request text, files and images selected by the user, and an audio recording to the extent required for speech recognition and preparation of form-filling suggestions. This transfer occurs only after an explicit user action and solely to perform the feature requested by that user.
The text request used to prepare suggestions is sent through the OpenAI Responses API with store=false, so OpenAI does not retain response application state for later retrieval through the API. The audio recording is sent in a separate request to the OpenAI speech recognition service; the store parameter does not apply to that request.
Under OpenAI’s standard API data controls, OpenAI may retain API inputs and outputs in abuse-monitoring logs for up to 30 days unless the project uses an applicable Zero Data Retention mode or a longer period is required by law. API data is not used by OpenAI to train models by default. The provider’s current rules are published at https://developers.openai.com/api/docs/guides/your-data/.
Data may also be disclosed to a public authority in the cases and to the extent expressly required by law. Other recipients do not receive data without a separate legal basis.
6. External sign-in and Google Calendar connection
Google sign-in requests only the openid, email, and profile scopes; Yandex sign-in requests login:email, login:info, and login:avatar; VK ID sign-in requests email. These scopes are used only to identify the user and obtain their email and available profile details.
Calendar scopes are not part of Google sign-in: connecting Google Calendar starts only after a separate explicit action by an authenticated user in NaKogda settings. It requests calendar.calendarlist.readonly, calendar.events, calendar.app.created, and userinfo.profile; no email scope is requested for the calendar connection.
The calendar.calendarlist.readonly scope is used to retrieve the calendar list and available permissions so the user can select busy-time sources and write destinations. The calendar.events scope is used to read events from selected sources and to create, update, and delete NaKogda events in selected calendars. The calendar.app.created scope lets the user create a “NaKogda” calendar with a separate button and manage events created in it. The userinfo.profile scope is used only to obtain the display name of the connected account.
Google Calendar API may return a complete event object. NaKogda immediately extracts only the start and end, all-day status, busy status, the user’s own declined response, and technical identifiers; recurring events are requested as expanded occurrences. The persistent cache receives busy intervals with start and end without event titles, descriptions, participants, or other content; this information is not shown to an organization or to widget visitors.
When writing to an external calendar, NaKogda sends the title “NaKogda: organization, client, service”, the start and end, recurrence rules, and private technical identifiers needed for later updates and deletion. Changes made in the external calendar do not change the source booking in NaKogda.
The provider authorization page receives the public client_id, exact redirect URI, requested scopes, a one-time state, and a PKCE challenge. During ordinary external sign-in, NaKogda does not send the user’s profile, organization, booking, or calendar data back to the provider. When calendar synchronization is enabled, data is sent to Google only for the operations described above.
The persistent external-account link stores the provider code and stable account identifier. The provider email is not stored in that link; when a new user is created, 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 linking uses only 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 remote URL is not stored, and after successful source, format, and file checks only a verified local copy is retained.
Access tokens, ID tokens, and a possible refresh token obtained specifically for external sign-in exist only briefly in Node.js memory during the provider exchange and are not stored in the database, profile, logs, or browser. A one-time provider authorization code is processed during the callback and is not stored in the database, profile, or logs. The raw email code for an external-account link is also not stored in the database; only its keyed HMAC is retained.
To run calendar synchronization in the background, Google access and refresh tokens are stored in the database only in encrypted form. The encryption key is kept separately from the database and repository; tokens are not returned to the browser or written to logs. A disconnected connection or one that requires reconnection is not used for Google requests.
NaKogda’s use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements: https://developers.google.com/terms/api-services-user-data-policy.
7. Sharing and protection of Google user data
NaKogda does not sell Google user data, does not transfer it to advertising networks, data brokers, or other applications, and does not use it for advertising, profiling, creditworthiness assessment, surveillance, or training generalized artificial intelligence models.
Access to or transfer of Google user data is permitted only following an explicit user action to read selected Google Calendars or write events to a selected Google Calendar; to hosting, infrastructure, and security providers strictly to the extent required to operate the service, under confidentiality obligations and a prohibition on using the data for their own purposes; or to government authorities when disclosure is required by law. Google user data is not disclosed to any other recipients.
When a user instructs NaKogda to write an event to a selected Google Calendar, Google receives only the title, time, recurrence rule, and private technical identifiers of that event. This is the user-requested synchronization feature and not an independent transfer to a third party for its own purposes.
Google OAuth tokens are protected at rest with authenticated AES-256-GCM encryption, and the encryption key is stored separately from the database and repository. Data exchanged with Google and the browser is protected by TLS-secured HTTPS connections; the server applies authorization checks and limits access to the current user and the synchronization service process. Tokens are not returned to the browser and are not written to logs.
NaKogda minimizes the data it receives: only the intervals and technical flags required to calculate availability are retained from events, while event content is not kept in the persistent cache. Access ends after the calendar is disconnected in NaKogda or the permission is revoked in the Google Account.
8. Retention and deletion
Data is processed until the stated purposes are achieved, consent is withdrawn, or another legal basis ceases to apply. Certain information and logs may be retained for longer where required by law, to protect the Operator’s rights, or to investigate violations.
Prepared requests and AI service responses, form attachments, and audio recordings are retained in NaKogda’s service log and non-public storage together with technical request details. Automatic cleanup of these materials is not performed; they are deleted following a substantiated data-subject request or when the processing purposes and other lawful retention grounds cease to apply.
An active OAuth request is retained for no longer than 10 minutes. Once it reaches a terminal result, the service immediately removes its personal and operational fields. An expired or abandoned request is cleared during the next five-minute cleanup cycle.
A minimal technical tombstone without a user identifier, provider, email, IP address, User-Agent, or return path is retained for 24 hours and then deleted during the next five-minute cleanup cycle. This cleanup applies to the one-time OAuth request and does not delete a user account or the account email created during a successful sign-in.
Of the identifying data, a confirmed consent record for external sign-in retains only the user identifier, provider, confirmation method, accepted document code and version, and creation and confirmation timestamps. The technical UID, contact hash, IP address, and User-Agent are removed.
External busy-time snapshots are used for no longer than 24 hours and are removed by scheduled cleanup after 48 hours. Synchronization jobs, delivery attempts, and links to deleted external copies are removed after their defined operational retention periods; active event links are retained while they are needed to update or delete an external copy.
The calendar connection, selected settings, and encrypted OAuth tokens are retained until the connection record is deleted or the legal basis for processing ends. Disconnecting in the interface makes the connection inactive: NaKogda stops reading external events and writing new ones, but events previously created in the external calendar are not automatically deleted.
When the relevant grounds cease to apply, data is deleted, destroyed, or anonymized within the period prescribed by law and the Operator’s internal procedures. Unverified codes and the related pending consents are retained only for the duration of the verification process.
9. Security measures
The Operator restricts access to data and applies authorization checks, secure connections, logging of significant actions, backups, and organizational rules for handling information.
These measures are reviewed in light of the nature of the data, current threats, and potential harm. If an incident is discovered, the Operator takes steps to contain it and fulfils applicable notification obligations where required by law.
11. Data subject rights and withdrawal of consent
A data subject may request information about processing, require data to be corrected, restricted, or deleted, and withdraw consent by contacting the Operator at the email address shown below.
Google Calendar access can be disconnected in NaKogda settings and revoked in Google Account settings. After disconnection, NaKogda performs no new read or write operations through that connection. Revoking provider access does not withdraw consent given to the Operator to process data already received; that consent must be withdrawn separately by email at the address shown below.
Withdrawal ends processing based solely on consent but does not end processing for which an independent legal basis remains. To handle a request, the Operator may ask for information needed to verify the applicant’s identity.
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 по Оренбургской области