Privacy Policy

Last updated: October 27, 2026

This Privacy Policy explains how Project (“Project”, “the App”, “we”, or “us”) accesses, collects, uses, stores, protects, shares, retains, and deletes information when you use the Project mobile application for iOS and Android. Project is a task, planning, and personal productivity application.

By using Project, you acknowledge the practices described in this Privacy Policy.

1. App owner and contact
Project is owned and operated by an individual (self-employed) based in the Russian Federation.
Contact email: karina@projectapp.ru

2. Information we collect

2.1 Account information
When you create or use an account, we may process your email address, authentication identifiers, and the name or profile image provided by an authentication provider such as Google or Apple, when available.

2.2 Content you create in Project
We store content you voluntarily create, including tasks, projects, areas, goals, notes, reminders, schedules, time blocks, date intervals, settings, and other information you enter into the App. This content is associated with your Project account.

2.3 App settings and technical data
We may process your time zone, language and display preferences, application configuration, device and operating-system information needed for compatibility, app launch events, error diagnostics, and timestamps related to synchronization or activity. We use this information to operate, secure, troubleshoot, and improve user-facing App functionality.

3. Google user data and Google Calendar integration
Google Calendar integration is optional. Project accesses Google user data only after you choose to connect a Google account and grant the requested permissions. You can use Project without connecting Google Calendar.

3.1 Google user data Project accesses
When you connect Google Calendar, Project may access:
• your Google Account identifier and email address, so the App can identify and display the connected account;
• the list of calendars available to that account, including calendar identifiers, names, colors, time zones, access roles, and selection status;
• events from calendars you select for synchronization, including event identifiers, titles, descriptions, dates and times, time zones, all-day status, recurrence rules and exceptions, locations, meeting links, organizers, attendee details and response status, attachments, reminders, visibility, and event status;
• changes to selected calendars and events that are necessary to keep synchronized Project items current.

Project requests access only to the Google data required to provide the calendar synchronization feature. Calendar-list access is used to let you choose calendars and configure synchronization. Calendar-event access is used for the two-way synchronization described below.

3.2 How Project uses Google user data
Project uses Google user data solely to provide and improve user-facing Google Calendar features that you request. These features include:
• showing selected Google Calendar events in Project as tasks with time, time blocks, or date intervals;
• providing offline access to synchronized items on your devices;
• synchronizing supported changes in both directions between Project and Google Calendar;
• creating, updating, moving, or deleting Google Calendar events when you perform the corresponding action in Project;
• maintaining recurrence, synchronization state, and background updates for selected calendars.

Project does not use Google user data for advertising, personalized or interest-based advertising, retargeting, credit or lending decisions, surveillance, or sale to data brokers or information resellers. Project does not sell Google user data.

Google Workspace APIs are not used to develop, improve, or train generalized artificial-intelligence or machine-learning models. Google Calendar data is not used to train generalized AI or ML models.

3.3 Storage and protection of Google user data
To provide synchronization across devices, background synchronization, and offline access, Project may store copies of selected calendar events, calendar metadata, links between Google events and Project items, synchronization settings, and synchronization state in Project’s cloud infrastructure and on your authorized devices.

Google OAuth access and refresh tokens are stored only in server-side protected storage and are encrypted at rest using AES-GCM encryption. Tokens are not stored in PowerSync, application analytics, or logs. Data is transmitted using HTTPS/TLS. Database access controls and row-level security are used to isolate data by Project account. We apply access restrictions and other reasonable technical and organizational safeguards designed to protect the confidentiality and integrity of Google user data.

3.4 Sharing and disclosure of Google user data
We do not sell, rent, or disclose Google user data for advertising or marketing. Google user data may be processed only:
• by Google, when Project reads an event or when you direct Project to create, update, move, or delete a Google Calendar event;
• by infrastructure providers, including Supabase and PowerSync, solely as necessary to host, synchronize, secure, and deliver Project’s user-facing features;
• when necessary to investigate abuse or a security incident;
• when required by applicable law or legal process.

Service providers may process data only to deliver their contracted services to Project. Human access to Google user data is prohibited unless you explicitly request support and consent to access to the specific data, access is necessary for security or abuse investigation, or access is required by law.

3.5 Retention, deletion, and user control
Google authorization tokens are retained only while the Google Calendar connection remains active. When you disconnect a Google account in Project, the stored OAuth tokens for that connection are deleted and future synchronization stops. You may also revoke Project’s access at any time in your Google Account permissions.

Calendar-derived copies already stored in Project may remain after disconnection so that your existing Project plans remain available. You can delete those items in Project or delete your Project account. Deleting a Project account removes the account data and stored Google authorization tokens from Project, but does not automatically delete events that already exist in Google Calendar.

Our use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.

4. Notifications
Project uses local notifications on your device to deliver reminders and alerts you configure for tasks, schedules, and goals. Notification data is primarily processed locally on your device. We do not send advertising notifications.

5. Payments
Paid subscriptions are processed by the Apple App Store or Google Play Store. We do not collect or store payment-card details.

6. Other data storage and processing
Project uses cloud infrastructure provided by Supabase and synchronization infrastructure provided by PowerSync. Project’s Supabase region is Northern Europe (Stockholm, Sweden, AWS). Data may be transferred to and processed outside your country of residence where permitted by applicable law.

7. Other data sharing
Apart from the Google-specific practices described above, we do not sell or rent personal data. We may share data with service providers strictly necessary for authentication, cloud storage, synchronization, security, diagnostics, and App operation, or when required by law. Service providers may process data only to provide services to Project.

8. General data retention and deletion
We retain personal data while your account is active or for as long as reasonably necessary to provide a feature you enabled, comply with legal obligations, resolve disputes, and protect the App. When data is no longer required for these purposes, it is deleted or anonymized according to applicable retention practices.

You can delete your Project account from the App. You may also contact karina@projectapp.ru to request access, correction, or deletion of associated personal data.

9. Your rights
Depending on your location, you may have rights to access, correct, delete, or obtain a copy of your personal data, object to or restrict certain processing, and withdraw consent. Contact us using the email above to exercise applicable rights.

10. Children’s privacy
Project is not intended for children under the age of 13, and we do not knowingly collect personal data from children under 13.

11. Changes to this policy
We may update this Privacy Policy when the App, its integrations, or legal requirements change. We will update the “Last updated” date and provide additional notice or request consent when required. We will keep this policy current with our use of Google user data.

12. Contact
Questions or requests regarding this Privacy Policy can be sent to:
karina@projectapp.ru