Personal data

Privacy Policy

Revision of 8 September 2026

This Policy sets out how the personal data of users of the PlannexPro mobile app, the plannexpro.app website and related services (together, the "Service") is processed and protected.

1. Operator

The operator of personal data:

Individual entrepreneur Evgeny Vladimirovich Savenko
TIN (INN): 504015256006
State registration number (OGRNIP): 317502700057270
Registered address, and the address for written enquiries: Prudovaya street 1, Zabolotye village, Ramenskoye municipal district, Moscow region, Russia
Email for privacy and data protection matters: privacy@plannexpro.app
Website: https://plannexpro.app

2. Scope

This Policy applies to data processed when you install and use the app, create an account, use server features, contact support, and visit the website.

The app works without an account. Your calendar entries live in the Android system calendar and are synchronised by the calendar provider you have chosen — Google, Microsoft Exchange or a CalDAV provider, for example. PlannexPro reaches them through Android's own interfaces once you grant permission.

Reading this Policy does not replace the separate consent to processing that the law requires in some cases.

3. What data is processed

3.1. Your PlannexPro account

Creating and using an account may involve:

• email address;
• an additional contact email address;
• an internal user identifier;
• details of your sign-in methods;
• a one-time confirmation code;
• session access and refresh tokens;
• subscription status and expiry;
• the device model and manufacturer reported when settings are synchronised;
• app language, region and time zone.

When you sign in with VK ID, the app receives an authorisation token and passes it to the PlannexPro server to confirm the sign-in. VK may process data under its own privacy policy. The Operator never receives your VK password.

PlannexPro tokens are kept in the app's private local storage and excluded from Android backups.

3.2. Calendar

Once you grant permission, the app reads and changes Android system calendar data, including:

• event titles, descriptions, dates and times;
• locations;
• time zones and recurrence rules;
• attendees and their email addresses;
• reminders;
• details of calendars and calendar accounts.

This data drives the calendar views, widgets, search, and the creation and editing of events and reminders. Events are saved to the Android system calendar and may be synchronised by its provider on that provider's terms.

PlannexPro does not send your whole calendar to its own server. When you use server-side voice parsing, however, the text you typed or dictated, the names of your available calendars and tags, your local time and your time zone are sent to the server — solely to interpret the command.

3.3. Contacts

Once you grant permission, the app may query Android contacts and enterprise directories for the name, email address and postal address of a person you are inviting. The lookup runs as you type an attendee's name.

PlannexPro does not build a copy of your address book on its server. The details you pick may be added to an event in the system calendar and then synchronised by that calendar's provider.

3.4. Location, addresses and routes

Once you grant permission, the app may obtain your approximate and precise location, and — for the route widget — your location in the background.

Location is used to:

• determine the weather;
• work out travel time to an event's location;
• draw the map and remind you when to leave.

For weather, the app sends the PlannexPro server coordinates rounded to roughly three decimal places, or the place name you chose, along with the language. The server may query WeatherAPI.

For routes, the origin and destination coordinates may be processed. For Pro subscribers they are sent to the PlannexPro server, which may use Google Maps Platform / Routes API. Otherwise the coordinates may be sent to the public OSRM service. To draw maps the app loads OpenStreetMap and CARTO tiles; those services receive the network details of the request, including your IP address.

An event's address may be passed to the Android system geocoder. Which provider handles it depends on your device and the services installed on it.

The app caches recent route data and map images locally. This cache is excluded from the app's cloud backup.

3.5. Voice commands

The app does not request direct access to the microphone. Speech recognition is performed by the Android system service you have chosen, and PlannexPro receives the finished text.

If you start server-side parsing of a command, the following is sent to the PlannexPro server:

• the recognised or typed text;
• the language;
• your local date and time;
• your time zone;
• the names of calendars and tags needed to make sense of the command.

The result may contain a title, time, place, attendees and other details of the event or task being created. You decide whether to start server-side parsing before anything is sent.

3.6. Tasks and integrations

If you connect Google Tasks or Todoist, the PlannexPro server may receive from that service, and send to it:

• the identifier of the connected account;
• task titles;
• due dates, priorities and completion status;
• task links and identifiers;
• the tokens the integration needs to work.

This data is used to show, create and complete tasks at your request. How the task provider itself handles data is governed by its own policy.

3.7. App settings

Interface, widget, weather, route and other settings are stored locally. If you are signed in, settings are synchronised with the PlannexPro server automatically so they carry over between devices. The device model and manufacturer are sent along with them.

3.8. Diagnostics

When the app crashes it saves, locally, the app version, device model, Android version, time, thread name and the technical stack of the error. The file is not sent anywhere automatically. You can send it to support yourself.

The current version of the app contains no third-party SDKs for automatic analytics or remote crash reporting.

3.9. Purchases and subscription

Using paid features may involve the purchase identifier, plan, purchase source, status and subscription expiry. Payment details are handled by the store or the payment provider; the Operator never receives your full card number. The available payment channels are named in the purchase interface.

3.10. Website and enquiries

When you visit the website, the hosting server may automatically process your IP address, the date and time of the request, the address requested, the User-Agent string and the technical outcome of the request. Your theme choice is stored locally in your browser.

The website runs Yandex Metrica, a web analytics service operated by Yandex LLC. Metrica collects details of your visit: IP address, cookie identifiers, the addresses of pages viewed, the referring source, details of your browser, device, language and screen resolution, and your actions on the page.

This is processed for statistical purposes — to understand which parts of the site are used and what is worth improving. Processing on the service's side follows Yandex Metrica's own terms. You can opt out through your browser: block cookies or install a blocking extension.

The site carries no advertising trackers and no other third-party analytics. The PlannexPro mobile app contains no third-party analytics at all.

When you contact support, your email address, the content of the correspondence, any attachments and anything else you choose to share are processed.

4. Purposes and legal bases

Data is processed in order to:

• register you, sign you in and protect your account — to conclude and perform our contract with you;
• provide the calendar, widgets, reminders, weather and routes — to perform the contract and at your request;
• access your calendar, contacts and location — on the basis of Android permissions and, where required, your consent;
• run voice parsing and integrations — to deliver the feature you asked for;
• synchronise settings — to perform the contract with you while you are signed in;
• confirm your subscription and provide paid features — to perform the contract and to meet legal requirements;
• prevent abuse and protect the Service — on the basis of the Operator's legitimate interest, where it does not override your rights;
• handle enquiries and comply with lawful demands — to perform the contract, meet a legal obligation, or defend legitimate interests;
• send marketing messages — only with your prior consent.

The Operator does not use data for purposes incompatible with those it was collected for, and does not sell personal data.

5. Android permissions

The app may request access to your calendar, contacts, notifications, and approximate, precise and background location. It also uses system capabilities for exact alarms, full-screen reminders, drawing over other apps, and exemption from battery optimisation.

Permissions can be revoked in Android settings. Features that do not objectively need a revoked permission keep working. Background location is requested separately and is needed only for the live route in the widget and the reminders that depend on it.

6. Recipients of data

Depending on the features you use, data may be passed to:

• the Russian hosting provider TIMEWEB.CLOUD LLC (TIN 7810945525, OGRN 1227800052215) — to host the backend, the database, backups and the supporting infrastructure in the Russian Federation;
• TIMEWEB.CLOUD LLC — to operate the mail infrastructure and deliver one-time sign-in codes to your email address;
• TIMEWEB.CLOUD LLC — as the provider of the AI infrastructure used for server-side parsing of your commands; the command text, language, local date and time, time zone and the names of your calendars and tags may be sent;
• VK ID — when you sign in with VK;
• WeatherAPI — when a forecast is fetched through the PlannexPro server;
• Google Maps Platform / Routes API — for Pro routing and through Android system services;
• OSRM — when a route is calculated on the free tier;
• OpenStreetMap and CARTO — when map tiles are loaded;
• the system calendar or contacts provider you have chosen;
• Google LLC — when Google Tasks is connected and used;
• Doist Inc. and the parties that operate Todoist with it — when Todoist is connected and used;
• Google Play, RuStore or another payment provider — when you make a purchase;
• Yandex LLC — when you visit the website, limited to what Yandex Metrica collects;
• state authorities — only where there is a lawful basis.

Anyone processing data on the Operator's instructions receives only the data they need and must meet confidentiality and security requirements.

7. Localisation and cross-border transfer

The PlannexPro backend and its principal database are located in the Russian Federation, on Timeweb Cloud infrastructure. When collecting the personal data of citizens of the Russian Federation, the Operator ensures compliance with part 5 of article 18 of Federal Law No. 152-FZ, which requires that recording, systematisation, accumulation, storage, amendment and retrieval be carried out using a database located in the Russian Federation, save for the exceptions the law allows.

Using foreign services may result in a cross-border transfer — in particular with Google Maps, Google Tasks, Todoist, WeatherAPI, OSRM, OpenStreetMap, CARTO, a foreign calendar provider or a foreign store.

8. Retention and deletion

Data is kept no longer than the stated purposes and the law require. The following periods or criteria apply:

• account data — until the account is deleted, then up to 30 days, apart from data that must be retained;
• session tokens — until sign-out, revocation, expiry or account deletion;
• synchronised settings — until the account is deleted or their storage is switched off;
• voice command text and the technical data of the request — up to 30 days;
• route and weather data on the server — up to 30 days;
• the local route cache — normally until the data is refreshed or the app's data is cleared;
• map tiles — locally, up to 30 days;
• the local report of the most recent crash — until the next crash, until you delete it, or until the app is uninstalled;
• support correspondence — up to 30 days;
• payment and accounting records — for the period the law prescribes;
• web server logs — up to 30 days;
• website analytics data — for the periods set by Yandex Metrica.

Once the purpose is met, data is destroyed or anonymised unless another lawful ground for keeping it exists. Data in backups is removed as backups rotate on schedule, within 30 days.

9. Deleting your account

You can delete your account with the "Delete account" button on the account page in the app, or by sending a request to privacy@plannexpro.app.

The procedure is described on a separate page: https://plannexpro.app/en/account-deletion.

The Operator may ask for reasonable confirmation that the account is yours. Once confirmed, the request is carried out without undue delay, normally within 30 days; a demand to stop processing is handled within the periods set by article 21 of Federal Law No. 152-FZ.

Data that must be retained by law is blocked from use for any other purpose until the mandatory period ends.

10. Your rights

You have the right to:

• learn whether your personal data is being processed, and receive the information the law provides for;
• demand that inaccurate, outdated, excessive or unlawfully processed data be corrected, blocked or destroyed;
• withdraw consent and demand that processing stop, where no other lawful ground applies;
• opt out of marketing messages;
• complain about the Operator's actions to Roskomnadzor or to a court;
• exercise any other right applicable law provides.

Send your request to privacy@plannexpro.app or to the Operator's postal address. Include enough detail to locate the account and confirm your authority, along with what you are asking for. The Operator may request further proof of identity, so that data is not disclosed to — or deleted at the request of — someone else.

11. Security

The Operator applies the legal, organisational and technical measures required: restricted access, TLS in transit, short-lived access tokens, revocation of refresh tokens, exclusion of tokens and the location cache from backups, redundancy, component updates, logging of security events, and oversight of processors.

No method of transmission or storage is completely secure. In the event of an incident, the Operator carries out the investigation and notification duties the law imposes.

12. Children

The app carries a 3+ age rating, but a child may create an account, give consent and use paid features only as applicable law allows and, where required, with the involvement of a legal representative.

If the Operator learns that a child's data was obtained without the representative's required consent, it takes steps to stop processing and delete the data. A representative can write to privacy@plannexpro.app.

13. Changes to this Policy

The current revision is published on a permanent, publicly accessible page of the website. Material changes are communicated through the app, the website or by email. Where a new purpose requires consent, processing for that purpose begins only once consent is given.

14. Contact

Individual entrepreneur Evgeny Vladimirovich Savenko
TIN (INN) 504015256006
OGRNIP 317502700057270
Address: Prudovaya street 1, Zabolotye village, Ramenskoye municipal district, Moscow region, Russia
Email: privacy@plannexpro.app

You may also contact the Federal Service for Supervision of Communications, Information Technology and Mass Media (Roskomnadzor).