Privacy and cookie policy

When you open the bot from this website, we record the source and subsequent actions internally by default. Google Analytics and Yandex Metrica remain disabled until you explicitly allow external analytics.

01

What this page covers

This policy describes data processing on onlyscreener.pro, internal source and user-action records in the OnlyScreener Pro Telegram bot, and the OnlyScreener Backups database recovery tool. The landing pages do not ask for a name, email address, payment-card data or exchange credentials. Telegram, payment providers and other external services also apply their own privacy policies.

02

Necessary storage

Local storage remembers your language, motion preference and cookie choice. Session storage remembers whether the intro has already been shown in the current tab. These settings do not build an advertising profile and cannot be disabled through the analytics banner because the site needs them to respect your choices.

03

Internal and external analytics

When you click a bot link, our server creates an internal click record: a random code, page, time, source label, campaign parameters and yclid when present in the page URL. The code is passed to the bot and linked to your Telegram identifier, registration, trial access and payment. This record does not use analytics-provider cookies and does not itself authorize sending data to Metrica or Google Analytics.

With separate permission, basic analytics enables Yandex Metrica and an external-analytics attribution record that may also contain a Yandex ClientID. Extended analytics additionally enables Google Analytics. Raw ClientID and yclid values are retained for 90 days. A code not linked to Telegram expires after 21 days. Source labels and funnel events remain for reporting. Providers may set analytics cookies such as _ga, _ga_* and Yandex _ym_* cookies. Webvisor session recording is disabled.

04

Why analytics is used

We use data for OnlyScreener’s internal analytics: evaluating useful pages and traffic sources, linking a visit with registration, trial access and payment, improving the interface and understanding subscriber acquisition performance. OnlyScreener does not use internal attribution records to select personalized advertising. Analytics is not used to make trading decisions, evaluate your portfolio or access exchange accounts.

05

Your choice

“Basic analytics” allows Yandex Metrica and external attribution. “Extended analytics” additionally enables Google Analytics and grants Google analytics storage. “No external analytics” keeps both providers unloaded; internal bot-click records remain enabled. Withdrawing consent stops future external uploads and revokes active external attribution access; it does not promise deletion of records already uploaded or internal history.

06

Providers and contact

The link between a visit, a Telegram user identifier, a subscription and a payment is stored in OnlyScreener’s database and accessible to authorized administrators. We do not sell or publish internal attribution records.

When basic analytics is allowed, visit data is sent to Yandex. To match registration, trial access and first-payment events, Metrica may receive ClientID and/or yclid, the event type and time, and the first-payment amount and currency in a supported format. This export does not contain the Telegram user identifier or username. When extended analytics is allowed, visit data is also sent to Google Analytics.

External analytics services process the data they receive under the policies and retention settings of Google and Yandex. For questions about this website or this policy, contact us through @OnlyScreenerProBot.

07

Google Drive access

OnlyScreener Backups is an administrative tool for recovering the service after a failure or data loss. After the operator connects their Google account, it uses the drive.file permission to create, read, verify and delete backup files in its dedicated folder. It reads backup file identifiers, sizes and other metadata, and available storage capacity. The configured tool works with files it creates; it does not request access to visitors’ or subscribers’ Google accounts. Google authorization tokens are stored in a configuration accessible only to authorized administrators and are used to maintain this connection.

08

Backup storage and retention

Database copies may contain Telegram user identifiers, subscription and payment records, signals and position history held by OnlyScreener. Before upload, backup contents and filenames are encrypted; Google Drive stores the encrypted files. Decryption keys are stored separately from the Drive copies. Once enabled, automatic retention keeps copies from the five latest successful daily dates and four latest successful calendar weeks; a copy qualifying for both is stored once. Older copies are permanently deleted only after a new copy passes verification. Failed or incomplete runs can delay deletion while an administrator investigates. Three completed local copies are retained on the server; incomplete local copies require manual review.

09

Use, access and revocation

Google Drive data is used only to store, verify and recover backups. It is not sold, used for advertising or used to train AI models. Google provides cloud storage under its privacy policy; authorized OnlyScreener administrators may access backup data for recovery and troubleshooting. The operator can revoke access in their Google account connections. Revocation stops future Drive access but does not itself delete existing cloud or local copies. The operator can remove cloud copies in Drive and request removal of local copies and connection credentials through @OnlyScreenerProBot. Use of Google API data is subject to the Google API Services User Data Policy, including applicable Limited Use requirements.

Last updated: October 16, 2026.