Application information

Privacy policy

Last updated: September 17, 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.

Google data and permissions

The owner authorizes a Google Account and chooses the calendars and selected task lists displayed. Dayboard can list the available calendars and task lists so the owner can choose them.

• 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.
• Google Tasks: Google's authorization scope permits task management, but Dayboard uses it only to read chosen lists, complete or reopen existing tasks, and read back each change to confirm it. Data may include task titles, notes, due dates, status, list names, identifiers and update timestamps. Dayboard does not create or delete tasks.
• Authorization: OAuth client credentials and access/refresh tokens allow the local application to access Google APIs after the owner's consent.

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 is the source of truth. Display-only event hiding is stored locally and does not change Google.

Google credentials, tokens, cached data, resource selections, action confirmations, 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

Google API requests go from the local host to Google over HTTPS. Requested task-status changes are sent back to Google. 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 Google calendar/task content, OAuth 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.

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. Revocation does not itself erase local cached copies or delete events/tasks in Google.

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 Google 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.