Application information
Privacy policy
Last updated: September 20, 2026
Dayboard is a personal household calendar/task display operated by its owner. This policy covers the local Dayboard application and this separate public information site. Contact: 585mjduffy@gmail.com.
Provider data and permissions
The owner authorizes a Google Account, supplies a Todoist personal API token through a hidden local prompt, and chooses the calendar and selected Todoist project displayed. Dayboard can list available calendars and Todoist projects so the owner can make those choices.
- Google Calendar: read-only access. Selected event data may include titles, start/end times, locations, calendar names, identifiers, recurring-event information and update timestamps. Dayboard does not create, edit or delete Google Calendar events.
- Todoist: Dayboard reads all open tasks and project collaborators in one owner-selected, invite-only household project. Data may include task titles, descriptions, due dates, recurrence, completion status, project and task identifiers, assignee display names and update timestamps. Complete and Undo send task-status changes to Todoist; the application then reads back the result before confirming it. Dayboard does not create or delete tasks through the dashboard.
- Authorization: OAuth client credentials and access/refresh tokens allow the local application to access Google Calendar after the owner's consent. A Todoist personal API token can authorize account API access; Dayboard verifies the account and confines its implemented reads and writes to the one selected project. The token is entered and stored only on the private host. During protected setup, an approved invitation email address may be sent directly to Todoist to share that project.
How the application uses and stores data
Data is used to display the selected agenda and tasks, refresh the local cache, and confirm requested task changes. Google Calendar is the source of truth for events and Todoist is the source of truth for household tasks. Display-only event hiding is stored locally and does not change Google.
Google credentials and tokens, the Todoist personal API token, cached data, resource selections, action confirmations, approved invitation records, device pairing/session records and application logs are stored in a private per-user application directory on the owner's Windows computer, outside the source repository. Backups may contain copies of this private state. Basic client diagnostics can include browser user agent, screen/viewport dimensions and activity timestamps.
The local display browser uses device-session and anti-forgery cookies. These are used to authorize paired devices and protect local actions, not to track visitors across websites. The public information site does not set application cookies.
The application is intended for a trusted private network. Its current local HTTP connection is not encrypted: household calendar/task data and paired-device cookies travel over that local connection. Do not expose the dashboard directly to the internet or use it on an untrusted network.
Sharing and Limited Use
Calendar API requests go from the local host to Google over HTTPS. Household-task reads and requested task-status changes go from the local host to Todoist over HTTPS. Authorized paired devices receive the selected dashboard data over the local network.
Dayboard data is not sold and is not used for advertising, profiling, or training AI models. The application does not send calendar/task content, provider credentials or device-session credentials to this public website or Cloudflare. Dayboard follows the Google API Services User Data Policy and its Limited Use requirements for Google data.
Retention, revocation and deletion
Cached snapshots are replaced during successful refreshes. Selections, local event visibility settings, action confirmations, session state and logs are retained locally until changed or removed by the owner; there is no promised automatic purge. Backups are separate copies and may remain after live state is removed. Uninstalling the application does not automatically remove private application data or backups.
To revoke future Google access, remove Dayboard from your Google Account third-party connections. To revoke Todoist access, reset the API token in Todoist and remove the locally stored token. Revocation does not itself erase local cached copies or change provider data.
To delete local copies, the owner can stop only Dayboard and remove its private application data and any retained backups. This removes its local credentials, cache and pairing state, but does not delete Google Calendar events or Todoist tasks. Contact the operator for help with access, revocation or deletion. Do not email tokens, pairing codes or task/calendar content.
This public website
This site contains only application information and these policies. It has no Google login, personal dashboard, analytics scripts, advertising or forms. Cloudflare hosts the pages and may process ordinary visitor request metadata, such as IP address, user agent and request timing, for delivery, security and operational diagnostics. Query strings are redacted from the Worker's sampled diagnostics. See Cloudflare's privacy policy for its processing practices.
If you email support, your email address and message are used to respond to that request through the operator's email provider. Include only the information needed for support.
Changes and contact
Updates will be posted here with a revised date. For privacy questions, contact 585mjduffy@gmail.com.