Privacy Policy - Clipini

Last updated: September 20, 2026

1Collection of Information

Clipini collects the following information:

  • •Basic profile data from Google Sign-In when you choose that login method (name, email, profile picture). Separately, if you connect YouTube to publish, we obtain OAuth tokens and your YouTube channel id/title via the YouTube Data API (see “Google user data” below).
  • •Content of the uploaded or imported video for processing
  • •Performance and usage data
  • •Billing data required for purchases (processed by Freemius)
  • •If you connect Meta (Facebook / Instagram), TikTok, or YouTube for publishing: OAuth tokens and account / Page / channel identifiers needed to publish (see Social publishing and Google user data sections).

2Usage of Information

Clipini uses the information for:

  • •Providing and maintaining our video editing services
  • •Improving your user experience
  • •Understanding our service usage
  • •Communicating with you about your account and usage

3Protection of Information

Clipini protects personal data, OAuth tokens, and project media by combining encryption, access controls, and least-privilege backend access:

  • •Security procedures are in place to protect the confidentiality of your data.
  • •Encryption in transit: traffic between your browser, Clipini, and Google Cloud uses HTTPS/TLS.
  • •Encryption at rest: account data, OAuth credentials, and media objects stored on Google Cloud (Firestore, Cloud Storage) are encrypted at rest by the platform.

4Storage, encryption, and access conditions

This section describes where Clipini stores data, how it is protected, and who can access it (OAuth tokens and project assets).

  • •Where we store data: Clipini runs on Google Cloud Platform. Account identity lives in Firebase Authentication. App records (projects, destinations, jobs) live in Firestore. Video and image assets (uploads, imports, generated clips, thumbnails, promo keyframes / segments / finals) live in Google Cloud Storage buckets operated for Clipini.
  • •OAuth tokens (Meta Pages / Instagram, TikTok, YouTube): access tokens, refresh tokens, and Page tokens are stored in Firestore in a credentials collection tied to your Clipini user and destination. Client apps and browsers cannot read or write these credentials (Firestore security rules deny all client access). Only Clipini backend services (Admin SDK, Cloud Functions, authorized Cloud Run) can load tokens, and only to publish content you request or to revoke / disconnect.
  • •Social destination metadata (Page name, Instagram username, TikTok / YouTube display labels, status): stored in Firestore without exposing raw tokens to the client; readable only by the signed-in owner of that Clipini account.
  • •Project input / output assets: your source videos, generated clips, thumbnails, and promo assets are stored under Clipini Cloud Storage. Playback and download go through authenticated Clipini APIs that issue time-limited signed URLs. They are not offered as a public open directory. Other Clipini users cannot access your project media.
  • •Processing access: to generate clips or promo videos, authorized Clipini backends (Cloud Run, Vertex AI / Gemini on Google Cloud) read the media needed for that job. That processing is to provide the feature you started. We do not sell your project media or OAuth tokens, and we do not use them to train generalized AI/ML models as a separate product.
  • •Human access: Clipini operators may access systems for security, abuse investigation, billing support, or to fulfill a deletion request you send to support@clipini.com. Access is limited to what is needed for that purpose. OAuth tokens are not used for staff browsing of your social accounts.
  • •Retention: project media remains while your account and projects exist and within your storage plan, unless you delete a project or ask us to delete data. OAuth tokens remain only while the social destination stays connected. After disconnect or a validated deletion request, we delete or destroy related credentials and, for account deletion, associated project data we no longer need to keep by law.

5Processors and service providers

We use service providers to operate the service. How we share Google user data with named parties is detailed in the “Google user data” section below:

  • •Freemius, Inc.: payments, invoicing, taxes, and purchase-related transactional emails (https://freemius.com/privacy/).
  • •Google (Firebase Auth, Firestore, Cloud Storage, Cloud Run, Gemini, YouTube Data API): authentication, app data, video processing, and optional YouTube publishing.
  • •Zoho: transactional and support emails (support@clipini.com).
  • •Google Analytics (GA4), when enabled: audience measurement with IP anonymization. We do not send YouTube OAuth tokens or YouTube channel credentials to Analytics.

6Google user data: access, use, storage, and sharing

This section discloses how Clipini accesses, uses, stores, shares, transfers, or discloses Google user data, in line with the Google API Services User Data Policy (including Limited Use).

  • •Access (Google Sign-In) (Firebase): if you sign in with Google, we receive your name, email address, and profile picture to create and manage your Clipini account. This login flow does not request YouTube upload scopes.
  • •Access (YouTube Connect) (separate OAuth client): if you connect YouTube from Account or Share, we request permission to upload videos and to read your channel identity. We receive OAuth access and refresh tokens, plus channel id and title, solely to publish clips or promo videos you choose to share to your YouTube channel.
  • •Use: Google Sign-In data is used for account identity, support, and billing. YouTube API data is used only to list your connected destination and to upload the selected video to YouTube when you tap Publish. We do not use Google user data for advertising, retargeting, credit decisions, or to train generalized AI/ML models.
  • •Storage: account profile data is stored in Firebase Authentication / Firestore. YouTube tokens and channel metadata are stored in our Firestore credentials linked to your Clipini user, on Google Cloud Platform, for as long as the YouTube destination remains connected.
  • •Sharing / transfer / disclosure (with whom): (a) Google LLC / YouTube: we send OAuth tokens and video bytes back to Google’s YouTube Data API to complete your publish request; (b) Google Cloud: infrastructure hosting of the same data; (c) Freemius, Inc.: account email and name derived from Google Sign-In (or email signup) for payment processing; (d) Zoho: account email for transactional and support emails. We do not transfer or disclose YouTube OAuth tokens, refresh tokens, or YouTube channel credentials to Meta, TikTok, Freemius, Zoho, advertising platforms, data brokers, or information resellers.
  • •We do not sell Google user data. We only share or transfer Google user data with the parties named above (Google / YouTube, Google Cloud, Freemius, Zoho), and only to operate Clipini (account, payments, emails, YouTube publishing you request). We do not share Google user data for advertising, data brokerage, or any other purpose not described in this policy.
  • •Limited Use: Clipini’s use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy, including the Limited Use requirements. Clipini does not use Google Workspace APIs; we do not use Google user data to develop, improve, or train generalized / non-personalized AI or ML models.
  • •Retention: we retain Google Sign-In profile data for as long as your Clipini account remains active and needed to provide the service, unless a longer period is required by law. YouTube OAuth tokens and channel metadata are retained only while your YouTube destination stays connected.
  • •Deletion: when you disconnect YouTube in Account, or when retention no longer applies, we delete or destroy the related YouTube credentials and revoke Google access tokens. You may also revoke Clipini in your Google Account settings. You may request deletion of your Clipini account and related data by emailing support@clipini.com.

7Cookies and similar technologies

We use:

  • •Essential cookies (e.g. NEXT_LOCALE language preference, authentication session).
  • •Analytics cookies/scripts (Google Analytics) only when audience measurement is enabled.

8Your Rights

You have the right to:

  • •Access your personal data
  • •Modify or correct your personal data
  • •Delete your account and your data: email support@clipini.com from your Clipini account email, or disconnect social destinations in Account. For Meta Platform Data and TikTok data, see the Social publishing section for step-by-step deletion.
  • •Export your personal data

9Social publishing and platform data (Meta, TikTok, YouTube)

When you connect social destinations (premium) and use Share, Clipini processes platform data from Meta, TikTok, and YouTube only to publish content you select. YouTube / Google details are also in the "Google user data" section.

  • •Meta (Facebook Pages / Instagram Pro) - data we access: after you connect via Facebook Login for Business, we receive Facebook Page id and name, linked Instagram professional account id and username when available, and OAuth access tokens (user and/or Page) needed to publish. We do not use Meta to sign you into Clipini; Clipini login stays Google or email.
  • •Meta - how we use it: we store destinations and credentials to show them in Account and Share, and we call Meta Graph APIs only when you tap Publish, to upload the selected clip or promo as a Reel / Page video with your caption. We do not sell Meta Platform Data, use it for advertising, or train AI models on it.
  • •Meta - sharing: Meta tokens and Page / Instagram identifiers are sent only back to Meta (Facebook / Instagram APIs) to complete your publish or to revoke access. They are not shared with TikTok, Google YouTube OAuth, Freemius, Zoho, or advertisers. Hosting is on Google Cloud (Firestore) for Clipini.
  • •TikTok - data we access: after you connect TikTok, we receive basic profile info allowed by Login Kit (such as display name / avatar fields as provided by TikTok), open_id or equivalent account id, and OAuth access / refresh tokens for Content Posting (upload or direct post, depending on your TikTok app status).
  • •TikTok - how we use it: we store the destination and tokens to publish or send to your TikTok inbox the video you choose in Share. We do not sell TikTok user data, use it for advertising, or share it with Meta or Google for their own purposes.
  • •TikTok - sharing: TikTok tokens and profile identifiers are sent only back to TikTok APIs to publish or revoke. They are not shared with Meta, Freemius, Zoho, or advertisers. Hosting is on Google Cloud for Clipini.
  • •YouTube: covered in the "Google user data" section (separate OAuth client from Clipini Google Sign-In).
  • •Retention: Meta and TikTok credentials and destination metadata are kept only while the destination stays connected in your Clipini Account, unless a longer period is required by law.
  • •How to request deletion of Meta / TikTok platform data: (1) Open Clipini Account, Social networks, and tap Disconnect for that destination (we delete local credentials and revoke tokens when possible). (2) Or email support@clipini.com with your Clipini account email and ask us to delete Meta and/or TikTok platform data; we will process the request and confirm. (3) You can also remove Clipini from your Facebook / Instagram or TikTok connected apps; Meta may call our data-deletion callback, and we record and process that request.

10Contact and Support

For any questions regarding this privacy policy, please contact us at:

support@clipini.com