Privacy policy

Privacy, plainly.

DayBoard keeps your calendar, tasks, reminders and mail between your Mac and the services you connect. This page explains what goes where. Last updated November 5, 2026.

The DayBoard app

  • No tracking. The app has no analytics, advertising or tracking, and DayBoard has no server that receives your calendar, tasks, reminders or mail.
  • On your Mac: settings, linked items and Assistant history are stored locally. Google sign-in tokens are encrypted with macOS's built-in protection.
  • Google: when you sign in, DayBoard asks for access to Google Calendar, Google Tasks and, in the beta, Gmail. It talks to Google's APIs directly from your Mac to show and change those items for you. Signing out deletes your Google sign-in tokens from your Mac and asks Google to revoke DayBoard's access.
  • Apple Reminders: read and changed on your Mac through macOS, with your permission.
  • AI (optional): nothing goes to an AI provider until you choose one. AI features send data to the provider you chose, through its app on your Mac (such as Claude Code or Codex) or with your API key. With each message, the Assistant sends a snapshot of up to 60 events, 80 open tasks and reminders, and your 30 latest emails (sender, subject and a short preview), and it can look up more as it answers. Other features, such as the daily briefing, send the items they cover. If you turn on the automatic briefing, it runs the first time you open DayBoard each day, without a click. That provider handles the data under its own terms. Dictation sends your recording to OpenAI for transcription, only when you use it.
  • MCP server (optional): off by default. When you turn it on, it runs only on your Mac, and clients need the access key shown in Settings. Apps you connect to it can read your calendar, tasks, reminders and mail, make changes if you allow them, and may send what they read to their own AI providers.
  • Updates: beta 11 and earlier never check for updates. Starting with beta 12, DayBoard checks GitHub, where its releases are published, for a newer version shortly after it opens and every few hours, and downloads updates from there. GitHub receives those requests, including your IP address, under its own terms; they carry none of your calendar, tasks, reminders or mail.
  • Licenses (paid versions only): activating a license sends your license key, an installation ID and the label "DayBoard on macOS" to DayBoard's license service, which checks it again about once a day. DayBoard computes the installation ID one-way from your Mac's hardware UUID, so it stays the same if you reinstall DayBoard or delete its data, and every macOS account on that Mac sends the same one. The hardware UUID itself is never sent or stored. If DayBoard can't read it, the installation ID is random. Beta builds have no license and never contact that service. See Purchases.

Google user data

DayBoard's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

DayBoard uses Google data only to show and change your calendar, tasks and mail inside the app, and, when you ask, to send the relevant items to the AI provider you chose. It doesn't sell Google data, use it for advertising, or use it to develop or train AI models.

This website

  • Waitlist: if you join the waitlist, we store your email address, the time you joined and internal review labels in DayBoard's signup database, and the DayBoard team gets an email with your address. Joining doesn't guarantee an invitation. We use your address only to contact you about early access and major DayBoard news, and we never sell or share it. We keep it until the waitlist closes or you ask us to delete it.
  • Abuse protection: to limit repeated signup attempts, the signup service keeps a keyed hash of your IP address, not the address itself.
  • No cookies or trackers: this site sets no cookies and runs no analytics (checkout, on a separate page, sets one; see Purchases). Fonts and images are served from this site. Our hosting provider processes basic request data, such as IP addresses, to deliver the site and block abuse.

Purchases

  • Payment: DayBoard Pro is sold through Link, Stripe's checkout service, which is the seller of record. Stripe and Link collect your payment details, email address and billing location to take the payment, calculate tax, send your receipt and prevent fraud, under the Stripe privacy policy and Link privacy policy. DayBoard never receives your card number.
  • What DayBoard keeps: DayBoard's license service stores an order record with Stripe's IDs for the checkout and payment, its status (paid, refunded or disputed), your license key (encrypted) and, for each Mac you activate, its installation ID (computed one-way from that Mac's hardware UUID, never the UUID itself, or random if DayBoard couldn't read it) and the label "DayBoard on macOS". It doesn't store your name, email address or payment details. To limit abuse, it briefly keeps a keyed hash of your IP address, not the address itself. We can see your purchase in our Stripe account when you ask for help or a refund.
  • Checkout cookie: the checkout page on api.getdayboard.com sets one cookie that lets the receipt page show your license key on the same browser. It expires after seven days and isn't used for tracking.

Removal and questions

To have your email removed, or to ask about this policy, email the DayBoard team. For purchases and refunds, email support@getdayboard.com. If this policy changes, we'll update this page and the date above.