Last updated: September 2026.
Note: this is a plain-language draft written to be honest and specific about what Dayrail actually does, not a substitute for legal advice. Before relying on it — including for Stripe's subscription requirements or Google's OAuth verification review — have it checked by a lawyer familiar with privacy law in the jurisdictions where you have users.
When you sign in with Google, Dayrail receives your name, email address, and a profile identifier from Google. If you grant Calendar access, Dayrail also receives read and write access to your Google Calendar events.
Dayrail stores the tasks you create (title and duration), the times you schedule them, and, for tasks you schedule, the identifier of the Google Calendar event created for that task. This data is stored in Dayrail's database, hosted on Cloudflare.
Dayrail requests Google Calendar access to:
Dayrail does not read, modify, or delete calendar events that you did not create through Dayrail, other than displaying their time and title so you can see your day.
Your task and schedule data is retained for as long as your account is active. If you'd like your account and associated data deleted, contact us at the address below and we'll remove it.
Dayrail uses a signed session cookie to keep you logged in, and a small cookie to remember whether you've seen today's morning planning screen. Neither is used for advertising or tracking across other sites.
Dayrail is built on Cloudflare (hosting and database) and Google (sign-in and Calendar API). Each has its own privacy policy governing how they handle data on their end.
If this policy changes materially, we'll update the date at the top of this page.
Questions about this policy or your data can be sent to hello@dayrail.app.