Privacy policy

Planner handles the tasks, projects, goals, tags, recurring schedules, notes, and other planning information entered into the application. Browser storage keeps preferences, locally held lists, and a copy of the notepad for use between visits and recovery while offline.

Google integrations handle calendar names and identifiers, event titles, dates, times, descriptions, and relevant event details; Gmail integrations handle message identifiers, headers, subjects, senders, message bodies, and labels needed for email features. Optional Apple integrations access configured calendars and birthday/contact information. Film and TV searches send the search query to Watchmode.

Google authorization allows Planner to display calendars and to create, edit, move, or delete events for planning actions. Gmail access lets the email panel show messages, generate task or event suggestions, archive or restore messages, and manage labels used by automations.

When configured, emails assigned to the task or calendar automation labels (normally Planner/Tasks and Planner/Calendar) can be processed in the background. The automation reads their content, uses AI to extract planning details, creates tasks or calendar events, updates processing labels, and sends confirmation messages. Processing history can include message identifiers, sender and subject, extracted details, created item identifiers, status, and error information.

OpenAI processes text submitted to AI capture and titles submitted for emoji suggestions. Email-based AI features send the relevant email subject and body, instructions, and date/time context; automated email processing can also include sender information. The generated output is used for the requested planning feature.

Planner does not use Google Workspace data to develop, improve, or train generalized AI or machine-learning models. OpenAI states that API data is not used for model training by default. Its account settings and API data controls and retention rules govern its processing; AI requests and responses may be retained by the provider.

Google and Apple process requests to their connected services. Watchmode processes film and TV search requests. Hosting and network providers process data needed to deliver and operate the application, which may include request metadata such as IP addresses, browser details, and timestamps. These providers may process information in countries other than the account holder’s country.

Planner uses Google sign-in restricted to its owner. A persistent, secure, HTTP-only session cookie remembers each signed-in device. The backend stores the owner’s Google account identifier and hashed session credentials. Sessions expire after 30 days of inactivity or 90 days from sign-in and can be revoked through the app. About and Privacy pages remain public; private planning data requires authenticated access.

Planner stores planning records, shared notes, Google authorization tokens, and email automation history on its backend. Some preferences and lists are stored in the browser. Google tokens enable ongoing access and automatic refresh while the authorization remains valid.

Connections to Google and OpenAI use HTTPS. The maintainer manages the application’s hosting and service accounts. Security and access controls also depend on the deployment and provider configuration; this policy does not promise end-to-end encryption or zero retention by service providers.

Planning data is retained to support continued use until it is deleted through the app or removed by the maintainer. Stored authorization credentials and automation history remain until removed by the maintainer; the application currently has no automatic expiry schedule for those records.

Deleting a task or event does not automatically erase its source email, automation history, or records retained by external providers. Clearing browser storage removes that browser’s local copy; it does not erase shared backend notes or Google data. Provider logs and any infrastructure backups have separate retention periods controlled by the relevant provider or hosting configuration.

For deletion of backend records, authorization tokens, or automation history, email moritz.knoedler@gmail.com. The maintainer can explain which records can be removed and any remaining provider-side limitations.

• Choose which text or emails to submit to AI features. Review generated suggestions before using them.
• Remove automation labels from emails and ask the maintainer to disable background processing to stop future automated handling.
• Revoke Planner’s authorization through Google Account connections. Revocation stops future authorized access, but existing Planner records need to be deleted separately.
• Delete planning items through the app and contact the maintainer for data that has no deletion control in the interface.

Planner uses Google data to provide its personal planning features. It does not sell this data, use it for advertising, or use it to train generalized AI models. Transfers to service providers support these features.

Information received from Google APIs will be used and transferred only as permitted by the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace user data policy.

This page will be updated as Planner’s features or data practices change. Material changes to connected-account data use should be explained before that new use begins, with consent obtained where required.

Support and privacy contact: moritz.knoedler@gmail.com. Read more about Planner.