DayPilot
Privacy Policy
Last updated: November 4, 2026
DayPilot is a personal planning service that schedules your tasks around your calendar. This policy explains what information DayPilot stores, why, who else sees it, and how to remove it. It applies to the website at daypilot.app and the DayPilot apps.
Information DayPilot stores
- Account details. Your email address, display name, password hash (if you use a password), time zone, preferences, and an optional profile picture. If you sign in with Google or Apple, DayPilot stores the identifier those services use for your account so it can recognize you next time. Apple may provide a private relay email address instead of your real one; DayPilot treats it like any other address.
- Your planning data. Tasks, projects, schedules, templates, attachments you upload, and the plan DayPilot computes from them, including how often a planned block was missed.
- Docs. The docs you write (their text, files and earlier versions), who you share each one with, and their review dates.
- Calendar data. If you connect Google Calendar, DayPilot reads the events of the calendars you own that you choose (titles, times, free/busy status, recurrence) and stores a copy of the events within the planning window so it can plan around them. It writes the task blocks it plans to the calendar you pick. DayPilot keeps the authorization tokens Google issues so it can keep syncing; it does not store your Google password.
- Emailed tasks. If you send email to your private DayPilot inbox address, DayPilot stores the message, turns it into a task, and keeps a record of the sender, subject and outcome.
- Devices. If you enable notifications in the app, DayPilot stores the push token for that device.
- API keys. If you make API keys on the Developer page, DayPilot stores each key's name, its first few characters, a one-way hash of the rest, when it expires and when it was last used. The key itself is shown to you once and never stored. Anything you give a key to can see and change your data as you, until you delete the key.
- Billing. If your workspace subscribes to a paid plan, DayPilot stores the plan, its status and renewal date, and the subscription and customer identifiers assigned by the payment processor (Stripe on the website, Apple in the app). DayPilot never sees or stores your card number.
- Workspace membership. Which workspace you belong to, your role in it, groups you are in, and invitations sent to you.
- Technical logs. The server keeps short-lived logs of requests and errors for troubleshooting. They are not used for advertising or profiling.
How DayPilot uses it
Only to provide the service: planning your time, syncing with your calendar, turning emails into tasks, sending the notifications you turn on, and letting people in your workspace share the projects and docs you choose to share. DayPilot does not sell your data, show advertising, or use your data to train models.
Services DayPilot relies on
- Google for Sign in with Google and Google Calendar. DayPilot's use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements: calendar data is used only to plan your tasks and write your planned blocks back, is never transferred to others except as needed to provide the service, and is never used for advertising. You can revoke DayPilot's access at any time from your Google account's security settings or by disconnecting the calendar in DayPilot.
- Apple for Sign in with Apple, push notifications to Apple devices, and in-app purchases. Apple processes app subscriptions under its own privacy policy; DayPilot receives only the subscription status, not your payment details.
- Stripe to take payment for plans bought on the website. Your card details and billing address go directly to Stripe and are handled under Stripe's privacy policy; DayPilot receives a customer identifier, the plan and its status.
- OpenAI to draft a title, estimate and due date from an email you send to your inbox address. The content of that email is sent to OpenAI for that purpose only. Email is not sent to OpenAI unless you use the inbox feature.
- Resend to receive the emails you send to your DayPilot task address ([email protected]), and to deliver DayPilot's own emails: the link that confirms your address when you sign up with a password, password reset links and notices, and workspace invitations. Resend handles those messages and their sender and recipient addresses; it does not receive your tasks or calendar.
- Cloudflare for DayPilot's domain name and to carry the encrypted traffic between your device and DayPilot's private network, which it also protects from attacks. Everything you see in DayPilot passes through Cloudflare on its way to you; it delivers it and does not use it for anything else.
How DayPilot shares Google user data
Google user data is what DayPilot receives from Google: your name and email address when you use Sign in with Google, and, if you connect Google Calendar, your list of calendars and the events on the calendars you own that you choose. Calendars other people share with you are never read. DayPilot does not sell Google user data. It shares, transfers or discloses it only as follows:
- Cloudflare carries it, encrypted, between DayPilot's private network and your device, for example when the planner shows your calendar events. It is only delivered, not stored or used.
- Resend receives your email address to deliver the emails DayPilot sends you, and Stripe receives it if you buy a plan on the website.
- People in your workspace see your name and email address in member lists. On a Team plan, workspace owners and admins, and the managers of your groups, also see how many hours of work are planned for you and how many free hours you have in the coming week. Free hours take into account time marked busy on your connected calendars; they never see your events' titles, times or any other details.
- Authorities, if the law requires it (for example, a valid court order), limited to what is required.
Your calendar events are never sent to OpenAI, Apple, Stripe or Resend. DayPilot does not use Google user data, including data from Google Workspace APIs, for advertising, and does not use it to develop, improve or train generalized or non-personalized AI or machine-learning models.
How DayPilot protects sensitive data, including Google user data
DayPilot treats Google user data (your name and email address from Google, your calendar list, and the calendar events it copies) and the rest of your personal data as sensitive, and protects it with these measures:
- Encryption in transit. Data crossing the internet is always encrypted: HTTPS between your device and Cloudflare, and an encrypted Cloudflare Tunnel from Cloudflare to DayPilot's router. From the router it travels only over DayPilot's private network to the server. Browsers are told to use only secure connections, and DayPilot talks to Google's APIs only over HTTPS.
- Encryption at rest. The tokens that let DayPilot reach your Google Calendar, and the titles of the calendar events it stores, are encrypted in the database using ASP.NET Core Data Protection, with keys kept separately from the database, so a copy of the database alone cannot reveal them. Event start and end times are kept unencrypted so DayPilot can find your free time. DayPilot never sees or stores your Google password.
- Access control. Every request is checked against your account and workspace, so no one can read another person's calendar data or another workspace's data. Uploaded files are served only after the same checks.
- Account security. Passwords are stored only as salted, one-way hashes, and API keys as one-way hashes. Repeated failed sign-ins lock the account for a while, and sign-in attempts are rate limited.
- Least data and short retention. DayPilot asks Google only for the permissions it needs, reads only calendars you own and choose, and keeps copies of events only within the planning window. Disconnecting a calendar deletes those copies and DayPilot's stored access, and removes the task blocks DayPilot added while it can still reach your calendar. Deleting your account deletes your data and revokes DayPilot's access at Google.
- Infrastructure and operator access. DayPilot is self-hosted on servers the operator controls rather than with a cloud provider. The server and the database are on a private network that cannot be reached from the internet: requests reach the server only through the encrypted tunnel, which ends at the network's router. Only the operator can access the servers, for maintenance and support. Backups stay on the same servers and are deleted after 14 days.
- Security incidents. If DayPilot learns of a breach that affects your data, it will tell affected users without undue delay and take steps to contain it.
Who can see your data
Your personal tasks and calendar are visible only to you. Work you place in a shared group is visible to that group's members, and a doc is visible only to the people, groups or workspace you share it with (and the docs under it with it), and workspace admins can see who is in the workspace. On a Team plan, workspace owners, admins and group managers also see each member's planned and free hours, as described above. Nobody outside your workspace can see your data. The operator of the server can access the database for maintenance and support and does not look at your content otherwise.
Retention and deletion
Data is kept while your account exists. You can delete tasks, projects, docs, attachments and calendar connections individually at any time. Deleting your account (Preferences → Account on the web, or Settings → Account in the app) removes your personal data, uploaded files, calendar copies and device tokens, revokes DayPilot's access at Apple and Google, and removes any DayPilot-created events from your Google Calendar. Shared group work, and docs you shared with others, stay with the workspace. Backups are kept for 14 days and then overwritten.
Children
DayPilot is not directed at children under 13 and does not knowingly collect information from them.
Changes
If this policy changes in a way that matters, the date above will change and the website will say so.
Contact
Questions about privacy, requests about your data, or anything else: [email protected].