gog

Privacy policy

Effective 7 October 2026

slpixe operates gog for access to his own Google account. Contact: slpixe@gmail.com.

Google account data

The setup accesses only data covered by the permissions slpixe grants. Its current permissions allow reading Gmail messages and metadata, sending requested emails, reading calendars and events, and managing events on calendars slpixe owns. It does not have Gmail mailbox-management or deletion permission.

Google account data is used to perform the owner’s requested email and calendar tasks. A local authorized assistant may process relevant data using its configured AI provider to carry out those tasks. Data handling by that provider is governed by the owner’s account settings and the provider’s policies.

Storage and sharing

gog stores OAuth refresh tokens in the operating system’s credential store. Email or calendar information may also be retained in local task files or the assistant’s conversation history when needed for a requested task. The owner controls those files and the assistant’s retention settings.

Information is shared with Google to perform API requests, with the configured assistant provider when used for an authorized task, and with email recipients or event attendees when the owner requests sending or invitations. This setup does not sell Google account data, use it for advertising, or use it to train a generalized AI model.

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

This website

This public information site does not connect to Google accounts, receive OAuth tokens, or store email or calendar content. It uses no analytics, tracking cookies, or contact forms. Cloudflare hosts the site and may process request information such as IP addresses for delivery and security under its privacy policy.

Revoking access and deleting data

The owner can revoke the app’s access through Google Account connections, remove the local gog credentials, and delete local task files or assistant conversations using their respective controls. Revoking access stops future API access; it does not delete previously retained files or conversations.

Updates

This page will be updated when the setup’s permissions or data practices change.