Privacy Policy

Account data. When you sign in with Google, we receive your name, email address, profile photo URL, and a unique Google account identifier. We store these in our database to identify your account across sessions.

Google Calendar data. With your explicit consent during OAuth, Planck reads events from calendars you authorize and, when you enable scheduling actions, creates or updates events on those calendars. This includes event titles, start and end times, attendees, descriptions, location, and event IDs.

Preferences and focus data. Your working hours, timezone, lunch window, focus-time goals, trust level, and similar scheduling settings. When you run focus sessions, we record the spell's start and end time to produce your focus log.

Operational data. Sign-in timestamps, request logs, and error reports generated by your use of the app. These help us keep the service running and diagnose bugs.

Billing data (if applicable). If you subscribe to a paid plan, our payment processor (Stripe) collects your payment details. Planck only stores a customer identifier and subscription status; we never see your card number.

We use your data only to run Planck:

• Display your calendar, identify focus blocks, cluster meetings, and surface conflicts in the product.
• Create, move, or shorten calendar events when you ask Planck's agents to act, or when you start, pause, or stop a focus spell.
• Train the agents' context for your session: your working hours, lunch, and focus goals inform the system prompt sent to the model.
• Send daily briefings and alerts to the channels you opted into.
• Process payments, handle refunds, and enforce plan limits.
• Detect abuse, debug errors, and keep the service operational.

We do not sell or rent your data. We do not use your calendar or focus data to train general-purpose machine learning models.

Planck's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

• We only request the Google Calendar scopes required to deliver Planck's scheduling features. You can review the scopes at the consent screen.
• We use Google Calendar data only to provide or improve user-facing features that are visible in the Planck product.
• We do not transfer Google user data to third parties except as necessary to provide or improve those features, comply with applicable law, or as part of a merger, acquisition, or sale of assets with notice to you.
• We do not use Google user data for advertising, for training generalized AI or ML models, or for any purpose unrelated to the scheduling features Planck provides.
• We do not allow humans to read your Google user data, except with your explicit consent for a specific message, when necessary for security purposes (e.g., investigating abuse), to comply with applicable law, or in aggregated and anonymized form for internal operations.

Planck relies on a short list of vendors to run the service. Each is bound by contract to use your data only to provide their service to us:

• Google — authentication and Calendar API access.
• Neon — managed Postgres database where your account, preferences, and focus history are stored.
• Google Cloud Platform — application hosting, task queues, and scheduled jobs.
• Anthropic and Google (Gemini) — large language model inference for the scheduling agent. Only the minimum context needed for the current request is sent (e.g., today's events, your preferences).
• Stripe — payment processing for paid plans.
• Resend — transactional and digest email delivery.
• Sentry — crash and error reporting. We strip sensitive fields before emission wherever practical.

We do not share your data with advertisers, data brokers, or other third parties beyond the vendors above.

Your data is stored in Postgres on managed infrastructure in asia-south1 and encrypted at rest. All traffic to and from Planck uses TLS.

We retain your account data and focus history for as long as your account is active. If you delete your account, we remove your personal data within 30 days, except where we are legally required to retain it (e.g., invoices for tax purposes).

Google Calendar tokens are stored encrypted. You can revoke Planck's access at any time from your Google Account security settings; we will stop accessing your calendar on the next request.

You can, at any time:

• Access and export your data from Settings → Data. We provide a JSON export of your preferences, focus history, and decisions.
• Correct your preferences directly in Settings.
• Delete your account and associated data from Settings → Data → Delete account. Deletion is permanent within 30 days.
• Revoke Google access independently of your Planck account at myaccount.google.com/permissions.

If you're in the EEA, UK, or a jurisdiction with equivalent laws, you also have the right to lodge a complaint with your local data protection authority.

Planck is not intended for users under 13 (or the minimum age in your jurisdiction). We do not knowingly collect data from children. If you believe we have, contact us and we will delete it.

Planck's infrastructure is hosted primarily in India (asia-south1). By using the service you consent to your data being processed in India and any other regions where our vendors operate.

We may update this policy as the product evolves. Material changes will be announced via email or in-app notice. The effective date at the top of this page always reflects the current version.

Questions, deletion requests, or data-subject requests: zara@ani.computer.