1
Information We Collect
Account and identity information
When you sign in, ModePilot stores account information such as your email address, display name, profile image URL, provider subject identifiers, and session data needed to keep you authenticated.
If you use the desktop app, ModePilot may issue desktop access tokens and store token metadata such as label, platform, creation time, and last-used time.
Connected service data
If you connect Google Calendar, ModePilot accesses the selected calendar and retains a limited rolling range of calendar event data needed to support calendar automation, longer out-of-office periods, calendar views, and historical time tracking.
ModePilot stores a deliberately limited calendar event projection rather than the complete response returned by Google. The retained fields are restricted to information required for active features, such as event identity, title, timing, recurrence, availability, your own attendance response, color, and ModePilot-managed metadata.
The synchronized calendar mirror does not retain event descriptions, locations, conference links, attachments, organizer or creator records, other attendees’ identities, or unrelated Google event fields unless a future feature clearly requires them and this policy is updated accordingly.
If you connect Slack, ModePilot stores workspace and user identifiers, granted scopes, limited profile metadata, and OAuth credentials needed to apply the status, presence, and DND behavior you configure.
If you connect Telegram, ModePilot stores the bot credential and chat identifier needed to send the confirmations you enable. Telegram mode confirmations are sent only after ModePilot has successfully made a corresponding Slack-facing change.
If you connect Everhour, ModePilot stores the credential, limited profile and project or task metadata, configuration, and synchronization state needed to create and maintain the time records you request.
Configuration and operational data
ModePilot stores schedules, mode rules, overrides, habits, integration settings, work windows, schedule snapshots, activity history, time tracking records, and related operational state required to run the product.
This may include limited event-derived context, scheduler results, mode-change history, time-tracking categorization, and content-free health or recovery metadata used for explainability and reliable operation.
Optional usage analytics
Optional usage analytics is off by default. Where available, you can enable it in Settings → Privacy & Data. Opening Settings or completing onboarding does not enable it.
Optional analytics helps us understand which ModePilot features get used. These records describe app usage and do not contain calendar or Slack content.
If enabled, PostHog processes selected feature events and application page visits in the United States, linked to a pseudonymous account identifier. Names, email addresses, form entries, and screenshots are also excluded. Session recording and automatic interaction capture are disabled.
2
How We Use Information
Core product operation
ModePilot uses your data only to provide and improve the features you choose, including determining your current mode, evaluating schedules, applying overrides, updating Slack status and presence, sending eligible Telegram confirmations, and generating activity and time-tracking views.
If you enable calendar scheduling or habits features, ModePilot may create calendar events according to your settings. Its scheduling features update, reschedule, or delete only events created by ModePilot; they do not modify or delete events created by you or other applications.
If you enable Everhour sync, ModePilot may create, update, or delete Everhour time records and may auto-create related Everhour projects or tasks when required by the configured sync behavior.
Google API data
ModePilot’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Google data is used only to provide or improve visible ModePilot features that depend on it. It is not used for advertising, sold to data brokers, or used to train general-purpose artificial intelligence models.
Human access to connected Google data is restricted to cases where you explicitly request support and provide permission, where access is necessary to investigate security or abuse, or where access is legally required.
Reliability, security, and support
ModePilot also uses operational data to keep the service running, troubleshoot failures, audit actions, prevent misuse, and explain why an automation decision was made.
We do not use your data for advertising, data brokerage, or unrelated profiling.
Product analytics and improvement
When you opt in, ModePilot uses limited usage analytics to understand which application features are used and improve the product experience. You can keep using ModePilot with optional analytics off.
3
Storage and Security
Per-user encryption
ModePilot uses per-user encryption to protect retained calendar content and private content in new or updated activity, automation, and workday records. Each user's protected content is secured with keys unique to that user.
ModePilot's application services can decrypt protected content when needed to run the features you enable, including automation while you are offline. This is server-side encryption, not end-to-end encryption.
Credentials and transport
Integration credentials stored by ModePilot—including OAuth access and refresh tokens, API keys, and Telegram bot tokens—are encrypted before database storage.
Connections between your browser and ModePilot, and supported connections between ModePilot and integration providers, use HTTPS or equivalent encrypted transport.
Authentication secrets, encryption keys, raw calendar payloads, and calendar content are excluded from calendar synchronization health records and operational job diagnostics.
Data minimization and separation
ModePilot retains only the connected-service fields needed for enabled product behavior and keeps synchronization, evaluation, and delivery records separate from readable calendar content.
Opaque identifiers are used in the encrypted calendar mirror instead of storing raw Google calendar and event identifiers as searchable database values.
Security posture
Our hosting provider maintains an ISO/IEC 27001:2022-certified information security management system.
ModePilot combines per-user encryption, encrypted integration credentials, access controls, validated webhooks, and content-minimized diagnostics to help protect your information.
No online service can guarantee complete security or uninterrupted protection against every threat. ModePilot reviews its safeguards as the product and its integrations evolve.
You remain responsible for protecting access to your connected accounts, devices, and any third-party credentials you choose to provide.
4
Data Sharing
When data is shared
ModePilot does not sell or rent your personal data.
ModePilot sends data to Google, Slack, Telegram, Everhour, or another connected provider only as needed to perform a feature you have enabled. Infrastructure providers may process encrypted or operational data on ModePilot’s behalf subject to appropriate restrictions.
ModePilot may disclose information where required by law, or where reasonably necessary to protect users, rights, security, or service integrity.
If you enable optional usage analytics, PostHog processes the limited analytics information described in this policy on ModePilot’s behalf.
5
Retention and Control
Retention
Synchronized calendar event data is retained for a limited rolling period based on the needs of ModePilot’s calendar automation, calendar views, and historical time-tracking features.
ModePilot keeps account configuration, activity history, derived time-tracking records, and other operational information for as long as reasonably needed to provide requested history, operate the service, troubleshoot problems, and satisfy legitimate business or legal needs.
Disconnecting Google Calendar stops future synchronization and deletes the active encrypted calendar mirror and the wrapped per-user calendar key used to decrypt it. Disconnecting another integration removes or disables the credential used for future access. Historical activity, derived reporting records, or records already sent to another provider may remain unless separately removed.
Deleting your account removes your account and associated active application records. Limited residual copies may remain temporarily in routine backups or where retention is required for security, legal compliance, or the establishment, exercise, or defense of legal claims.
Your choices
You can disconnect integrations, delete your account from Profile Settings, revoke access directly with the original provider, or contact us about access, portability, or other privacy requests.
Account deletion does not remove records that ModePilot previously created in connected services, such as Google Calendar events or Everhour time records. You continue to control those records in the relevant service.
If OAuth access or other required credentials are revoked, some features may stop working until the connection is restored.
For more control over online tracking, ModePilot recommends Brave Browser, which includes built-in tracker blocking through Brave Shields. Using Brave is optional; you can also use privacy controls or content blockers in your preferred browser.
You can turn optional usage analytics off in Settings → Privacy & Data. Withdrawal stops collection in the browser immediately, and ModePilot requests deletion of associated provider analytics data. If saving fails, the browser remains opted out and you can retry saving your preference.
7
Your Privacy Rights
Access, correction, export, and deletion
You can delete your account through Profile Settings, disconnect integrations, and update the settings available in your account. You can also contact [email protected] to request access to your personal data, corrections, an export, or deletion.
Depending on applicable law, you may also have rights to restrict or object to processing, withdraw consent where processing relies on consent, and receive a portable copy of your data. You may complain to the relevant privacy regulator where that right applies.
We may need to verify your identity before fulfilling a request. We handle requests within the time limits required by applicable law, subject to lawful exceptions. The retention and connected-service limits described above also apply to deletion requests.
8
Children
Not for children under 13
ModePilot is intended for workplace productivity and is not directed to children under 13. Children under 13 are not permitted to use the service, including in the United States. We do not knowingly collect personal information from children under 13.
If you believe a child under 13 has provided personal information to ModePilot, contact [email protected]. If we learn that we have collected such information, we will take steps to delete it and disable the child's account.
9
Changes and Contact
Policy updates
We may update this Privacy Policy from time to time. The updated version becomes effective when posted to this page. Continued use of ModePilot after an update means you accept the revised policy.
Questions about this Privacy Policy can be sent to [email protected].