Privacy Policy

Updated on September 19, 2026.

This policy describes data processing in Clipper Studio, available at clipper-studio.com, for creating, editing, and publishing clips at the user's request.

Data we use

• Account: identifier, email, and profile information made available by Google to the Supabase authentication service. Clipper does not receive your Google password.
• Projects: videos, extracted audio, links, source video information, transcripts, editorial directions, captions, logos, editing settings, and generated clips.
• YouTube, when connected: authorization credentials, channel identifier and name, plus identifiers of videos published through Clipper.
• Usage and billing: consumption, plan limits, processing reservations, purchase and subscription identifiers, amounts, payment status, and refunds. Full card details are handled by Stripe, not Clipper.
• Technical data: session and authorization cookies, IP address, and request or error logs that may be processed by the infrastructure to deliver and protect the service.

Purposes and legal bases

We use the data needed to authenticate your account, maintain your projects, process requested edits, administer your plan, and process payments. These activities support the service requested by the user. We process records needed for legal obligations, security, and abuse prevention while respecting data subject rights. The optional YouTube connection depends on your authorization, which can be revoked.

Processing and services involved

Project files and operational records are stored on Clipper's backend infrastructure. Audio transcription runs on that backend. To select moments and suggest publishing text, we send the transcribed text, timings, editorial directions, and relevant video information to Google's Gemini API. Credentials for accessing your channel are not included in those analysis requests.

Google's handling of those texts depends on the service mode contracted by Clipper, independently of whether your Clipper plan is free or paid. In the free API tier, Google may use prompts and responses to improve its products, including human review. In the paid tier, Google's terms state that this content is not used to improve its products, while processing for safety and abuse prevention remains. Do not send personal, sensitive, or confidential content while processing uses the free tier. See the Gemini API terms.

We also use Supabase for authentication, Cloudflare for site delivery and traffic, and Stripe for payments. The site loads Google Fonts, which creates requests to that provider. These services may process data outside Brazil according to their contracts and policies. We share data only as needed for these functions and legal obligations.

YouTube connection

Clipper uses YouTube API Services. Read permission is used to identify your channel; upload permission allows publishing the clip you choose. Uploading includes the file, title, description, and visibility setting. See Google's Privacy Policy.

When you disconnect YouTube in Clipper, we remove local credentials and channel identification cache. To also revoke authorization in your Google account, visit third-party app connections. Disconnecting a channel does not delete Clipper projects or videos already uploaded to YouTube; those must be managed on YouTube.

Storage and deletion

Projects remain stored for review and editing; there is currently no automatic expiration for all projects. Channel credentials remain until disconnection or deletion. Payment and security records may need to be retained for legal obligations, fraud prevention, or exercise of rights. Deleting content in Clipper does not delete content published to other services.

Your rights and contact

You may request information about processing, access, correction, and deletion of your data, as well as revoke authorizations, subject to applicable retention obligations. We may need to confirm your identity before responding to a request.

Controller details and contact channel: pending confirmation before this policy is published as final.

Cookies and security

We use necessary cookies to maintain your session and validate authorization returns. The current version of the app does not include behavioral advertising tools. We restrict project access to the associated account and use HTTPS on the public domain. No service is free from risk.

Updates

Changes will be reflected on this page and in the date above. Relevant changes in purpose or processing should be communicated to users and, when required, depend on new authorization.