Privacy Policy

Updated on November 5, 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.

Approximate country and currency

We may use the approximate country associated with your IP address, supplied by Cloudflare, to display a currency supported for your region. We do not request GPS access or collect coordinates for this purpose. VPNs, proxies or travel may affect this estimate, which is not proof of residence. If the country cannot be reliably identified or its currency is unsupported, we use US dollars (USD).

When selecting a deposit amount, we display its currency and applicable minimum. Reference conversions are identified as estimates; the final amount must be confirmed before any payment. We may retain the approximate country, currency, amount, conversion reference, date and displayed confirmation version, linked to the account, to record the selection and handle support requests. We do not store IP addresses or coordinates in these selection records. Infrastructure logs remain subject to the other provisions of this policy. This confirmation does not charge you or authorize recurring payments. Our server may consult European Central Bank reference rates without sending account data to that service.

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, uploaded or extracted audio files, links, source video information, transcripts, conversations and proposed text revisions, editorial directions, captions, logos, music, voice samples supplied for narration, editing settings, and generated clips.
• YouTube, when connected: authorization credentials, channel identifier and name, plus identifiers of videos published through Clipper.
• Usage and billing: usage, token counts, maximum monthly spend, prepaid balance, processing reservations, transaction identifiers, amounts, payment status, and refunds. When automatic usage-based billing is authorized, we also record that authorization and the version of the conditions accepted. Historical payment records are retained for the purposes and periods described in this policy. 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. To transcribe, we may send audio to Google's Gemini API; where applicable, transcription may also run on Clipper's infrastructure. In Audio to text, audio is sent to Google for transcription. The original transcript, proposed changes, and conversation history are saved in the project. We also send text, timings, instructions, and conversation context to the Gemini API to analyze content, select moments, answer requests, and suggest revisions or publishing text. Credentials for accessing your channel are not included in these requests.

Google's handling of those texts depends on the service mode contracted by Clipper, independently of your billing arrangement with Clipper. 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.

Music creation

When you request music, we send Google your description and instrumental setting. We save the description, generated music, any lyrics, and generation and billing records in your private account project. Processing may continue after you close the page. You may select a generated song as background music in the editor. Account credentials are not included in these requests.

Image creation

We send Google your descriptions, reference images and, for edits, the previous image needed to fulfill your request. References, generated images and conversations are saved in your private account project. In economy mode, the task is submitted to the batch-processing API and may continue after you close the page. When you enable visual search, queries related to your request are also sent to Google; search references are displayed with the result. We do not include your account credentials in those queries. We record model, resolution, processing mode and usage to calculate and audit charges.

Video generation

When you request a video, we send Google your description, generation settings and reference image, if attached. Processing may continue after you close the page. The interaction is stored by Google under its API retention policy, allowing us to retrieve the same generation after an interruption. We save the description, reference, generated video and history in your private account project, along with technical, usage and balance-reservation records needed for recovery and billing. The backend retrieves the video and provides authenticated access; provider credentials are not sent to your browser.

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.

AI voices, narration and dubbing

When you request a voice identity or AI narration and dubbing, we send Google APIs the voice description, requested text and delivery settings needed to generate previews or audio. Identities and previews are stored in your account's voice library; texts, subtitles and generated audio are stored in their private projects together with usage records. Clipper does not use these materials to train its own models or make them available to other accounts. Use only voices and materials you own or are authorized to use.

AI music

When you request music, we send your description and generation settings to Google APIs. The generated audio, prompt and usage records are stored in your private account project. Sharing or publishing depends on actions you request.

Storage and deletion

Projects remain stored for review and editing according to plan rules. Storage follows the current plan quota. Archived projects are not automatically deleted based on time and still use storage. 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.

Support

When you use support, your subject, category, messages and replies are stored on Clipper infrastructure and can be reviewed by authorized staff to handle your request. Recent conversation history is sent to Google's Gemini API to provide guidance about policies and the application. Do not send passwords, access codes, full card numbers or other sensitive information. The assistant is automated and does not decide refunds; payment and refund requests are reviewed by staff. Support records may be retained while needed to handle requests and exercise rights. You can request human review or exercise your rights through this same page.

When you submit feedback through Settings, we store your description and any screenshot you choose to upload, linked to your account, for review by authorized support staff. The screenshot is optional, has technical metadata removed, and is not sent to the AI assistant. Do not include confidential information in the description or image. These records follow the support retention rules above.

Contact channel: Clipper Studio support. Controller identification details are still pending confirmation.

Refund review requests may generate internal email notifications containing account identification, the message and payment information needed for review. Staff compose replies in the support area and send them to the registered email address. Our email provider (UOL) processes the data needed to deliver these messages; refund review and execution are restricted to authorized staff.

Optional Discord announcements

You can separately authorize announcements of your connected YouTube channel and public videos uploaded through Clipper in the official Discord community. Both options start disabled. With your permission, we share the public name, handle, profile image or thumbnail, and channel or video links. Private, unlisted, and still-processing videos are not announced. We record preferences and delivery history to prevent duplicates and allow moderation. Turning off announcements prevents new posts but does not remove messages already published on Discord. This permission is independent of your Google connection and can be changed in the YouTube window in the workspace.

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.

TikTok connection

TikTok connection and posting are unavailable while the integration awaits approval. Once enabled, the feature will require your authorization. In that case, authorization tokens will be stored on the backend to query profile and publishing options, refresh access, and send videos you explicitly confirm. TikTok will receive the video, post caption, visibility, interaction settings, and commercial disclosures you choose. We will store the submission identifier and status. A temporary video copy will be accessible through a secret URL for up to 24 hours for transfer; expired copies will be removed on subsequent uploads. You will be able to disconnect in Clipper to revoke authorization or through TikTok settings. Disconnecting does not delete previous posts. See the TikTok Privacy Policy.

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.