Privacy policy

Effective November 3, 2026.

Purpose and information used

This personal integration exports approved WhatsApp news-channel text from the operator's existing collection system and text from four public Telegram channel preview pages to two separate private Google Drive files for a daily ChatGPT briefing. Telegram sources are calcalist, interil, TechNewsHeb and the7eye; no Telegram login, session, channel joining or private-content access is used. Records include channel and message identifiers, channel names and links, text or captions, publication and collection timestamps, a content hash, and collection-health fields. No private statuses, private chats, contact lists, session data, media files or source-system credentials are included in the exported files.

Google access

The publisher requests only https://www.googleapis.com/auth/drive.file. It creates and updates its two dedicated snapshot files, checks the signed-in publisher's email address, and manages each file's specific viewer permission. It does not request general access to the user's Drive library. OAuth tokens are stored in access-restricted local and server files and are not included in the snapshots or public website.

Sharing and processing

The snapshot is private to the authorized publisher and the specifically approved briefing account, which has reader access. Google stores the file; the connected ChatGPT account reads it for the requested briefing. Subsequent ChatGPT processing is governed by that account's OpenAI settings and terms. The integration does not sell this information, use it for advertising, or use Google Workspace data to train generalized AI or machine-learning models. Its use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including Limited Use requirements.

Retention and security

Each current export contains a rolling 24-hour window and is limited to 1 MiB. WhatsApp is limited to 100 records; Telegram is limited to 20 text records per channel and 80 total, from the latest public preview page only, with possible coverage gaps. Updates replace each file's contents. The Telegram collector does not retain a separate message database or raw preview archive. Unpinned Drive revisions are subject to Google's revision-retention rules; removal from the current snapshot does not guarantee immediate deletion from revision history or provider backups. Operational logs record status, counts and timestamps rather than message bodies or tokens. The existing WhatsApp source database has its own retention policy. The server's credentials and protected backups remain until the operator removes them or revokes access.

Control and deletion

You may revoke the application's access in your Google Account connections, stop the publisher, remove the viewer permission, or delete the snapshot in Google Drive. Revoking OAuth access stops future authorized updates but does not itself delete the existing file or copies already included in briefings. Contact rshaham@gmail.com for access, correction or deletion requests concerning this integration.

This information website

These static pages do not collect form submissions or run application analytics or advertising scripts. The hosting provider may process ordinary request and security logs, such as IP addresses, under its own policies. This website does not expose the briefing dataset.

Google API Services User Data Policy · Terms of use