PRIVACY / UPDATED SEPTEMBER 16, 2026
Your visit and
your choices.
Invitations and basic operation
Exit First Notes prepares a Telegram invitation in the background when an invitation page opens. This creates a random visit ID and a signed session token stored in your browser so that repeat clicks reuse the invitation. It does not automatically open Telegram or grant advertising consent.
Our service associates the invitation with that random visit. Telegram sends the bot a join request and membership update when you use it. The bot approves valid requests automatically without a greeting. A real membership update—not a button click—is the join event. A shared backup invitation is available during outages; it cannot reliably attribute an individual advertising click.
Optional advertising measurement
If you opt in, we may store the Google click identifier from the URL and the campaign identifier with your visit and send a confirmed join to the assigned Google Ads account. Without that consent, invitation preparation does not send advertising identifiers to our invitation API. Consent is optional and does not change your access.
Optional personalized advertising
A separate checkbox permits the Google tag and advertising cookies. Consented events such as a visit and a prepared invitation can build advertising audiences. A join is not inferred from a click. Eligibility to use an audience is subject to Google’s rules. We do not send your Telegram username or private messages to Google.
Local exercise and browser memory
The three-line exercise on the story page stays in that browser tab and is not submitted to our server. The invitation token and advertising choices may be remembered in local storage for up to 180 days. Use “Withdraw ad choices / reset invitation” on the channel page to withdraw future advertising use and reset the remembered invitation. Withdrawing does not recall data already processed by Google.
Service providers and operational records
Cloudflare hosts the pages and application, Telegram provides the channel and bot API, and Google provides advertising. Operational logs and anonymous error counters help us keep invitations available. We hash network addresses for rate limiting rather than keeping raw addresses in that table. Service providers may process network data under their own policies.
Invitation and join records are retained for attribution, troubleshooting and reconciliation, then reviewed for deletion; access is limited to the project’s operators. Contact us for access, correction or deletion requests. Do not send passwords or financial account credentials.