Privacy Policy

This Privacy Policy explains how assistbda ltd ("we", "us", "Clyp") collects, uses, and shares personal data when you use Clyp — a service that turns your videos into short clips, writes post copy for them, and (optionally) publishes them to social accounts you connect. assistbda ltd is the data controller. We are registered in England & Wales and you can contact us about privacy at [email protected].

1. Personal data we collect

• Account & identity. When you sign up we use Clerk to manage your account; we hold your account identifier and email address.
• Payment data. If you buy credits or a subscription, payment is processed by Stripe. We receive and store your billing email, a Stripe customer reference, and your plan/credit balance. We do not store your card details.
• Content you provide. Videos you upload or YouTube links you submit, any brief or instructions you type, and the transcripts, clips, thumbnails and post copy we generate from them.
• Connected social accounts. If you connect a TikTok, Instagram or YouTube account, we store which platform, your account handle/ID, and the access token we need to publish on your instruction. Tokens are encrypted at rest.
• Publishing data. The caption text and the clip you choose to publish, and a reference/link to the resulting post.
• Usage & analytics. Product-usage events (e.g. sign-up, clip generation, purchases) tied to your account identifier, via PostHog. With your consent, browser Sentry monitors technical errors and performance. Separately, when you use Clyp, our API and video-processing services always send scrubbed operational error data to Sentry so we can keep the service reliable. Neither Sentry path is configured to receive video content, transcripts, prompts, authentication data, or request bodies.
• Communications. Transactional emails we send you (e.g. job complete, payment confirmations).
• Affiliate waitlist. If you join the affiliate waitlist we store your name, email address, and (if you give it) Instagram handle, so we can contact you when the program opens.

2. How and why we use it, and our legal bases

• To provide the service — process your videos, generate clips and post copy, and publish to accounts you connect. Legal basis: performance of our contract with you.
• Billing and fraud prevention. Contract; and our legitimate interests in securing payments.
• Analytics and improving Clyp. Legitimate interests (and, where required, your consent for non-essential cookies).
• Security, reliability and abuse prevention. This includes scrubbed server-side operational error monitoring. Legitimate interests.
• Publishing to your social accounts. Only on your instruction, using the accounts you connect. Contract / your consent.
• Legal compliance. Compliance with a legal obligation.
• Affiliate waitlist. To email you about the affiliate program you asked to join. Your request / legitimate interests.

3. AI processing of your content

To find the best moments in your video and to write titles, hooks and hashtags, we send the transcript of your video to an AI provider — currently xAI (Grok). Transcription itself is performed with a self-run speech-to-text model (Whisper), which may run on our compute provider (Modal). We may change the AI provider; we will update this policy if the default provider changes. We do not use your content to train third-party AI models beyond what is needed to return the result to you.

4. Who we share data with (sub-processors)

We share personal data with the following service providers, only as needed to run Clyp:

We do not sell your personal data.

5. Connected social accounts & publishing

Connecting an account is optional. When you connect one, we only ever publish your own content, to your own account, on your instruction, with the caption you choose. You can disconnect an account at any time in Clyp, and you can revoke Clyp's access directly from the platform.

Google / YouTube

Clyp uses YouTube API Services to upload the videos you choose to your channel. By connecting your YouTube account you agree to the YouTube Terms of Service. Clyp's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Userequirements, and Google's handling of your data is described in the Google Privacy Policy. We access your YouTube account solely to upload the videos you choose; we do not use YouTube data for any other purpose, and we do not transfer or sell it. You can revoke access at Google Account → Third-party access.

TikTok

We access your basic TikTok profile (to show which account is connected) and use the Content Posting API to publish clips you choose to your account. Revoke access in your TikTok settings under Security & permissions → Manage app permissions.

Instagram / Meta

We connect Instagram via Facebook Login to publish Reels you choose to your account. Revoke access in your Facebook/Instagram settings under Apps and websites.

6. MCP connector

Clyp publishes an MCP (Model Context Protocol) server that lets AI agents — such as Claude Code, Claude Desktop, and Cursor — call Clyp tools on your behalf. The connector is authenticated with a Clyp API key, which you create in your account under Profile → API Keys.

The API key carries your full account authority, including spending credits. Treat it as a secret: keep it out of source control and chat logs, and store it only in your MCP client's configuration (not in prompts or chat history).

When you use the MCP connector, the following data flows apply:

• The MCP server runs locally on your machine. It never receives the content of your conversations with the AI agent — it receives only the structured tool calls the agent makes.
• Tool calls that involve video content (for example clyp_create_clips) pass only a YouTube URL or a local file path; the underlying video processing is the same as the web app and covered by §§ 1–4 of this policy.
• No additional personal data is collected by the connector beyond what the equivalent web-app actions would collect.
• If you revoke or delete your API key in Clyp (Profile → API Keys), the connector immediately loses access to your account.

The MCP connector is optional. Using it does not change the data you have already consented to Clyp processing under this policy; it provides an alternative interface to the same backend.

7. International transfers

Some of our providers are located outside the UK/EEA (for example in the United States). Where we transfer personal data internationally, we rely on appropriate safeguards such as the UK International Data Transfer Agreement / Addendum, the EU Standard Contractual Clauses, or an adequacy decision, as applicable.

8. Retention

We keep your account and billing data for as long as you have an account, and as needed for legal, tax and accounting purposes. Videos, clips and related files are retained so that re-edits and re-exports keep working, and are not automatically deleted after processing; they remain until you delete the job or your account. You can delete individual jobs in the app at any time. If you close your account, we delete or anonymise your personal data within 30 days, except where we must retain it by law.

9. Your rights

Under UK GDPR you have the right to access, rectify, erase, restrict, or object to our processing of your personal data, and the right to data portability. To exercise any of these, email [email protected]. You also have the right to complain to the UK Information Commissioner's Office (ICO) at ico.org.uk.

10. Deleting your data

You can request deletion of your data at any time — see our Data Deletion page, or email [email protected].

11. Cookies

We use strictly necessary cookies to keep you signed in (via Clerk). We also use analytics and monitoring cookies (via PostHog and Sentry) to understand product quality; where required by law we ask for your consent for non-essential cookies. You can control cookies in your browser settings.

12. Children

Clyp is not intended for anyone under 18, and we do not knowingly collect data from them.

13. Security

Data is encrypted in transit. Access to stored media is gated by short-lived signed links, and any stored social-account tokens are encrypted at rest. No system is perfectly secure, but we take reasonable technical and organisational measures to protect your data.

14. Changes to this policy

We may update this policy from time to time. We will post the new version here and update the "last updated" date; material changes affecting how we use your data will be notified to you.

15. Contact

assistbda ltd, registered in England & Wales. Privacy enquiries: [email protected].