Privacy Policy

1. Who we are

PatchWork is operated by Bryan Scott Chen, an individual based in Houston, Texas, USA ("PatchWork", "we", "us"). We are responsible for the personal data described in this policy. This policy applies to the website at www.patchworkvideo.com and its subdomains, the web app, the desktop app, and the agent tools (together, the "Service"). The Terms of Service use the same words.

2. What we collect

Your account

• Email address and display name.
• Your password, stored only as a salted hash. We cannot read it.
• If you sign in with Google or GitHub: the account ID and email that the provider sends us.
• The invite code that you used, your plan, and your role.
• Your answers to the optional onboarding questions (for example, your role, what you make and the tools you use).
• Sign-in sessions: when each one started, when it was last used, and its type (browser, agent or developer key). We do not store your IP address or browser type with sessions.

Invite requests

When you request an invite, we collect your email, your name if you give it, what you make, your note, and which form you used. To stop abuse, we also store a keyed hash of your IP address, not the address itself.

Your content

• Projects that you save to your account, including prompts, scripts, settings and documents.
• Images, video and audio that you upload or generate, and the files of your asset library.
• Comments, review notes and share-link permissions; workspace membership and activity; templates that you publish.

Settings and API keys

While you are signed in, your settings sync to your account. This includes the API keys that you enter for providers such as Google Gemini, fal.ai, ElevenLabs, BytePlus and Resemble, and the ComfyUI key. We encrypt the keys before we store them, with a key that our server holds. This means that our server can decrypt them. We use them only to put your keys on your other devices. GPU provider keys, such as your RunPod key, sync only if you turn that on.

Usage and service data

• Usage counts. How many generations you ran each day, by provider and type, with the app's own cost estimate. The days on which you used the app.
• GPU timings, if you leave this on (Settings, "Contribute to fleet statistics"). For each GPU generation: the model, settings, image size, timings, GPU type, errors and a salted hash of the prompt. These records are linked to your account. Your prompt text reaches our server only so that the server can hash it, and we do not store it. We publish only combined statistics, never one account's runs.
• Bug reports, only when you send one: what you write, the screen, the app version and platform, and the files that you attach. The diagnostics file has app versions, your storage state, recent errors and your browser's user agent. It does not contain keys, tokens or prompt text.

Technical data

Our hosting provider, Cloudflare, receives your IP address and request details when you use the Service. Cloudflare uses them to deliver the Service and to protect it, for example with rate limits. Our own database does not store raw IP addresses. For invite requests, password-reset requests and sign-in links, we store a keyed hash of the IP address to limit abuse.

Payments

Paid plans are not live yet. When they are, Stripe will process your payment details. We will receive and store your Stripe customer ID, your plan, its status and its billing period. We will never see your full card number.

Cookies and browser storage

PatchWork does not set cookies, and it does not use advertising or analytics trackers. The app uses your browser's storage (local storage and IndexedDB) to keep you signed in and to keep your settings and work on your device. When you use Google sign-in or the Google Drive picker, Google can set its own cookies. Because we do not track you across sites, we have no tracking for "Do Not Track" or Global Privacy Control to switch off.

3. What stays on your device

• Provider logins. In the desktop app, your sign-ins to Google Flow, ChatGPT, Kling, Grok, Higgsfield, Dreamina and CapCut, and their cookies, stay in the app's data folder on your computer. They are encrypted with your operating system's keychain when one is available. We never receive them.
• Logs and crash reports. The desktop app writes logs and crash dumps to your computer. It does not upload them. A bug report includes a log only if you attach it.
• Local work. Projects and media that you keep on your device, and the video editor's media, stay there unless you sync or upload them.
• Browser extension. The PatchWork extension sends data only to the desktop app on your own computer.
• In the web app, your settings, including API keys, are also kept in your browser's storage. Anyone with access to your browser profile can read them.

4. How we use data

We do not sell personal data. We do not share it for cross-context behavioural advertising. We do not use your content to train AI models. The people who run PatchWork can see account data when they give support, investigate abuse or fix the Service.

5. Services you connect

When you generate, the app sends your prompts, reference media and settings to the provider that you chose. That provider handles them under its own terms and privacy policy, not this one. Depending on what you connect, these include Google (Flow, Gemini), OpenAI (ChatGPT), Kling, xAI (Grok), Higgsfield, ByteDance (Dreamina, CapCut, BytePlus), fal.ai, ElevenLabs, Resemble, RunPod, Comfy Cloud, your own ComfyUI server, and the stock media sites Pexels, Pixabay and Freesound.

The Claude chat in the desktop app runs your own Claude Code installation with your own login. Anthropic handles those messages under your agreement with Anthropic.

Some requests from your browser go through our proxy so that they can reach the provider: calls to RunPod and your GPU pods, and some media downloads and uploads. The proxy forwards these requests, including the key that the request carries. It does not store them, but our logs can record the provider's hostname.

6. Our service providers

These companies process data for us, to run the Service:

7. Google user data

• Google sign-in gives us your Google account ID, email address and name. We use them only to create your account and sign you in.
• Google Drive uses the drive.file permission. PatchWork can reach only the files that you pick, or that PatchWork created in your Drive. We use this access only to import and export your media and projects when you ask. On the desktop, the Drive token is stored encrypted on your computer. It passes through our server when it is created or renewed, and our server does not store it.
• We do not use Google user data for advertising, we do not sell it, and we do not use it to train AI models. People can read it only with your permission, for security, or when the law requires it.

PatchWork's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

8. What other people can see

• Collaborators on a project or workspace that you share can see your name, email and profile picture, your comments and your activity in it.
• Templates that you publish show your name as the author.
• Media links are public. Anyone who has the URL of an uploaded or generated file can open it.
• AI agents and tools that you connect with an agent token can do what you can do in your account.
• If you accept a developer access request, that developer can reach your account as the request describes, until you revoke it.

9. How long we keep data

• Account data and synced content: until you delete it or delete your account.
• Sessions: a browser sign-in ends after 30 days. Agent tokens and developer keys last until you revoke them.
• Public media storage: uploaded and generated images, video and audio are deleted automatically after 7 days. Shared artifacts, project snapshots, workspace assets and GPU outputs stay until they are deleted. Ask us if you want them deleted.
• Invite requests: until you ask us to delete them, or until you delete your account.
• Bug reports: until we no longer need them to fix the problem.
• Shared projects, workspaces and live rooms: until their owner deletes them. Comments stay with the project that they are on.
• Security and admin logs: as long as we need them to protect the Service. They can include your email.
• Backups: our database host keeps a rolling history for up to 30 days. Deleted data leaves it within that time.

Delete your account

On the Account page, open Profile & security and use Delete account. This deletes at once:

• Your account, sign-in methods and every session.
• Your settings and synced API keys.
• Your cloud projects, your private files, and the templates that you published.
• Your usage records, GPU timings, onboarding answers and bug reports.
• Your invite request and password-reset requests.

It does not reach the items below. Delete them in the app first, or email us:

• Shared projects and workspaces that you own, and comments that you left in other people's projects.
• Media at public URLs that has not expired yet.
• Data on your own devices, and data that connected providers hold under your accounts with them.
• Security and admin logs, and records that we must keep by law.

If you have an active paid plan, cancel it first. If you cannot use the Account page, email us from your account address and we will delete the account for you.

10. Your choices and rights

• See and export your data. Export projects as .nbflow files in the app. For a copy of your account data, email us.
• Correct it. Email us, and we will correct it.
• Delete it. See Delete your account.
• Turn off GPU timings in Settings.
• Stop key sync by signing out, or by removing the keys from Settings.

Depending on where you live, the law can give you more rights. For example, in the EEA, the UK and some US states, you can ask to access, correct, delete or port your data, object to or restrict some uses, and withdraw consent. If you are in the EEA or the UK, you can also complain to your data protection authority. We will not treat you differently because you used these rights.

To make a request, email [email protected] from the address on your account. We reply within 30 days. We can ask you to confirm that the account is yours. Someone can make a request for you if you authorise them in writing.

11. Security

All traffic uses TLS. Passwords and sign-in tokens are stored only as hashes. API keys are encrypted at rest. On the desktop, provider logins are encrypted with your operating system's keychain when one is available. No system is fully secure. Media links are public by design, so do not put confidential material through the beta. If we learn of a breach that affects your data, we will tell you as the law requires.

12. Where data is processed

We are in the United States. Cloudflare runs our servers and storage on its global network. If you use PatchWork from outside the United States, your data is processed in the United States and in other countries where our providers operate. Where the law requires it, we rely on safeguards such as the European Commission's Standard Contractual Clauses that our providers offer.

13. Children

PatchWork is for people aged 18 or older. We do not knowingly collect data from children. If you think that a child has given us data, email us and we will delete it.

14. Changes

We can change this policy. If a change is material, we will tell you by email or in the app before it applies. The date at the top of this page shows when the policy last changed.

15. Contact

Questions or requests about privacy: [email protected].