DayTandem Privacy Policy

Summary

DayTandem is a local-first day planner for Windows and macOS. Your schedules, lists, layouts, and settings are stored on your device. Garda Studio does not operate any server that receives your planner data, and the app has no accounts, analytics, telemetry, crash reporting, advertising, or tracking.

Connecting Google Calendar is optional. If you connect it, calendar data travels only between your device and Google.

Who is responsible

DayTandem is published by Dmytro Shubchynskyi under the trading name Garda Studio. Privacy questions can be sent to support@garda-studio.com.

Data stored on your device

The app keeps a local SQLite database in the application data folder of your operating system user account, or in the data folder next to the portable executable. It contains:

• your weekly schedule, lists, list items, and notes;
• compact layouts and appearance, language, timer, sound, and window settings;
• up to 10 recent copies of this data, used to recover from errors;
• selected Google calendar IDs, which may contain an email address. Older builds also store a cached calendar list and event snapshot; builds with database schema 2 use memory-only snapshots.

This data is not sent to Garda Studio. The app does not encrypt it, so protect your device and user account. Backups you export are JSON files under your control; they never include Google tokens or cached calendar events.

Google Calendar

If you choose Connect Google, you sign in on Google’s own page in your browser and can grant these permissions:

• View events (calendar.events.readonly): to show events for today and the next 7 days from the calendars you select;
• Manage events in calendars you own (calendar.events.owned): used only to create a new event when you submit the quick add form. The app never edits or deletes existing events;
• View your calendar list (calendar.calendarlist.readonly): so you can choose which calendars to show.

Calendar data is requested directly from Google and displayed on your device. In builds with database schema 2, calendar lists and event snapshots are held only in process memory, not written to the app database. The refresh token is kept in the operating system’s secure credential store (Windows Credential Manager or macOS Keychain), and the short-lived access token stays in memory. Google user data is never sent to Garda Studio or any other third party, is not sold, is not used for advertising, is not read by people, and is not used to develop, improve, or train generalized artificial intelligence or machine learning models.

DayTandem’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

To disconnect, choose Sign out of Google in the app’s settings. This removes the stored token and the cached calendar data from your device and asks Google to revoke the app’s access. You can also remove access at any time in your Google Account permissions. Events in your Google Calendar are not deleted.

Data protection

Requests to Google for authorization tokens and calendar data use HTTPS with certificate validation. Browser sign-in uses PKCE and a state check; its HTTP callback is restricted to the local loopback interface on your device. DayTandem does not collect your Google password.

Refresh tokens are protected by Windows Credential Manager or macOS Keychain under your operating system account. Access tokens stay in process memory; neither type of token is included in the planner database or JSON exports. The planner database and exported files are not encrypted by DayTandem. Protect your account and backups and use device encryption where appropriate.

Memory-only calendar snapshots are cleared when you sign out or quit the app. During a temporary network failure, the last snapshot from the current session may remain visible with its sync time. After restarting offline, events must be fetched again; your ordinary planner remains available. Selected calendar IDs are retained as settings and can appear in planner backups.

On the first launch of a schema-2 build, DayTandem removes the older disk calendar cache, compacts the active SQLite database and truncates its write-ahead log. This does not remove copies you made elsewhere or guarantee forensic erasure from SSD storage, operating-system swap or hibernation files. Older installed builds keep their previous caching behavior until upgraded.

Signing out removes the locally stored token and calendar snapshot and requests revocation at Google. If the network request fails, local sign-out still takes place, but you may need to revoke access in your Google Account permissions. No calendar events are deleted at Google.

Network connections

The app connects to the internet only for these purposes:

• Google sign-in and Google Calendar requests, only while Google Calendar is connected;
• checking for and downloading updates, only in builds where automatic updates are enabled. These requests contain no personal or planner data, but like any web request they reveal your IP address and basic request details to the hosting provider of the update server;
• opening links you click, such as this website or an event in Google Calendar, in your browser.

If you install DayTandem from an app store, the store operator may process data such as installation, purchase, and diagnostic information under its own privacy policy.

Retention and deletion

Local data stays on your device until you delete it. You can delete individual items, reset the app to its defaults, or uninstall it. The Windows uninstaller offers to remove the local app data. On macOS, delete the app.daytandem.desktop folder in ~/Library/Application Support after moving the app to the Trash. For the portable version, delete its folder. Signing out of Google removes the stored token and the cached calendar data.

Children

DayTandem is a general-audience productivity app and is not directed to children under 13.

Your rights and contact

Because planner and calendar data stay on your device, Garda Studio holds no copy that it could access, correct, or delete on your behalf. If you email the studio, that correspondence is handled as described in the Garda Studio website privacy notice. Questions about this policy can be sent to support@garda-studio.com.

Changes

This policy will be updated before DayTandem adds accounts, analytics, crash reporting, cloud sync, or any other feature that changes how data is handled. The effective date above shows the current version.