In short: the plugin connects directly from your device to Google. The developer does not operate a server that receives your plan or Google Calendar data.
Information the plugin accesses
The plugin requests only the Google Calendar permissions needed for its calendar workflow:
- Read calendar-list metadata so you can select a calendar you are allowed to write to.
- Create a secondary calendar when you explicitly request one.
- Create events in the selected calendar and read back plugin-created events to verify that creation succeeded.
Google’s Calendar event permission is technically capable of viewing and editing events across calendars available to your account. The plugin is designed to operate only on the calendar you select and to verify events it can identify as its own.
Information sent to Google
When you approve a preview, the plugin sends the event titles, dates, start and end times, time zone, reminders setting, and private plugin identity markers required to create and verify those events. Google processes this information under the Google Privacy Policy.
Local storage
OAuth client credentials and the Google refresh token are stored through Obsidian SecretStorage on your device. Non-secret settings—such as the selected calendar ID, event IDs, configured heading, time zone, and completed-day records—are stored in the plugin’s local Obsidian data.
If you choose to synchronize your Obsidian configuration with another service or device, that synchronization is controlled by you and by the service you selected.
Collection and sharing
The plugin contains no analytics, advertising, or developer-operated telemetry. The developer does not receive, sell, rent, or share your plan, calendar contents, OAuth credentials, or usage information. Requests necessary for the feature are sent directly to Google’s OAuth and Calendar services.
Retention and deletion
You control locally stored plugin information. Using the plugin’s disconnect or reset controls clears its stored authorization and attempts to revoke access with Google. You may also revoke access from your Google Account permissions page.
Disconnecting or removing the plugin does not automatically delete calendars or events already created in Google Calendar. You can delete those directly in Google Calendar.
Security
The plugin uses Google OAuth, requests access over HTTPS, and keeps credential values out of ordinary plugin settings. No security measure is perfect, so you should protect access to your devices, Obsidian vault, Google account, and synchronization tools.
Changes to this policy
This policy may be updated if the plugin’s data handling changes. The date at the top of this page identifies the current version.
Contact
For privacy questions, email contact@ptt-calendar.tech.