Privacy policy

1. Scope and operator

The integration runs on infrastructure controlled by Zach Rideout and is configured for the owner’s personal use.

The public information website does not connect visitors’ Google accounts, display private calendar data, or collect Google credentials. Questions about the integration or this policy can be sent to zrides@gmail.com.

2. Information the integration accesses

Google Calendar

The integration requests calendar.events to read, create, change, and delete events on calendars the authorized account can access, within Google’s access controls. Its configuration selects one destination calendar. It also requests calendar.calendarlist.readonly to read the calendar list and metadata needed to find that calendar.

Calendar information can include event identifiers, titles, dates and times, locations, descriptions, recurrence details, cancellation status, organizer and attendee information, and meeting links included in the source material. Read operations may also return existing events on the selected calendar for matching and reconciliation.

Forwarded email

Using a separately configured Gmail app password and IMAP connection, the integration reads messages under a selected Gmail label. These may include forwarded original messages, meeting invitations, attachments, calendar snapshots, and messages without calendar content. Upstream forwarding and any email relay are configured by the owner.

Credentials and service records

The integration uses Google OAuth tokens and the Gmail app password to maintain its connections. Local records include message and event identifiers, processing outcomes, timestamps, event descriptions, and recurring invitation data. Operational logs can contain event titles, identifiers, and error details.

3. How the information is used

The integration uses this information to apply the owner’s requested calendar sync, match existing events, process updates and cancellations, avoid duplicate processing, keep a local message archive, and diagnose failures.

After processing a message, the service adds a done or error label in Gmail. When configured to do so, it also archives the message by removing it from the Inbox. It does not delete the original message.

This calendar-sync integration does not sell the information, use it for advertising, or use it to train generalized artificial-intelligence or machine-learning models.

Use of information received from Google APIs is limited to these disclosed purposes and is subject to the Google API Services User Data Policy, including its Limited Use requirements.

4. Storage and recipients

• Google: The integration communicates with Google’s authorization, Calendar, and Gmail services. Events written to the destination calendar and original Gmail messages are stored by Google under the account’s settings and Google’s policies. Copied events are visible according to the destination calendar’s sharing settings and the events’ visibility settings.
• The owner’s infrastructure: Local storage holds OAuth credentials, the separately configured Gmail credential, sync state, logs, and an offline archive. The archive includes full raw messages and their attachments, sanitized HTML copies, and an index containing message metadata and processing results. Local preview reports, if generated, can contain event descriptions and details of existing calendar events. The operator and anyone with administrative or storage access to the host can read local records.
• Forwarding services: Before the integration reads a message, the owner’s configured source-email and relay services may process that message. Those services operate under their own terms and privacy policies.
• Backups: Copies made by the owner can retain calendar exports, messages, state, or other local data. Their location and removal are controlled by the owner.

The integration is not a public calendar-sharing service. This information website contains no private messages, calendar events, access tokens, or app passwords.

5. Retention, revocation, and deletion

The local archive and sync state have no automatic age-based deletion. They remain until the owner deletes them. Log retention depends on the deployment’s log settings, and backups remain until removed through the owner’s backup process.

The account owner can stop the service, remove its connection credentials, and revoke the n8n-ai authorization in Google Account connections. Gmail app-password access is managed separately in the account’s app-password settings.

Those copies must be removed separately from their respective storage locations. Contact zrides@gmail.com about access or deletion requests related to this integration.

6. This website

These static pages include no analytics scripts, advertising, sign-in forms, or application cookies. The hosting provider may process ordinary request and security information, such as an IP address, requested URL, browser information, and request time, to deliver and protect the pages. Links to Google open services governed by Google’s own policies.

7. Changes and contact

This policy will be updated when the integration’s data practices change. The date at the top identifies the current version.

Operator: Zach Rideout
Contact: zrides@gmail.com