Privacy policy

How YTpanel.click handles personal data

Below is an overview of the data the service receives, including Google user data during sign-in and data received through the Telegram bot, how that data is used, protected, stored, shared, and deleted.

YT Panel markYT Panel
Disclosure for Google and Telegram

This policy explicitly explains what Google and Telegram data the service receives, why it is needed, how long it is stored, and that we do not sell it or use it for advertising.

Effective date

April 10, 2026

This version aligns with Google OAuth privacy policy requirements and includes Telegram-specific disclosures: what the service receives from Telegram, how it uses that data for account linking, notifications, and communication, and how a user can disconnect Telegram and request deletion.

1. Scope of this policy

This policy applies to the public site `ytpanel.click`, the application `app.ytpanel.click`, and the YTpanel.click service as a whole.

It explains how YTpanel.click receives, uses, stores, protects, and deletes personal data, including data received through Google OAuth 2.0 / OpenID Connect and through the Telegram Bot Platform.

Telegram remains a separate platform with its own privacy policy. This page governs data processing by YTpanel.click and does not replace Telegram’s policy.

2. Data we collect

Account data such as email, name, avatar URL, and profile attributes received through Google sign-in.

Workspace data such as members, invitations, tags, channels, sync history, and related YouTube metrics.

Technical data such as IP address, browser data, session identifiers, system logs, and security-related events.

Communication data such as invitation recipient emails, Telegram link data, and support correspondence.

3. Google data we receive

During Google sign-in we request only the basic `openid`, `email`, and `profile` scopes.

Within those scopes, YTpanel.click receives the Google user data required for authentication and account creation: Google account identifier, name, email, and profile image if available.

We do not request access to Gmail, Google Drive, Google Calendar, or other Google data unless it is explicitly added to the product and disclosed in this policy.

4. Telegram data we receive

When the Telegram bot is connected, YTpanel.click may receive your Telegram user id, chat id, username, first name, and last name if they are available in your profile.

If you start the bot, send commands, messages, files, contacts, or a phone number, the bot may receive the data that Telegram Bot Platform provides to our service.

For account linking we generate a short-lived, one-time link. The database stores a hash of the token rather than its raw value.

5. Why we process data

To create accounts, maintain sign-in, and manage workspace access.

To add channels, sync public YouTube data, and display analytics inside YTpanel.click.

To connect Telegram, confirm ownership of the Telegram account, and send service notifications or support replies.

To send invitations, access-change messages, and support communication.

To prevent abuse, investigate incidents, protect the service, and improve product stability.

6. How Google and Telegram data is used

Google user data is used only for sign-in, user identification, profile creation, session support, and workspace access management.

Telegram data is used only within product functions related to account linking, service notifications, bot replies, and Telegram-based support workflows visible inside the product.

We do not use Google or Telegram user data for targeted advertising, resale, data brokerage, or unrelated external scenarios.

We do not use Google user data to train general-purpose AI models unrelated to the user-facing functions of YTpanel.click.

7. Legal basis, cookies, and technical mechanisms

We process data to provide the service, meet contractual needs, protect legitimate security interests, and comply with applicable law.

YTpanel.click uses technical cookies and similar mechanisms for authorization, session continuity, form protection, and stable interface behavior.

We may store local interface settings, such as selected workspace or display preferences, to improve repeat visits.

8. Sharing and protection

We may share data with infrastructure, hosting, email, communications, payment, or accounting providers when needed to operate the service.

We may disclose data to state authorities or other authorized parties when required by law or necessary to protect rights and service security.

We apply organizational and technical safeguards to protect data against accidental loss, unauthorized access, modification, and disclosure.

No internet service can guarantee absolute security, so we recommend using a secure Google account and carefully managing workspace access.

9. Retention and deletion

Account and workspace data is stored while the account remains active or while it is needed to provide the service.

Security logs and technical records may be retained longer when justified by incident investigation, abuse prevention, or legal requirements.

Google sign-in data is retained as long as necessary to support the account and session unless a longer period is required by law.

Telegram link data is retained while the Telegram connection is needed for product functions or until the user disconnects Telegram and requests deletion.

You may request account and personal data deletion via the contact address below.

10. User rights and policy updates

You may request access to your data, correction of inaccuracies, deletion, restriction of processing, and export of the data you provided to us.

You may also object to certain types of processing where applicable and withdraw consent when processing is based on consent.

We may update this policy when product functionality, infrastructure, or legal requirements change. The current version is always published on this page.