Privacy Policy

Last updated: 10 October 2026.

1. Data controller and contact

The data controller for the Plano application is Mariusz Błaszczyk. For privacy questions and data deletion requests, contact Blaszczyk8610@gmail.com.

2. What data we process and why

Plano helps users manage tasks, projects and calendars. Depending on the features used, we may process account and authentication details, task and project content, schedules, planning preferences, synchronization information, technical data needed to operate the service, and information relating to purchases and credits. Some data may be stored on the user’s device.

If AI features are used, content submitted in a request may be processed to provide the requested result. Data is used to deliver selected features, maintain accounts, secure the service and handle billing.

3. Integration with Google services

Connecting a Google account is optional. With the user’s consent, Plano may retrieve calendar lists, read, create, update and delete events, check calendar availability and, when the feature is used, read contacts. The access granted depends on the permissions accepted during authorization.

Google authorization tokens are stored in encrypted form on the server side. They are not intentionally included in public Planosphere website URLs. Users may also revoke access in their Google Account settings.

4. Service providers

Plano uses Microsoft Azure for backend services and storage, Firebase Authentication / Google for authentication and Google integrations, Google Play for distribution and purchases, and Cloudflare for hosting this website. When AI features are used, submitted content may be sent to the AI model provider handling the request. The specific processing must reflect the current application and server configuration.

5. Where data is stored

Planning data may be stored locally on a device and in a PostgreSQL database. Account and sign-in services also use Firebase Authentication. Encrypted Google tokens and connection or synchronization information are stored in Microsoft Azure Storage.

6. How long data is retained

Data is retained for as long as needed to operate the service, provide synchronization, handle support, security and payments, or comply with legal obligations. Retention varies by data category. A single verified retention period for every category and backup has not yet been established. For details about a specific category, contact Blaszczyk8610@gmail.com.

7. Account and data deletion

Users may request deletion of their accounts and personal data at Blaszczyk8610@gmail.com. The system supports deletion of saved plans and related application data, and deletion or deactivation of certain account records. Some transactional, billing and technical records may need to be retained longer, for example to comply with legal obligations.

Google connections may require separate disconnection. Deleting a Plano account does not necessarily delete Google tokens associated with every connection. To request removal of these data, disconnect Google in the application if available and contact the controller. Disconnecting Google does not automatically delete events held in the Google account.

If backups are made, data in backups may be deleted later than data in active systems, depending on backup retention settings.

8. Your rights

Users may request access to, correction or deletion of their data, restriction of processing, and exercise other rights under applicable law. Requests may be sent to the email address above.

9. Changes to this policy

The latest version of this Privacy Policy is available at https://planosphere.app/en/privacy/.