← Home
Last updated August 15, 2026

Privacy policy

This policy explains what Clippyprom collects, why we collect it, and the choices you have. We keep it plain and specific so you always know where your data lives and how it is used.

Who we are

Clippyprom is a verified short-form clipping and distribution service. We connect creators to campaigns, verify the clips they post, count real views, and pay earnings. If you have any question about this policy or your data, contact us at contact@clippyprom.xyz.

What we collect

  • Account email. When you sign up we collect the email tied to your account through Supabase Auth.
  • YouTube channel identity and public metrics. When you connect a channel through Google OAuth, we read your channel identity, public subscriber count, and public video view counts using a single read-only scope, youtube.readonly. We request no write, upload, delete, or management access, and no other Google or YouTube scopes.
  • Clip links and public view counts. We store the links to the clips you submit and the public view counts we poll for those clips.
  • Audience region. We collect the general audience region reported for your content so we can match campaign eligibility.

We store only links and metrics. We never download, host, or store the videos themselves.

How we use it

  • Verify that you own the channel you connect.
  • Match you to campaigns you are eligible for.
  • Count verified views on the clips you post.
  • Calculate and pay your earnings.
  • Detect and prevent fraud across the platform.

Where your data is stored

Account data, clip links, and metrics are stored in Supabase on a managed Postgres database. OAuth tokens are stored encrypted. We apply access controls so only the systems that run the clipping service can read your data.

How we protect your data

We protect all user data, and sensitive data such as Google and YouTube data and OAuth tokens in particular, with the following mechanisms:

  • Encryption in transit. All connections to Clippyprom and to Google APIs use HTTPS with TLS. Data is never transmitted in plain text over the network.
  • Encryption at rest. OAuth access and refresh tokens are encrypted at rest using strong symmetric encryption (AES-based Fernet) before they are written to the database. Encryption keys are held as server secrets, separate from the database, and are never stored in source control.
  • Least-privilege access. Only the application service and a small number of authorized administrators can access production data, over authenticated, access-controlled connections. We request the minimum scope needed (read-only youtube.readonly) and no more.
  • Secure infrastructure. The database and authentication are hosted on Supabase; the application runs on a hardened server behind an HTTPS reverse proxy with automatically renewed certificates.
  • No AI/ML training. We do not use Google user data, or any other user data, to develop, improve, or train generalized artificial intelligence or machine-learning models.
  • Revocation and deletion. Disconnecting a channel revokes the stored OAuth tokens at the provider and deletes them from our systems. You can also delete your account and associated data at any time (see below).

Third parties

We share the minimum data needed to run the service with a small set of providers: Google and YouTube (to read your channel identity and public metrics under the read-only scopes above), Supabase (authentication and database hosting), and our crypto payout processing partner (to send your earnings to the wallet you provide). We do not sell your data to anyone.

Google API Services and Limited Use

Clippyprom's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We only use YouTube data to operate the clipping service, that is, to verify channel ownership, match campaign eligibility, and count verified views. We never use YouTube data to build advertising profiles, and we never sell YouTube data or any other user data.

Your rights

  • Access. You can request a copy of the data we hold about you.
  • Deletion. You can request deletion of your account and associated data.
  • Disconnect a channel. Disconnecting a channel revokes our access to it. You can disconnect at any time from your dashboard, or by removing Clippyprom from your Google account permissions at myaccount.google.com/permissions.

Data retention

We keep account data, clip links, and metrics for as long as your account is active, and for as long as we need them to settle earnings and meet legal and fraud-prevention obligations. When you delete your account we remove your data, except records we are required to retain for compliance.

Children

Clippyprom is for people aged 18 and over. We do not knowingly collect data from anyone under 18.

How to revoke access

You can revoke our access to a channel in two ways: disconnect the channel from your Clippyprom dashboard, or remove Clippyprom under your Google account permissions. Either action revokes the OAuth tokens we hold for that channel.

Contact

Questions about this policy or your data go to contact@clippyprom.xyz.