Privacy Policy

Clipwise is a video clipping service that turns long-form video into short-form clips. In data-protection terms we are the data controller for your account and content, and the processors listed in section 4 act on our instructions.

Questions, requests, or complaints: support@use-clip-wise.com .

Account data. Your email address and authentication identifiers. Sign-in is handled by Clerk; we store the account identifier they issue, never your password.

Content you submit. Videos you upload, video URLs you paste, and any prompts or notes you type. Processing these produces transcripts, detected moments, rendered clips, captions, scripts, voiceovers and generated images, all stored against your account.

Payment data. For crypto payments we store the deposit address shown to you, the amount, and the transaction hash you submit — all of which are already public on the blockchain. For card payments the processor handles your card details; we never see or store a card number.

Connected accounts. If you connect YouTube, TikTok or Instagram to publish, we store the access and refresh tokens those platforms issue. They are encrypted at rest and used only to publish what you ask us to publish.

Operational data. Job status, timing, credit ledger entries, error messages, and API keys you generate.

To provide the service you asked for (performing our contract with you): downloading or receiving your video, transcribing it, detecting moments, rendering clips, and publishing where you direct.

To bill you and prevent abuse (our legitimate interests, and a legal obligation for financial records): credit accounting, rate limiting, and per-plan job caps.

To keep the service working: diagnosing failures from error messages and job history. We do not profile you, sell your data, or use your content to train models.

Running the pipeline necessarily sends parts of your content to specialised providers. Which ones apply depends on the features you use and how this instance is configured:

• Groq — speech-to-text. Receives the audio of your video.
• Anthropic — moment detection, scripts, subtitle translation, publish copy. Receives your transcript text, not your video.
• Clerk — accounts and sign-in.
• Stripe and/or Binance Pay — payments, when card checkout is enabled.
• Public blockchain explorers (TronScan, BscScan) — to confirm a USDT payment. Receives a transaction hash, not your identity.
• YouTube, TikTok, Meta/Instagram — only when you connect an account and ask us to publish. They receive the clip and the title and description you approve.
• ElevenLabs (voiceover) and OpenAI or Stability AI (image generation) — receive only the text or prompt you submit for those features.

Some of these operate outside your country. Where that involves an international transfer, it takes place under the provider's standard contractual clauses or equivalent safeguards.

Source video and intermediate files are temporary. The working directory for a job — the downloaded source, extracted audio, and partial renders — is deleted after the job completes, and a sweep reclaims anything left behind by a crash (default: within six hours).

Your finished work is kept until you delete it. Clips, scripts, voiceovers and images stay in your library so you can come back to them. Deleting an item removes both the record and the underlying file from storage.

Account, credit ledger and payment records are retained while your account is open, and afterwards only as long as tax and accounting rules require.

You can access, correct, export or delete your data, object to processing, or withdraw consent at any time. Most of this is self-service: delete individual items from your library, and disconnect any social account from the Connections page, which revokes the stored token.

For anything else — a full export, or deletion of your entire account — email support@use-clip-wise.com and we will respond within 30 days. If you are in the UK, EU or EEA you also have the right to complain to your local data protection authority.

We use a small number of strictly necessary cookies to keep you signed in and to keep the app secure. These cannot be switched off without breaking sign-in, and under the ePrivacy rules they do not require consent.

Anything beyond that — analytics — is off until you accept it. Decline and no analytics script is loaded at all. Your choice is stored in your own browser and you can change it any time from the link in the footer.

Traffic is encrypted in transit with HTTPS. Publishing tokens are encrypted at rest with a key held outside the database, and API keys are stored as hashes, so a database copy alone does not reveal them. Access to production is limited to the operator.

No system is perfectly secure. If we discover a breach affecting your personal data, we will notify you and the relevant authority as required by law.

The service is not directed at children under 16, and we do not knowingly collect their data. If you believe a child has given us personal data, contact us and we will delete it.

If this policy changes materially we will update the date at the top and, where the change affects you, tell you in the app before it takes effect.

See also our Terms of Service.