Privacy policy

1. Information accessed and processed

With the operator’s authorization, the integration accesses Google Calendar information needed to locate the designated calendar and its synchronized events. This can include calendar and event identifiers, event titles, descriptions, start and end times, and colors.

It also processes time-tracking information from Toggl Track, including entry identifiers, activity descriptions, project information, and timestamps, to create or update corresponding Google Calendar events. OAuth access and refresh tokens are used to authenticate requests to Google.

This policy covers the Google Calendar integration described on the homepage. It does not describe access to Gmail, Google Drive, or other Google services.

2. How information is used

Information is used to synchronize the operator’s time-tracking entries with Google Calendar, identify existing synchronized events, avoid duplicates, and diagnose failed synchronization runs.

Google user data is not sold, used for advertising, or used to train generalized artificial-intelligence or machine-learning models. Its use is limited to providing and maintaining this personal integration.

The integration’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

3. Storage and access

The automation runs on the operator’s self-hosted n8n instance. OAuth credentials are stored by that instance. Workflow records, execution history, and diagnostic logs may contain information processed during synchronization.

Stored instance data may also be included in the operator’s backups, including encrypted off-site backups hosted on Cloudflare R2. Access to the automation system and its stored data is intended for the operator.

Google data and OAuth tokens are not published on this informational website.

4. Transfers and service providers

The integration sends calendar requests and synchronized event content to Google Calendar. It retrieves source time-tracking information from Toggl Track. Storage and backup providers may process stored data as part of hosting and backup operations.

Workflow failures may generate email notifications through Mailjet containing the workflow name, failed step, and error message. Depending on the error, diagnostic information may include details relating to a calendar request. Google user data is not intentionally sent to Toggl Track, Lunatask, or other unrelated destinations.

Google, Toggl Track, Cloudflare, and Mailjet operate their own services under their respective terms and privacy policies.

5. Retention and deletion

Credentials are retained while the integration is connected, until they are removed from n8n. Workflow records, execution history, logs, and backups are retained according to the operator’s configured storage and retention settings; removing a record from the live instance does not immediately remove existing backup copies.

Calendar events already created remain in Google Calendar until deleted there. Original time-tracking entries remain in Toggl Track under the operator’s account and that service’s settings.

Requests to remove integration-held data or credentials can be sent to the contact below. Residual copies in backups expire under the applicable backup-retention schedule.

6. Revoking Google access

Google access can be revoked at any time through Google Account connections by selecting the app and removing its access. The operator can also remove the Google credential in n8n and disable the synchronization workflow.

Revoking access stops future authorized Google API requests. It does not automatically delete existing calendar events, workflow history, logs, or backup copies.

7. This informational website

These pages contain no analytics scripts, advertising, forms, tracking cookies, or embedded third-party assets. The hosting provider may process ordinary request information, such as IP addresses and browser metadata, to deliver and protect the website.

8. Contact and policy changes

For questions or data-deletion requests, contact Catalin at eeecatalin@proton.me.

This policy may be updated if the integration’s functionality or data handling changes. The current policy will be published on this page.