Privacy Policy

ClipDesk is a private content operations service used to prepare, review, publish, and measure short-form video on social accounts that their owners connect and authorize. It finds moments in public Twitch and Kick clips of the streamers a profile follows, transcribes them, cuts and captions vertical clips, and publishes the ones a person approves.

• People who sign in. Profile owners and the members they invite.
• Connected channels. The YouTube channels, X accounts, TikTok accounts and Instagram professional accounts an owner connects for publishing or draft delivery.
• People in the source clips. ClipDesk collects public clips of the streamers a profile chooses to follow on Twitch and Kick, and public videos from links a member submits. Those clips show and quote the streamer and anyone else in them, and can show chat usernames and messages on screen. ClipDesk processes them only to make clips for that profile, as this policy describes. If you appear in content ClipDesk processed and want it removed, write to lane.gg.support@gmail.com.

Sign-in runs through Clerk (see Service Providers). You can sign in with Google, Microsoft, or an email address and password; Clerk emails the verification codes. Clerk holds your sign-in profile: the details you give it, or that Google or Microsoft share when you sign in with them, your password if you set one, and your sessions and devices.

ClipDesk itself stores:

• your verified email address, your Clerk user id, the sign-in method you used (Google, Microsoft, or password) and when you last signed in. ClipDesk does not store your name or profile photo;
• which profiles you belong to and your role in each;
• invitations: the invitee's email address, the profile and role, who sent it, and whether it was accepted or revoked. ClipDesk does not email invitations; the person who creates one shares the link themselves;
• your signed-in sessions, each with its expiry and a one-way hash of the IP address it started from;
• audit records of sign-ins, refused sign-ins, revoked sessions and changes to members and invitations, each with the person, the time and a one-way hash of the IP address. The hash is not reversible on its own, but anyone who already knows an address can match it;
• which notifications you have read or cleared, which groups of notifications you turned off and when, and editor drafts you have not saved yet.

The request-access form stores nothing: it opens a message in your own email app, addressed to lane.gg.support@gmail.com, and we receive only what you send.

We process connected-account identifiers (a YouTube channel id and title, an X account id and handle, a TikTok open id and display name, and an Instagram professional account id and username), encrypted authorization tokens, approved video and caption content, publishing status, and post performance: for the videos ClipDesk posted to YouTube, their view, like and comment counts. We also process the source video, transcripts, and editing decisions used to produce a clip, public details of the clips and streamers a profile follows (names, clip titles and view counts), and operational logs needed to prevent duplicate posts, investigate failures, and protect the service.

Information is used only to provide the requested publishing workflow, show account and post results, improve clip selection and editing quality, secure the service, and comply with law. ClipDesk does not sell personal information or connected-account data, and does not use it for advertising. It shares information only with the platform a profile owner chose to publish to and the service providers listed below, each for the task named there.

These companies process information on ClipDesk's behalf:

• Clerk runs sign-in: it receives your email address, your password or Google or Microsoft sign-in, your sessions, and the IP address and browser details of each sign-in, and sends the verification codes. Clerk's sign-in pages can run a bot check from Cloudflare, which receives your browser's details and IP address.
• Railway hosts the ClipDesk server, background workers, database and media storage, so it holds everything the service keeps: source video, rendered clips, transcripts, profile and sign-in records, and database backups.
• Netlify hosts the website. Every page request passes through it, with your IP address and the requests the website forwards to the ClipDesk server.
• Stripe takes payment for a paid plan. Checkout and Manage billing open on Stripe's own pages: ClipDesk sends Stripe the profile's id, the plan and period chosen and, on a first checkout, your email address; Stripe itself collects your name, billing address, tax id if you give one, and card or crypto payment details. ClipDesk keeps Stripe's customer and subscription ids for the profile, and the plan, its payment status and period dates; it does not see or store your card number.
• Sentry receives error reports, used only to find and fix errors, from the website (in your browser and on its server), the ClipDesk server and the background workers: the error message and stack trace, the page or route and the profile it happened in, browser details, the time and the software version. Each report is scrubbed before it is sent: no cookies, sign-in tokens, request bodies, query strings or email addresses. A report from your browser goes to Sentry directly, which sees your IP address as any server you connect to does; the report itself does not carry it.
• ElevenLabs transcribes speech. It receives the audio track of each source clip and of each long recording a member uploads or links, and returns the words, their timings and who spoke them.
• OpenAI chooses clips and drafts post text. It receives the transcript around each candidate moment, with details of the source, the streamer, the people and topics mentioned, the profile's editing notes, and the writing voice and posting preferences set for the streamer, alongside ClipDesk's own example posts. When ClipDesk's editorial memory is switched on, it also receives patterns drawn from the profile's earlier review decisions on the same streamer's clips. For a long recording it also maps the chapters and the moments worth a clip: it receives the whole transcript, one section at a time, with the recording's title and length. When a member enables meaning search, it receives bounded transcript passages, chapter summaries, moment descriptions and search text to create search embeddings. When a member requests translation, it receives transcript passages and the target language to create a separate translated track. It also researches the streamers a profile follows: when a creator is added, or a member asks for the research again, it receives the creator's name and channel handles, the titles of their most viewed public clips and any notes a member already wrote about them, and searches the web through OpenAI's web search tool to draft the creator notes that the clip choosing reads. For a creator with enough decided clips it proposes further notes once a day from the decisions members made about that creator's clips (each clip's title and summary, the decision, a rating, tags and what the member wrote); a proposal is shown to a member and changes nothing until one approves it. Before a clip renders it applies the profile's editing notes to the clip's edit: it receives those notes, the creator notes, the edit as planned, the clip's title and the transcript around it. Once a clip is chosen it writes the clip's post text for the profile: it receives the transcript around the clip, the streamer's name, the creator notes, the writing voice set for the streamer, the notes and drafts it wrote when it chose the clip and, when the clip's frames were looked at, a written account of what they show. It receives no audio or video.
• Google (Gemini API) plans the vertical layout and identifies visible story beats, and picks thumbnails. For the layout it receives a copy of each clip, with its audio, and its transcript, and finds the faces, webcam and chat on screen; it transcribes the chat messages on screen only for a clip a member opted in to that. The same request may identify redundant speech for optional tighter pacing; the renderer checks those suggestions against the transcript. When a member asks it to pick a thumbnail, it receives a sheet of stills from the finished clip with the words spoken at each, the streamer's name, the title of the stream or source, the clip's summary and headline where it has them, and the language it is in. For a profile that turned on narrator lines, it writes the short lines of text a clip shows between the captions and names the reactions in its silent beats: it receives the words spoken in the clip with their timing, the streamer's name, the stream title, the clip's summary and why it was chosen, the text already on screen and the seconds where nobody speaks, and no audio or video.
• Anthropic grades a sample of candidate moments a second time while ClipDesk is checking its own clip choosing against another model. For each such moment it receives what OpenAI receives: the transcript around it, with details of the source, the streamer, the people and topics mentioned and the profile's editing notes. Nothing it answers changes which clips are chosen. It receives no audio or video.

Each provider keeps what it receives under its own terms. ClipDesk turns off optional response storage on its OpenAI text-generation requests. The embeddings endpoint does not retain application state. These controls do not remove OpenAI's default abuse-monitoring logs, which may retain inputs and outputs for up to 30 days, with legal and safety exceptions. See OpenAI's API data controls. ClipDesk does not ask ElevenLabs, OpenAI, Anthropic or Google for shorter retention than their defaults. Twitch and Kick see ClipDesk's requests for public clips, and YouTube and Twitch see its requests for the videos a member links; those requests carry none of your data. A YouTube video a member links is fetched through a proxy service, which sees the video's address and carries the download, and receives nothing else. ClipDesk does not send email itself and uses no analytics or advertising service.

Your own AI account. Edit With AI and the site assistant run on an OpenAI or Anthropic API key you link yourself in Settings, never on ClipDesk's keys. What they send goes to that provider under your own account and its terms, and that provider's storage of it is between you and the provider. Edit With AI sends your instruction and the pictures you attach with the clip's planned edit, its transcript under the speaker names given in the captions, the clip's summary and why it was chosen, frames of its last render, the profile's editing notes and library sound titles. The site assistant sends your message with what it reads, on your behalf, from the screens of the profile you have open. ClipDesk keeps the key encrypted and never shows it again, and keeps those conversations on its server for the profile they were held in.

YouTube. ClipDesk uses YouTube API Services. By connecting a YouTube channel you agree to the YouTube Terms of Service, and Google's handling of your data is described in the Google Privacy Policy. ClipDesk requests two permissions: upload, used only to publish videos an operator has explicitly approved, and read-only access, used to confirm which channel is connected and to read the view, like and comment counts of the videos it published, from an hour to 90 days after each was posted. ClipDesk's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can revoke ClipDesk's access at any time from your Google account permissions.

X. ClipDesk requests permission to read and write posts, upload media, read the connected account's profile, and keep the connection active between sessions. These are used only to publish approved content and confirm that it was posted; ClipDesk does not read the view or engagement counts of X posts. You can revoke access at any time from X's connected apps.

TikTok. ClipDesk requests basic profile information to confirm the connected identity and draft-upload permission to deliver approved video to your TikTok inbox. ClipDesk does not publish that draft publicly, read engagement counts, or set its caption or privacy. Open the inbox notification in TikTok to finish editing, add the caption, choose privacy and post. You can disconnect in ClipDesk Settings or revoke access in TikTok's app permissions.

Instagram. ClipDesk requests basic professional-account information and permission to publish approved Reels. It stores the professional account id, username and encrypted long-lived access token, and refreshes that token while publishing. ClipDesk does not request messages, comments or insights permissions. You can disconnect in ClipDesk Settings or revoke access in Instagram's Apps and Websites settings. Business or Creator accounts are required; connections for other customers depend on Meta's app review and access approval.

Disconnecting an account. When you disconnect a YouTube channel, or an X, TikTok or Instagram account, under Settings → Connections, ClipDesk immediately deletes the sign-in it stored for that account and the post performance numbers it read from it, and stops posting to it. It then asks Google, X or TikTok to end ClipDesk's access, unless another ClipDesk profile is still connected to the same account, in which case that access is kept for it. If the platform does not confirm, or for Instagram, which has no way to be asked, ClipDesk tells you on screen where to remove its access yourself.

Publishing sends the approved video and its post text to the platform the profile owner selected, together with the minimum account data the platform needs. TikTok draft delivery sends the video; its post text remains available to copy in ClipDesk.

The public pages (this one, the home page, pricing, the terms, the copyright policy and request access) set no cookies. After you sign in, ClipDesk sets only what it needs to work:

• clipping_admin_session keeps you signed in. Page scripts cannot read it, and it lasts for the session, at most 24 hours.
• clipping_admin_csrf protects your changes from forged requests, for the same length of time.
• clipping_clerk_check records for one minute that Clerk confirmed your session.
• clipping-account remembers which profile you are viewing, for up to a year.
• sidebar_state remembers whether the sidebar is open, for seven days.
• Clerk sets its own cookies on the sign-in pages and inside the app to keep your sign-in working.

The app also keeps preferences in your browser's local storage: the color theme, panel and column sizes, video volume, per-clip choices, and a copy of your profiles' names and settings. Session storage holds an invitation link while you accept it and a record of a channel connection in progress. Signing out clears all of it, and every cookie above except the sidebar's. There are no advertising or analytics cookies.

Authorization tokens are stored encrypted in our database, used only by the server-side publishing worker, and never exposed to public pages or client-side code. The ClipDesk server, database and media storage run in Railway data centers in the western United States. The other providers above process what they receive wherever they run their services, which may be outside the country where you live.

• Source video, extracted audio and working copies are not deleted automatically today. A cleanup that would delete them 24 hours after the source finishes processing runs in preview only: it lists what it would delete and deletes nothing. Until it is switched on, they are kept until you ask us to delete them. We will update this policy before it is switched on.
• Video collected for a clip-monitor moment whose processing ended as rejected, a duplicate, or archived is deleted automatically soon after that decision, unless something still depends on it; when no clip was made from it, its transcript is deleted too. The decision and its score are kept so the same moment is not collected again.
• Rendered clips are not deleted automatically today. A cleanup that would delete a clip 24 hours after it became ready for review or was rejected runs in preview only: it lists what it would delete and deletes nothing. Until it is switched on, rendered clips are kept until you ask us to delete them. An approved clip is kept with its publication record.
• A video a member chose to keep when giving feedback, and media under a legal hold or a set retention date, are never deleted automatically, even once cleanup is on, until that keep or hold is released.
• YouTube view, like and comment counts are kept with the publication record, each with the time it was read. ClipDesk confirms the channel's authorization with Google at least every 30 days and deletes the counts if it cannot. Disconnecting a channel in ClipDesk deletes its counts at once. When a channel is removed or its access is revoked, its counts are deleted within seven days of ClipDesk finding that it can no longer read the channel, unless the channel is connected again, and can be read, before then.
• Transcripts, editing decisions, captions, review decisions and audit records are kept for the life of the profile, because they are what improves later clips.
• Your sign-in record, memberships and invitations are kept while the account exists; removing a member ends their access but does not delete their sign-in record. Each ClipDesk session ends within 24 hours.
• A profile an owner deletes is closed to everyone at once, and its files are removed for good 30 days later. The files include its uploaded and rendered media, library uploads and their previews, exports, the copies prepared for its TikTok and Instagram posts, and saved transcription progress. A library file that another profile also uses is kept for that profile. When a profile is deleted, we keep a log of the actions taken in it (which person did what, and when, recorded against item identifiers) for security and accountability, with the content of those records removed; the rest of the profile's records are removed for good 30 days after the deletion is requested. When the profile's records are removed, we also ask X, YouTube and TikTok to end the access that profile gave ClipDesk, unless another ClipDesk profile is still connected to the same account. If a platform does not confirm, or for Instagram, which offers no way for us to do it, you can remove ClipDesk from that account's connected apps yourself. We also keep the record of what a deleted profile's processing cost (which provider, how much and when), with nothing in it that identifies the profile or what was processed, so our accounts keep matching our providers' invoices. A profile export can be downloaded for seven days, then the file is deleted.
• Authorization tokens are kept only while a connection is active. Revoking access on the platform makes the stored token unusable immediately. Disconnecting an account in ClipDesk Settings removes its stored token and stops new sends. A disconnected YouTube channel's or X account's ID and handle are deleted with it; a TikTok or Instagram account's connection identity and publication history remain until you request deletion. For other stored copies, ask us and we will remove them.
• Database backups kept by our hosting provider can hold deleted records until those backups expire.

You can ask for a copy of the personal information ClipDesk holds about you, ask us to correct it, or ask us to delete it: your sign-in record, memberships and sessions, a connected channel, source video and rendered clips, or content you appear in. You can also object to how we use it. Signed in, open Your Data from the profile menu to download your own data or delete your login; a profile owner can also export the whole profile there, or delete it. For anything else, email us as described below.

You can revoke ClipDesk's access to a connected channel from the platform's own settings at any time, and sign out to clear ClipDesk's cookies and browser storage. If the law where you live gives you further rights, write to us and we will respond as that law requires.

Your Data in the profile menu covers the common cases without writing to us: downloading or deleting your login, and an owner exporting or deleting a profile. Deleting your login signs you out and removes it at once; you cannot delete it while you are the only owner of a profile. A deleted profile can be restored by contacting us within its 30 days.

Connected YouTube channels and X accounts. An owner can disconnect a channel or account at any time under Settings → Connections. Disconnecting ends ClipDesk's access and asks Google or X to revoke it (unless another ClipDesk profile is still connected to the same account). It deletes the sign-in, the post numbers and the channel or account ID and handle ClipDesk kept: at once in ClipDesk's database, and in profile exports within 7 days. It keeps the ID and link of each post ClipDesk published to that account, as the record of what was published. You can also remove ClipDesk's access under Google Account → Security → Third-party connections. ClipDesk checks a connected YouTube channel's access twice a day, whether or not it keeps post numbers for that channel, and within 7 days of the access ending it deletes that channel's post numbers, ID and handle. An X account keeps its ID and handle until it is disconnected in ClipDesk or you ask us to delete it. If you cannot sign in, email us at lane.gg.support@gmail.com and we will delete a channel's data within 7 days. Copies in our backups are deleted as those backups expire.

TikTok and Instagram accounts. An owner can disconnect one under Settings → Connections, which removes its stored sign-in and stops new sends. Its connection identity and publication history remain until you ask us to delete them.

For anything else, such as deleting a TikTok or Instagram account's saved data and publication history, data about a channel or content you appear in, or a copy of that data, email lane.gg.support@gmail.com from the address you sign in with or one associated with the account, and name the channel, handle or account. We verify that you control the account, then complete the request within 30 days and confirm by email. Posts already published live on the platform and are not deleted by ClipDesk; remove them from the platform directly.

ClipDesk is for people aged 13 and older, and is not intended for children under 13. If you believe a child under 13 has provided personal data, contact lane.gg.support@gmail.com so we can investigate and remove it. People below the legal age to enter an agreement where they live need a parent or guardian’s permission.

Privacy questions and requests can be sent to lane.gg.support@gmail.com.