Legal

ClipEmber Privacy Policy

Effective October 19, 2026. This policy covers the ClipEmber web application at clipember.com and the ClipEmber API. See also our Terms of Service.

1. Who we are

ClipEmber is a video repurposing service: it turns a long video into short vertical clips with burned-in captions, and can publish those clips to social accounts you connect. ClipEmber is operated by ClipEmber from Ukraine (“ClipEmber”, “we”, “us”). We are the data controller for the data described here. For any privacy question or request, write to hello@clipember.com — we answer from a human address, not a no-reply.

ClipEmber is an independent product. It is not affiliated with, endorsed by, or sponsored by TikTok, YouTube/Google, or Instagram/Meta.

2. What data ClipEmber collects

CategoryWhat exactly
AccountEmail address and display name. If you sign in with Google, we receive only your email address and name from Google — never your Google password.
Your contentVideos you upload, video URLs you paste, the source video files ClipEmber downloads for you, the transcript (including word-level timings), the clips we render, thumbnails, your editor settings and caption edits, and any B-roll or music selections you add.
Product activityProjects and their processing status, credit ledger entries (why a credit was spent or granted), schedule entries, clip thumbs up/down, share links you create and their view counts, API keys you generate, and rate-limit counters.
Connected accountsFor each social account you connect: the platform, your handle or channel name, avatar URL, the platform account id, the granted scopes, and the OAuth access and refresh tokens needed to publish on your behalf. Details in section 3.
PaymentsIf you buy credits or a plan, Stripe processes the payment on its own checkout page. ClipEmber stores the Stripe session/invoice identifier, the amount, and what it granted. ClipEmber never sees or stores your full card number.
TechnicalServer logs from our hosting providers (IP address, user agent, timestamps, requested paths) used for security and debugging. ClipEmber runs no advertising or cross-site tracking pixels.

3. Data from connected platforms (TikTok, YouTube, Instagram)

Connecting a social account is always optional — ClipEmber works fully without it (you can just download your clips). When you do connect an account, you go through that platform’s own OAuth consent screen and see the permissions before you approve them. Here is exactly what ClipEmber requests and what it deliberately does not touch:

TikTok — scopes: user.info.basic, video.upload, video.publish, video.list

  • user.info.basic — read only your TikTok open id, display name and avatar image URL, so the Connected accounts and Calendar screens can show you which account a clip will go to before you confirm it.
  • video.upload — upload one rendered clip that you selected to your own TikTok account when you have not chosen its audience on the Post to TikTok screen. TikTok then sends a notification to your Inbox, you tap it in the TikTok app, and the editing and posting happen there — on this path we cannot publish it for you, so the final publishing decision stays inside TikTok.
  • video.publish — post a clip straight to your profile (TikTok calls this Direct Post) — but only a clip for which you yourself, on the Post to TikTok screen or the TikTok queue screen, wrote the caption and picked who can see it. There is no saved default and nothing is inherited, so a new clip always arrives without a choice and waits for you to make one. If TikTok ever refuses a direct post, we upload the clip to your Inbox instead, so it is never lost and you finish the post yourself in the TikTok app.
  • video.list — read back the public view, like, comment and share counts of the clips you published through us, so the app can show you how each clip performed and improve which moments it picks next time.
  • ClipEmber does not read your direct messages, followers list, private analytics or advertising data, or post anything to your TikTok profile that you did not choose to publish yourself — a clip goes straight to your profile only when you wrote its caption and picked its audience on the Post to TikTok screen; everything else arrives as a notification in your Inbox for you to finish inside the TikTok app.

YouTube — scopes: youtube.upload, youtube.readonly

  • youtube.readonly — read your channel id and channel title, so you can see which channel is connected.
  • youtube.upload — upload the clips you chose to publish to that channel.
  • ClipEmber does not read your watch history, subscriptions, comments or channel analytics.

Instagram — scopes: instagram_business_basic, instagram_business_content_publish, instagram_business_manage_insights (Instagram Login) — or instagram_basic, instagram_content_publish, pages_show_list, pages_read_engagement, business_management (Facebook Login)

  • instagram_business_basic / instagram_basic + pages_show_list — read your Instagram professional account id and username (and the linked Facebook Page id) to show which account is connected.
  • instagram_business_content_publish / instagram_content_publish — publish the Reels you chose to publish to that account.
  • instagram_business_manage_insights — read back the views, likes and comments of the Reels we published for you — nothing else. Two things use it: the Analytics screen, so you can see how a clip did, and the scoring model, which compares what it picked against what people actually watched and gets better at picking next time. We read only media we published through ClipEmber.
  • ClipEmber does not read your feed, followers, direct messages, or the insights of posts you made outside ClipEmber.

Publishing is user-initiated. A clip leaves ClipEmber for a platform only when you press Post on that clip, or when it reaches a time slot in a schedule or automation rule that you created yourself and can pause or delete at any time. ClipEmber does not post promotional content of its own to your accounts, and does not use your connected accounts to follow, like, comment or message anyone.

We keep platform tokens only to perform these publish actions and to refresh expiring tokens. Tokens are never shared with other ClipEmber users, sold, or used to build profiles or datasets about you or your audience.

4. Why ClipEmber uses your data

ClipEmber does not sell your personal data, does not share it for cross-context behavioural advertising, and does not use your videos, transcripts or clips to train machine-learning models — ours or anyone else’s.

5. Where processing happens, and AI

Cutting, rendering and storage run on ClipEmber’s own worker and storage providers. Two steps use external AI providers, each receiving only what that step needs. Speech-to-text runs on Groq: ClipEmber sends the audio track of your video, compressed and without the picture, and gets the transcript back; if Groq is unavailable, a Whisper model on our own worker does it instead. Picking and describing clips uses Google’s Gemini API: it receives the transcript text, short low-resolution previews of candidate moments and a few still frames, and returns scores, titles, hashtags, translations and layout hints. Both are listed in section 6. If we add another provider that sees your content, we will name it in this policy before switching it on.

AI-generated output (ClipEmber clip scores, suggested titles, hashtags, summaries and translations) is a suggestion, not editorial fact. You stay responsible for what you publish — see the Terms of Service.

6. Who we share data with

ClipEmber shares data only with the processors below, only for the purpose listed, and only the data that purpose needs. There are no data brokers, ad networks or analytics resellers in this list.

ProviderPurposeData involved
Vercel Inc. (USA)Web application hostingRequests to clipember.com, IP addresses in server logs
Supabase, Inc. (USA)Managed PostgreSQL databaseAccount records, project metadata, transcripts, schedule, connection tokens
Cloudflare, Inc. (USA)R2 object storage, DNS, email routing for hello@Uploaded/downloaded source videos, rendered clips, thumbnails; email you send us
Fly.io, Inc. (USA)Background worker that downloads source videos and runs scheduled jobsSource videos while they are fetched; job and schedule records
OVH US LLC (USA)Background worker that transcribes, cuts and rendersYour media and transcripts during processing
Groq, Inc. (USA)Speech-to-text for your videosThe audio track of your video, compressed and without the picture; the transcript it returns
Stripe, Inc. (USA)Payment processing (only if you buy credits or a plan)Billing details you enter on Stripe’s own checkout; we receive only a session id and result
Google LLCSign in with Google; YouTube Data API (only if you connect YouTube); Gemini API for picking and describing clipsYour email and name at sign-in; upload of clips you choose to publish; transcript text, short low-resolution previews and a few still frames of your video
TikTok (ByteDance Ltd. and affiliates)TikTok Login Kit and Content Posting API (Direct Post and Inbox upload) — only if you connect TikTokYour TikTok open id, display name, avatar; clips you send to your TikTok account for posting
Meta Platforms, Inc.Instagram Graph API (only if you connect Instagram)Your Instagram business account id and username; clips you choose to publish
Resend (USA)Sending account and notification emailsYour email address and the content of emails we send you
Amplitude, Inc. (USA)Product analyticsPages you open and actions you take in the app, linked to a pseudonymous id; sampled session recordings with form inputs masked

We may also disclose data if the law requires it (for example a valid legal request), to protect the rights and safety of users or the public, or as part of a merger or acquisition — in which case we will say so here before your data moves.

If you create a public share link for a clip, anyone with that link can watch that clip until you revoke the link. That is the one case where ClipEmber exposes your content outside your account, and only because you asked it to.

7. Cookies

ClipEmber uses strictly necessary cookies only: one session cookie that keeps you signed in, and short-lived cookies during a social-account connect flow (a CSRF state value and your user id) that are deleted as soon as the connection completes. There are no advertising, profiling or third-party analytics cookies, which is why ClipEmber shows no cookie banner.

8. How long ClipEmber keeps data

9. Disconnecting a platform and revoking access

You can disconnect any connected account at any time in ClipEmber → Connections → Disconnect. ClipEmber then asks the platform to revoke the token and deletes the stored access token, refresh token and connection record from our database. Scheduled posts that depended on that connection stop.

You can also revoke ClipEmber’s access from the platform’s own settings, independently of us:

10. Deleting your account and data

Delete your account in ClipEmber → Settings → Account, or email hello@clipember.com from your account address with the subject “Delete my ClipEmber account”. Deletion closes access immediately; we then erase your account record, projects, media, transcripts, clips, schedule and platform tokens within 30 days, except records we must keep by law (payment records) which are retained in isolation for that purpose only.

Want only your data from one platform gone? Disconnecting that platform (section 9) removes its tokens and connection record without touching the rest of your account.

11. Your privacy rights

Wherever you live, you can ask ClipEmber to give you a copy of your data, correct it, delete it, or stop a specific use. If you are in the EU/EEA, the UK or Switzerland you also have the rights to restriction, objection and data portability, and to complain to your local supervisory authority. If you are in California, you have the rights to know, delete, correct and to opt out of sale/sharing — ClipEmber does not sell or share personal information in that sense, so there is nothing to opt out of, and we do not discriminate against anyone who exercises a right.

To exercise any right, email hello@clipember.com from your account address. We reply within 30 days and never charge for a first request.

12. Security

All traffic to ClipEmber runs over HTTPS/TLS. Data at rest sits in managed services (Supabase Postgres, Cloudflare R2) that encrypt storage volumes. Media in object storage is private and served only through short-lived signed URLs. Access to production systems is limited to the people who operate ClipEmber, and platform tokens are requested with the narrowest scopes the feature needs (for example: upload permission, not read-your-videos permission). No system is perfectly secure; if a breach ever affects your data we will notify you and the relevant authority as the law requires.

13. Children

ClipEmber is a business tool for creators and is not directed to children. You must be at least 18 years old to use it. We do not knowingly collect data from children; if you believe a child has an account, write to hello@clipember.com and we will delete it.

14. International transfers

ClipEmber’s hosting, storage and payment providers are located in the United States, so your data is processed there and in Ukraine. Where we transfer personal data out of the EU/EEA or the UK, we rely on the European Commission’s Standard Contractual Clauses (and the UK addendum) in our agreements with those providers.

15. Changes to this policy

If we change how ClipEmber handles your data, we update this page and its effective date, and for material changes we email account holders before the change takes effect. Continuing to use ClipEmber after that date means the updated policy applies.

16. Contact

Privacy questions, data requests and complaints: hello@clipember.com. Operator: ClipEmber, Ukraine. Related document: ClipEmber Terms of Service.