Privacy Policy
What YapCut sees and what stays on your machine.
Last updated: May 15, 2026
The short version
- Your original video files never leave your browser. Renders run on your hardware.
- We do collect account data (email, name) through our auth provider and a small amount of project metadata and prompts on our server, so YapCut can resume your work.
- We use Microsoft Clarity to understand product usability. You can opt out via your browser's Do Not Track settings or cookie controls.
- You can delete your account and associated server-side data at any time by emailing [email protected].
1. Scope
This Privacy Policy explains how YapCut ("YapCut", "we", "us") handles information when you use the YapCut web application and related services (the "Service"). By using the Service you agree to the practices described here.
2. Definitions
- Account
- A unique account created so you can use the Service.
- Personal Data
- Any information that identifies, or can be used to identify, an individual.
- Usage Data
- Information collected automatically from your use of the Service, such as request timestamps and feature usage counts.
- Local Data
- Files and derived data that remain inside your browser — including your original source video — and never reach our servers.
- Cookies
- Small files placed on your device by the Service or by our third-party providers.
- Service Provider
- A third party that processes data on our behalf (for example, our authentication provider).
- You
- The individual using the Service, or the entity on whose behalf you act.
3. The local-first carve-out
YapCut is designed so that the most sensitive parts of your work stay on your device. Specifically:
- Source video files are kept in browser storage (IndexedDB) and read directly when you edit or export. They are not uploaded to YapCut servers, even for analysis of 4K masters.
- Final exports are rendered locally using your device's GPU/CPU through the in-browser renderer. We do not host a copy of the rendered output.
- Lightweight derived metadata (for example, video duration, resolution, transcript text, or selected timeline ranges) may be sent to our servers so that YapCut's AI features can plan an edit. We try to keep this footprint as small as the feature allows.
If you delete a project from the YapCut home page, the locally cached source files for that project are also removed from your browser.
4. Data we collect
4.1 Information you provide
- Account identifiers from our authentication provider — typically email address, given name, and family name.
- Prompts and instructions you type into YapCut's editing composer.
- Project, session, and turn metadata you create while using the Service (titles, timestamps, comments).
- Support correspondence you send to us.
4.2 Information collected automatically
- Usage Data such as IP address, browser type and version, operating system, device identifiers, language, timezone, screen size and device pixel ratio, and the times and routes of API requests.
- Diagnostic events and error reports generated by the Service.
- Credit consumption records (which AI models you ran, how many tokens or seconds were billed, on which session).
4.3 Information from third parties
- Authentication metadata returned by our identity provider when you sign in (for example, the verified email of your account).
5. Third-party services
YapCut relies on a small number of third parties to operate. Each one handles a defined slice of data:
- Clerk — authentication and account management. Clerk receives the data needed to verify your identity (for example, your email address and login activity).
- Microsoft Clarity — product analytics and session recordings of UI interactions to help us debug and improve the interface. Clarity may capture clicks, scrolls, and rendered DOM, subject to Microsoft's privacy controls.
- Large language model and media providers — to generate edits, captions, and transcripts, YapCut may forward your prompts and the derived metadata (not the source video) to model providers that we contract with. Generation requests are processed under those providers' data-handling terms.
- Object storage and database providers — used to store derived assets (such as extracted audio transcripts or generated frames you have explicitly asked YapCut to keep on the server).
6. Cookies and similar tracking
We use cookies, local storage, and similar technologies for these purposes:
- Essential — to keep you signed in, remember your active project, and protect against fraudulent use of your account. The Service will not function correctly without these.
- Functional — to remember preferences such as theme, language, or last-opened panel.
- Analytics — to measure product usage through Microsoft Clarity. You can decline these by enabling Do Not Track, blocking third-party cookies, or using a privacy extension; the rest of the Service will continue to work.
You can clear cookies and local browser storage at any time from your browser's settings. Clearing the storage that holds local video files will also remove those files from this device.
7. How we use your data
- To provide, operate, maintain, and improve the Service.
- To authenticate you, secure your account, and prevent abuse.
- To bill credits, enforce quotas, and provide usage history.
- To respond to support requests, deletion requests, and legal obligations.
- To analyze aggregate usage trends and improve product quality.
- To communicate operational notices (such as outage alerts or material changes to terms).
We do not sell your Personal Data, and we do not use your prompts, transcripts, or project metadata to train our own foundation models.
8. Data retention
Account and project metadata are kept for as long as your account exists, so that you can return to past projects. Usage Data and diagnostic logs are retained for a rolling window sufficient for operational and security purposes, then aggregated or deleted.
Locally cached source video files persist in your browser until you delete the project, clear browser storage, or use a different browser/device.
9. Security
We use commercially reasonable safeguards — including TLS for data in transit, scoped access controls, and audit logging — to protect the Personal Data we hold. However, no method of transmission over the Internet or method of electronic storage is 100% secure. We cannot guarantee absolute security of data on our servers or on third-party platforms.
10. Children's privacy
The Service is not directed to children under the age of 13. We do not knowingly collect Personal Data from anyone under 13. If you believe a child has provided us with Personal Data, please contact us and we will delete it.
11. Changes to this policy
We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date at the top of this page and, for material changes, surface a notice in the Service. Continued use of YapCut after the update means you accept the revised policy.
12. Data deletion
You can request deletion of your YapCut account and the server-side data associated with it by emailing [email protected]. We will permanently delete that data from our active systems within 14 days, except where retention is required by law (for example, billing records).
Local files (source videos and generated previews stored in your browser) can be removed at any time by deleting the corresponding project from the home page or by clearing your browser's storage.
13. Contact us
Questions about this policy or about how we handle your data:
Email: [email protected]