Overview
Clyps processes the information needed to create an account, organize a workspace, turn videos into editable clips, render exports, and run the service. We do not sell personal information or use your projects for cross-site advertising.
A source video is private unless you choose to publish an output. Team members can access workspace content according to their assigned role.
Data Clyps handles
Account and security
Your name, email address, profile image, provider account ID, authentication tokens, session records, IP address, user agent, and team membership. You can sign in with email, Google, or Apple. Native Apple sign-in uses the system account flow.
Videos and project content
Videos you upload, audio, proxies, thumbnails, transcripts, word timing, speaker labels, clip ranges, captions, templates, edits, brand assets, exports, and project metadata.
Billing
Plan, subscription, customer, checkout, and entitlement records. Stripe handles payment details. Clyps does not store complete payment-card numbers.
Service activity
Processing status, upload and render events, feature actions, errors, request logs, and security signals. Clyps records how candidate clips are shown, opened, adjusted, dismissed, exported, or published so the editing workflow can improve.
Web sessions
Clyps uses secure session cookies to keep you signed in. The current web app does not load an advertising or cross-site tracking SDK.
Information you publish
If you choose to publish, the selected clip, title, caption, creator profile, topics, and source attribution can become public. Private and unlisted projects do not become public posts automatically.
How we use data
- Provide authentication, workspaces, editing, processing, and exports.
- Save project changes and synchronize the cloud features you choose.
- Operate subscriptions, usage limits, and team permissions.
- Send service notifications that match your settings.
- Prevent abuse, investigate failures, and protect Clyps accounts.
- Meet legal obligations and enforce our agreements.
Cloud media processing can analyze audio, transcripts, speaker turns, and video frames to produce captions, framing data, and highlight suggestions. It does not make your source public.
Local processing on Mac
The Mac app has a local Captions only workflow. When the app labels a project as local, it uses the on-device transcription engine you select and local rendering. The Clyps multilingual pack is downloaded only after you choose it. The source video and generated transcript are not uploaded by that workflow.
Signing in, opening a cloud project, synchronizing metadata, or choosing a cloud export connects to Clyps services. Local project files remain on the Mac until you remove them there. Deleting a cloud account does not delete local files from your device.
Service providers
Clyps uses the following providers to run the product:
- Cloudflare
- Website and API delivery, security checks, service logs, media storage in R2, Workers AI, and cloud media processing.
- PlanetScale
- Hosted PostgreSQL for accounts, workspaces, project records, transcripts, and service state. Binary media is not stored in PostgreSQL.
- Google and Apple
- Account authentication when you choose either provider. Email sign-in is handled by Clyps authentication services.
- Stripe
- Checkout, subscription management, billing portal access, and payment processing.
These providers may process data in countries where they operate. Their own privacy notices also apply to information they receive directly from you.
Your controls
- Edit your profile, project content, and notification settings.
- Choose whether a social post is private, unlisted, or public.
- Remove content you own, subject to team permissions.
- Use Account settings to request deletion of your cloud account.
An accepted deletion request is queued. It is not complete until Clyps reports completion. If the service says deletion is unavailable, no deletion has started. Team owners must transfer ownership or delete their team first. Shared team history may remain for the other members.
If you cannot access your account, use the support contact shown on the Clyps App Store listing or the distribution channel where you received the app.
Retention and security
Clyps keeps cloud data while your account or workspace needs it and as needed to operate, secure, and document the service. Retention varies by data type and provider. We do not promise a fixed deletion period in this policy. Backups, security logs, billing records, and records required by law may remain after other account data is removed.
Clyps uses tenant authorization, encrypted connections, secure web session cookies, Keychain storage in native apps, private media storage, and time-limited media access. No system is immune to risk, so report suspected account misuse through the available support channel.
We may update this policy as Clyps changes. The date at the top identifies the current version.