ClipperX
CLIPPERX / DATA PRIVACY LAYER
21 PRIVACY SECTIONS
LEGAL PRIVACY DISCLOSURELAST UPDATED: OCTOBER 19, 2026·SECURITY: ENCRYPTED TRANSIT

Privacy Policy.

ClipperX is built for performance, discretion, and accountable infrastructure. This Policy explains how we process authentication data, subscriptions, extraction requests, queue telemetry, and security signals across the platform.

✓ Ephemeral Media Processing✓ Account Access Controls✓ No Card Data Stored
SECTION 01

Scope

This Privacy Policy explains how ClipperX collects, uses, stores, shares, and protects information when you access our website, APIs, AI video clipping services, subscription plans, and support channels. ClipperX is operated by Synapvo Technologies at getclipperx.com and provides account-based video clipping, captions, scheduling and connected-account features.

SECTION 02

Who We Are

For the purposes of privacy law, ClipperX is the controller, or equivalent decision-maker, for account, billing, security, and service-operations data that we determine how to process. Certain infrastructure vendors act as processors or sub-processors on our behalf.

SECTION 03

Compliance Position

Your privacy rights depend on where you live and the laws that apply to your use of the service. This policy describes our processing; it is not a claim of independent certification. Contact the privacy address below to request access, correction or deletion of your information.

SECTION 04

Data We Process

We may process account and identity data, authentication session data, subscription and payment records, IP and device signals, logs, queue metadata, rate-limit state, extraction job state, support communications, and user-submitted media URLs, format requests, and filenames. We do not intentionally request sensitive personal data and ask that you avoid submitting unnecessary sensitive information.

SECTION 05

Supabase Authentication

We use Supabase for authentication, session management, token issuance, and related account services. Supabase may process login credentials, tokens, user identifiers, and security metadata on our behalf. You remain responsible for maintaining credential confidentiality.

SECTION 06

Payment Processing

We use authorized payment processors for subscription billing, payment verification, order handling, and payment webhooks. ClipperX does not intentionally store full card numbers on its own application servers. Payment data is processed subject to the processor's legal and regulatory obligations.

SECTION 07

Plan Tiers

ClipperX may offer Free, Pro, and Premium subscriptions. Free plans have lower limits and lower operational priority. Pro plans provide expanded clipping entitlements and elevated limits. Premium plans provide the highest consumer-tier entitlement set and advanced access where offered. We may also offer API or enterprise arrangements separately.

SECTION 08

Why We Process Data

We process data to authenticate users, provision subscriptions, authorize downloads, operate AI workers, route and monitor queue activity, detect abuse, enforce rate limits, maintain secure logs, deliver media artifacts, provide fallback delivery where necessary, and improve reliability and security.

SECTION 09

Render and Queue Operations

ClipperX processes uploaded media through a bounded render queue. We process operational telemetry concerning queue behavior, render health, and delivery success.

SECTION 10

API Rate Limiting and Abuse Controls

We apply rate limiting, request validation, entitlement checks, and security heuristics to website, API, and worker traffic. We may log account identifiers, IP metadata, request timestamps, provider targets, quota state, and error patterns for fraud prevention, operational visibility, and contractual enforcement.

SECTION 12

Sharing and Transfers

We share data only where reasonably necessary with infrastructure, identity, payment, hosting, delivery, monitoring, and network partners. Because our service uses globally distributed infrastructure, your data may be processed in India and other jurisdictions where our providers operate, subject to lawful safeguards and contractual protections where required.

SECTION 13

Retention and Security

We retain personal data only for as long as reasonably necessary for account administration, legal compliance, fraud prevention, dispute resolution, subscription records, and service integrity. Short-lived media artifacts and worker outputs are intended to remain ephemeral and may be deleted automatically after delivery or expiry. We implement reasonable technical and organizational safeguards, but no internet service can guarantee absolute security.

SECTION 14

Your Rights

Depending on your jurisdiction, you may have rights to access, correct, update, erase, restrict, object to, or port your personal data, withdraw consent where relevant, and seek grievance redressal. Under the DPDP Act, this may include consent withdrawal and nomination-related rights. Under GDPR, this may include objection, restriction, portability, and complaint to a supervisory authority.

SECTION 15

Children and Contact

ClipperX is not directed to children and should not be used by minors where prohibited by law or by relevant platform rules. Privacy, rights, and grievance requests should be directed through ClipperX support or the designated contact channel published by the service.

SECTION 16

Google Sign-In Data

When you choose Sign in with Google, Google provides your account identifier, name, email address and profile picture to Supabase so ClipperX can create or recognize your account and maintain your sign-in session. Google Sign-In is separate from connecting a YouTube channel. Signing in does not itself authorize ClipperX to upload a video. The sign-in feature does not request access to Gmail messages, Google Drive files or Google Calendar.

SECTION 17

YouTube Connections, Publishing and Analytics

If you separately connect YouTube, ClipperX requests permission to upload videos and read your YouTube channel information. We access the connected channel identifier, name and image, and video information needed for publication status and available analytics. Additional YouTube Analytics permission is requested only when that feature is selected. Access and refresh tokens permit authorized API calls. A calendar reminder does not upload or publish content. If publishing is available and you explicitly choose it, the selected clip and its title, description and publication settings are sent to YouTube. We do not request your Google password.

SECTION 18

How Google and YouTube Data Is Used and Shared

Google and YouTube information is used for the sign-in, channel connection, publishing and analytics features you authorize. ClipperX's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. ClipperX does not sell this information, use it for personalized advertising, or use it to train generalized AI or machine-learning models. Google API information is not provided to data brokers. Identity and connection records are processed through Supabase, our application servers and necessary infrastructure providers to operate these features. User-requested publication sends the selected content to Google or YouTube. Data may also be disclosed when required by applicable law.

SECTION 19

Uploaded Media and AI Processing Providers

Media that you upload for clipping, its audio and generated transcripts may be sent to configured transcription and text-generation providers, including Groq and Microsoft Azure AI, to produce the clips and draft metadata you request. This processing is distinct from Google sign-in and YouTube channel access. OAuth access and refresh tokens are not included in these AI requests. Supabase provides account and database services; Cloudflare R2 stores media objects; Oracle-hosted application workers coordinate processing. Only submit media you are authorized to process.

SECTION 20

Google Data Storage, Security and Retention

ClipperX stores connected-account access and refresh tokens encrypted on the server and excludes them from browser-facing account responses. Ownership checks restrict access to clips, history and connected accounts. Network requests to Google use HTTPS. Tokens are retained while the connection remains active so requested jobs and token refresh can work. Disconnecting clears the active stored connection credentials. Channel identifiers, connection status and publication history can remain as account or operational records; deletion of those records can be requested through the privacy contact. Analytics reports are temporarily cached for five minutes. Expiry of a media download link does not mean a video already published on YouTube is deleted.

SECTION 21

Revoke Access, Delete Data and Contact Us

You can disconnect a channel from the connected-account controls in ClipperX and revoke Google access from your Google Account permissions page. If provider-side revocation cannot be confirmed, ClipperX reports that you must revoke access with Google directly. For deletion of your account, retained Google or YouTube records, uploaded media or generated clips, email [email protected] from the account email and identify the records to remove. We verify account ownership before processing deletion requests and retain records only where needed for the service or applicable legal and security obligations. Disconnecting ClipperX does not delete videos already published to YouTube; manage those in YouTube Studio.

PRIVACY CONTACT & GRIEVANCES

Have Questions or Need to Exercise Your Privacy Rights?

Privacy, data access, erasure, or grievance requests should be directed to our official support team. We respond to all verified inquiries promptly.