Privacy Policy
Plancy - web application for project, task and work time management
ООО «Архитектурный Портал» (Architectural Portal LLC) | Version of November 19, 2026 | Effective upon publication at plancy.ru/en/legal/plancy-privacy
1. Overview
1.1. This Privacy Policy (the "Policy") describes what data Architectural Portal LLC (OGRN 1237700594779, INN 9709098730; "we", the "Operator") processes when operating the Plancy web application at https://app.plancy.ru (the "Service"), including data obtained from Google Calendar, how this data is used, shared, retained and deleted.
1.2. We process personal data in accordance with Russian Federal Law No. 152-FZ "On Personal Data". We handle data obtained through Google APIs in accordance with the Google API Services User Data Policy, including the Limited Use requirements (Section 6).
1.3. The Service is intended for organizations and their employees and is not directed to persons under 18.
1.4. The Plancy Meetings recording service (https://ai.plancy.ru) is governed by a separate Plancy Meetings Privacy Policy.
2. Data we process
2.1. We process:
a) account data: name, email address, profile photo (if uploaded), job title, department, roles in the workspace;
b) work data that users enter into the Service: projects, tasks, comments, files, time entries, absences;
c) technical data: IP address, browser information, event logs, cookies;
d) Google Calendar data - only if the user connects the Google Calendar integration (Section 3).
2.2. We do not collect data that is not necessary for the Service to work.
3. Google Calendar integration
3.1. The integration is optional. Users connect it themselves in their Service profile ("Integrations" - "Google Calendar") and see the requested permissions on the Google consent screen. The integration can be disconnected there at any time.
3.2. The Service requests the following Google permissions (scopes):
| Google scope | Data it gives access to | How we use it |
|---|---|---|
| openid, userinfo.email | Google account identifier and email address | To show the user which Google account is connected |
| calendar.calendarlist.readonly | The user's calendar list: name, identifier, primary calendar flag (read-only) | The user chooses which calendars' events to show in time tracking |
| calendar.events | Events in the user's calendars; creating, changing and deleting events | 1) to show meetings from the selected calendars on the "Time tracking" page so the user can log the time spent on a meeting in one action; 2) if the user enables this setting - to add deadlines of the user's tasks and the user's absences from the Service to the user's primary calendar and keep them up to date |
3.3. From Google Calendar events the Service stores only: title, start and end time, event and calendar identifiers, and the link to the event in Google Calendar. Event descriptions, attendee lists and attachments are not stored.
3.4. The Service changes and deletes in Google Calendar only the events it created itself (task deadlines and absences). It never changes or deletes the user's other events.
3.5. Meetings imported from Google Calendar are visible only to the user who connected the calendar. If the user logs time for a meeting, the resulting time entry (with the meeting title) becomes part of the workspace's work data and is visible like any other time entry - according to the access rights configured in the workspace.
4. Purposes of processing
4.1. We process data solely to:
a) provide the features of the Service, including the integration features described in Section 3;
b) authenticate users and keep the Service secure;
c) respond to user support requests;
d) comply with the laws of the Russian Federation.
5. How we use Google user data
5.1. Data obtained through Google APIs is used only to provide the features described in Section 3 that are visible to the user in the Service's interface.
5.2. We do not sell Google user data, do not transfer it to advertising platforms, data brokers or information resellers, and do not use it to serve advertisements, including personalized advertisements.
5.3. Google user data is not used to determine creditworthiness or for lending purposes.
5.4. Google user data is not used to develop, train or improve machine learning or artificial intelligence models.
5.5. Our staff do not read Google user data unless: the user has given affirmative agreement to view specific data (for example, in a support request); it is necessary for security purposes (for example, investigating abuse); it is required to comply with applicable law; or the data is aggregated and anonymized and used for internal operations of the Service.
6. Limited Use disclosure
6.1. Plancy's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
7. Sharing with third parties
7.1. Google user data is not shared with third parties except:
a) our hosting provider Timeweb Cloud (Russian Federation), whose servers host the Service;
b) where required by the laws of the Russian Federation;
c) in the event of a reorganization, merger or sale of our business - with prior notice to users.
7.2. To operate the Service we also engage processors (data hosting, email notifications) and share with them only the minimum data necessary under data processing agreements.
8. Retention and deletion
8.1. Google access tokens are stored encrypted (AES-256-GCM), used only to synchronize the calendar, and deleted when the integration is disconnected.
8.2. The list of Google calendars is deleted when the integration is disconnected.
8.3. Google Calendar events for which the user has not logged time stop being shown immediately after the integration is disconnected and are deleted the next time Google Calendar is connected, or upon the user's request (Section 8.7).
8.4. For events for which the user logged time or which the user hid, we keep the title, time and identifiers so that the meeting does not reappear when the calendar is reconnected. This information is deleted together with the time entry, with the user's account, or upon the user's request.
8.5. When the integration is disconnected, the Service deletes from the user's Google Calendar the events it created (task deadlines and absences), unless calendar access has already been revoked.
8.6. Account data and work data are retained while the user's organization uses the Service and are deleted at its request, except for data that must be retained by law.
8.7. Users can revoke Plancy's access to their Google account at https://myaccount.google.com/permissions or by disconnecting the integration in their Service profile. Data deletion requests can be sent to info@plancy.ru; we delete the data within 30 (thirty) days unless we are legally required to keep it.
9. Security
9.1. We apply legal, organizational and technical safeguards: encryption of secrets (AES-256-GCM), data transfer over HTTPS only, access control, and data hosting on servers in the Russian Federation.
10. Your rights
10.1. You have the right to obtain information about the processing of your personal data, to request its correction, blocking or deletion, to withdraw consent to processing, and to file a complaint with the supervisory authority (Roskomnadzor) or a court.
10.2. Requests can be sent to info@plancy.ru. We respond within 10 (ten) business days of receiving the request.
11. Changes to this policy
11.1. We may amend this Policy. A new version takes effect on the date of publication on this page. If we materially change how Google user data is used, we will notify users and obtain their consent before the new use begins.
12. Contact details
Operator: Architectural Portal LLC
OGRN: 1237700594779
INN: 9709098730
Address: 105120, Russia, Moscow, Nizhnyaya Syromyatnicheskaya St., 10, Bldg. 2, Basmanny Municipal District.
E-mail: info@plancy.ru
Personal data officer: Andrey Sidorov, General Director