DynamicLand for macOS

DynamicLand Privacy Policy

This page provides a copy of the DynamicLand Privacy Policy for users who reach it through existing in-app links. The main website version is available at https://hypercubicapp.online/privacy.html . This policy concerns DynamicLand for macOS.

Last updated: September 22, 2026

This policy explains how DynamicLand handles information through its Google Calendar integration and the other app features described below. References to the DynamicLand developer mean the developer providing the application, reachable at [email protected] .

Connecting Google Calendar is optional. You authorize the connection through Google, and you can disconnect it in DynamicLand. Other features have their own permissions, settings and data stores.

The essential distinction: Calendar records are cached on your Mac, but calendar synchronization communicates with Google. Actions such as opening a meeting, requesting directions, sharing information or using a cloud-enabled Assistant can involve other recipients. Disconnecting Calendar does not erase every independent copy of information you have saved or shared.

1. Google user data DynamicLand accesses

After you authorize Google Calendar, DynamicLand receives authorization tokens and the following categories of information, where available and permitted by your Google account:

• Account identity: your Google account's stable identifier and email address. The app also records the connection date to manage the account locally.
• Calendar metadata: calendar identifiers, names and display-name overrides, colors, time zones, access roles, primary-calendar status, and selection or deletion flags.
• Event content and metadata: event identifiers, titles, descriptions or notes, locations, start and end dates and times, time zones, all-day status, recurrence rules and occurrence references, reminders, event-page links, availability, status, visibility, event type, colors or labels, and update or version information.
• Event participants: organizer and creator names and email addresses, and attendee names, email addresses, responses and role information, such as optional-attendee or organizer status.

For supported changes to this and future occurrences of a recurring event, the app can retrieve additional series information, including guest permissions, additional guests or resources, custom event properties, attachment metadata, conference information and incomplete-attendee, locked or private-copy flags. This information helps preserve supported settings or identify an operation the app cannot safely perform. Retrieving attachment metadata does not download the attachment files.

Decoded account, calendar and ordinary event records are stored locally. Additional series information is processed for the operation; the app does not separately archive the full raw series response. Some nested response data is received temporarily without being retained in the decoded records. Not every retained metadata field is displayed separately in the interface.

Google permissions

• https://www.googleapis.com/auth/calendar.events allows the app to read, create, edit and delete events where your account permits those actions.
• https://www.googleapis.com/auth/calendar.calendarlist.readonly allows the app to read your calendar list and its metadata.
• openid and email identify the connected account and its email address.