Monolith Dayboard privacy policy

Effective September 12, 2026

This policy describes Monolith Dayboard, a local calendar application developed by Endgame Training and Consultation Solutions, LLC (Endgame Solutions). It covers the installed application, its optional Google Calendar connection, and these public Dayboard information pages.

Google data the app accesses

Dayboard requests Google Calendar read-only permission (calendar.readonly) after you choose to connect your account. The current application retrieves:

• Calendar identifiers and names, colors, time zones, access roles, and selection or visibility settings.
• Event identifiers, titles, start and end dates and times, status, visibility, availability information, event type, and links to Google Calendar.

Calendar names, identifiers, and event titles may contain personal information. The app does not request event descriptions, locations, attendee lists, Gmail, Drive, Contacts, or separate Google profile information.

Dayboard lists accessible calendars, then reads events from calendars that are selected and not hidden or deleted in Google Calendar. It requests the displayed period plus one adjacent day on each side and expands recurring events. Dayboard’s own calendar checkboxes control the display; they do not narrow the Google permission or prevent those calendars from being fetched.

How the data is used

Calendar data is used to display your timeline, calculate occupied time, identify the current activity and next transition, and open Google event links you select. Activity labels are derived by local rules. Calendar data is not used for advertising, sold, or sent to AI services for inference or model training.

Dayboard’s use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Google data is used only to provide the calendar features described here.

Where data and authorization are kept

The installed application keeps calendar data in memory, with no event database or offline calendar cache. The last-loaded timeline may remain visible if a refresh fails. Closing or reloading an application window clears that window’s working view.

The local helper stores a Google renewal credential in KDE Wallet so it can reconnect on later launches. Short-lived Google access credentials remain in the helper’s memory. The installed app’s browser window receives a local session cookie and request-protection value, not those Google credentials. Local sessions expire after 12 hours of inactivity.

The saved wallet credential has no scheduled deletion date. It remains until you disconnect or remove it. Google can expire or revoke access separately. KDE Wallet and your computer’s account controls protect access to the stored credential; keep your device and user account secure.

A legacy browser-only setup is also retained for testing. In that setup, the temporary Google access credential stays in browser memory for the session and is not saved for automatic renewal.

Connections and sharing

The app connects to Google for authorization, renewal of access, and Calendar reads using HTTPS. Its window communicates with its local helper through the computer’s loopback address. Opening an event takes you to Google Calendar.

Normal Dayboard operation does not upload calendar data or Google credentials to Endgame Solutions, this website, analytics services, advertisers, or AI providers. Endgame has no central Dayboard calendar database. Google processes data under its own policies.

These public information pages are hosted through Sites and Cloudflare. Visiting them sends ordinary web-request information, such as your IP address, browser details, and requested URL, to the hosting infrastructure. Providers may process operational and security logs under their policies; that traffic does not include your Dayboard calendar or Google credentials. These pages add no analytics trackers or calendar sign-in form.

Disconnect, remove access, and clear data

1. Click DISCONNECT GOOGLE in Dayboard. On success, it removes the configured Desktop client’s saved wallet entry, clears the helper’s active access credentials and pending authorization, and returns that window to sample data.
2. Close or reload other open Dayboard windows to clear calendar information already displayed there.
3. To revoke permission at Google as well, visit Google Account connections, select the Dayboard connection, and remove its access.

Disconnecting does not delete events from Google Calendar, sign your browser out of Google, or remove other applications’ connections. Calendar originals remain in your Google account and are managed there.

Support and policy changes

If you email Endgame about Dayboard, the message and contact details you choose to send are processed to answer your request. Avoid sending sensitive calendar content or credentials. You can ask us to remove support correspondence; any applicable legal retention obligations may limit deletion.

Updates to this policy will appear here with a revised effective date. A new use of Google data will be disclosed and consent requested before it begins. Privacy questions or requests can be sent to assessment@endgametrainingandconsultation.com.