Privacy policy

saudi-bot Google integration · Effective 2026-09-21

This policy covers the Google connection identified as saudi-bot on the consent screen and its supporting workflows. It does not replace the separate policies of Google, Telegram, or other services you choose to use.

Data accessed and purposes

• Google Sheets: spreadsheet contents needed by configured workflows, including questions, answers and processing notes. The publishing workflow reads the designated worksheet and writes status notes.
• Gmail: where authorized, message content and metadata for requested mail review, summaries, drafting, sending or organization.
• Calendar: event data for requested scheduling and calendar management.
• Drive and Docs: files, document contents and metadata for requested search, document and file workflows.
• Contacts: read-only contact information for authorized lookup workflows.

OAuth credentials allow the integration to obtain short-lived access tokens without requesting your Google password. Permissions may be broader than one individual workflow; the Google consent screen identifies the permissions actually requested.

Processing and sharing

Google data is processed by the hosting infrastructure and application components used to carry out the authorized workflow. Configured educational questions can be sent to Telegram for publication. Other content may be passed to a configured processing or AI service when needed for a user-requested workflow. Do not place confidential or personal material in a worksheet intended for public publication.

Access, use and transfers of Google API data must comply with the Google API Services User Data Policy, including its Limited Use requirements. Google user data must not be sold, used for advertising, or used to develop or train generalized AI or machine-learning models. Human access must be limited to authorized operational needs and the exceptions permitted by that policy.

Storage and retention

OAuth credentials, workflow records, selected content and operational logs may be stored on the systems running the integration. Retention depends on the workflow and its operational needs; there is no single automatic deletion interval stated for all workflows. Access must be limited to authorized operators and service components. This informational website does not request your Google password or OAuth token and contains no analytics scripts; its hosting provider may process technical request logs.

Your controls and deletion requests

You can disconnect access through Google Account connections. Revoking access prevents further authorized API access but does not automatically delete previously stored records or published Telegram messages. To request deletion of stored integration credentials or Google-derived records, contact smledates@gmail.com and identify the relevant account or workflow without sending passwords or tokens. Requests may require identity verification. Copies held by third-party recipients and retention required by law may not be under our control.

Changes and contact

Updates to this policy will be published on this page with a revised effective date. Privacy and support inquiries: smledates@gmail.com.