プライバシーポリシー

Who we are

This website and the CutCull WebApp (together, "the Service") are operated by Gryphon, an individual ("we", "us"). You can reach us at support@cutcull.com.

This policy covers the Service as offered in your web browser. It does not cover the CutCull desktop application, which will ship with its own terms.

Your media never leaves your device

When you open a video or photo in the WebApp, it is read and processed entirely inside your browser. We do not upload, receive, store or view your media, and neither does anyone else on our behalf.

The same applies to the file names and folder locations of your media, to any LUT files you import, and to the edits you make (in and out points, grading and crop settings). None of these are sent to us or to any third party.

This is enforced by the page itself: the site's security policy only allows the browser to connect back to our own site, and the only thing the WebApp requests from it is the site's own code and assets.

What is stored on your device

To remember your work between visits, the WebApp stores the following in your browser. It stays on your device and is never sent to us.

A cookie named cutcull.web.language that remembers your language choice. It is written only when you actively switch languages on the site — never just from visiting — and the same choice is also kept in local storage. It is the only cookie the Service sets, and it is used to show you the right language, not to track you.
A note in local storage named cutcull.web.languageBannerDismissed that remembers you dismissed the language suggestion banner, so it is not shown to you again.
Display preferences such as player volume, panel layout (including widths and collapsed state), and color theme, kept in local storage.
Your editing decisions — segment ranges and names, grading and crop settings, output preferences — kept in a browser database.
The text of any LUT files you import, so they are available again next time.
For each file you work on, its name and size plus a digest calculated from small samples of its content. This lets the WebApp reconnect your saved decisions when you open the same file again. The digest cannot be used to rebuild the file's content.

Your media files themselves and the outputs you render are never stored by the Service; your browser only holds them in memory while the page is open. You can delete everything listed above at any time with "Clear local records" in the WebApp, or by clearing this site's data in your browser settings.

Hosting

The Service is served through Cloudflare. Like any web host, Cloudflare necessarily processes technical information about each request — such as your IP address, browser type and the page requested — in order to deliver the site and protect it from abuse. Cloudflare handles this information under its own privacy policy. We do not use it to identify you or to build a profile of you.

Product analytics and error reporting

To understand which features are useful and what fails in practice, the Service includes first-party product analytics and error reporting. It records which pages are visited, broad browser capabilities (such as whether the technologies behind the editor are supported), how many videos, photos and RAW files you import together with a coarse size band for the batch, how many files in a batch could not be imported and the reason category (unsupported type, unreadable, over the limit or a duplicate), which editing tools were used, how many items are in your workspace when you start an export compared with how many go into it and how many subclips are switched on, whether the desktop waitlist form was opened or a signup was submitted (with the platform you chose — never your email address), whether exports succeeded, failed or were cancelled, how long exports took as a coarse time band, the resolution band of the output, error codes when something fails, and — when you leave or switch away from the page — how far a visit got through the import-and-export flow and a coarse band of how long the page was in the foreground. No event carries free text: your media, file names, file locations, LUT files and edit values are never sent, and error reports carry a code, never a message or stack.

Each event carries a random identifier that your browser generates once and keeps in its local storage (keys starting with cutcull.web.telemetry). It is not linked to your name or email — the Service has no accounts — and you can delete it at any time by clearing this site's data in your browser. Because this identifier persists in your browser, the data is pseudonymous rather than fully anonymous.

When events are delivered, our infrastructure derives your country from the request and keeps only that country code with the data; your IP address is not stored with events. Events are retained for about three months in the analytics store we query, and for thirteen months in a raw event archive kept for reprocessing.

You can turn analytics off at any time: the switch sits in the site footer, on this privacy page, and in the workspace preferences of the WebApp. If your browser sends a Global Privacy Control or Do Not Track signal, we treat that as a refusal and collect nothing. In regions where the law requires prior consent, we ask you first with a banner and collect nothing until you agree.

We sometimes use an AI service provider to help analyse aggregated statistics. Only aggregated results — never anything that identifies an individual visitor — are shared in that process. The Service still contains no advertising and no third-party analytics or beacon scripts, and it has no accounts and takes no payments.

The desktop release waitlist

The desktop page offers a waitlist: leave your email address, and we notify you when the CutCull desktop application is released. When you submit the form we collect the email address you type, the platform you choose (macOS, Windows or both), and the interface language you are using, plus a status and timestamps that our server records. That is everything.

We do not store your IP address, and the list is not linked to the pseudonymous identifier used for product analytics. To limit abuse, our infrastructure compares a hash of your email address and your IP address against recent signups; both are held in memory only, for a short time, and are never written to the database.

The list serves exactly one purpose: sending you one notification when the desktop version is released. It is not used for marketing campaigns, we do not sell it, and we do not share it with anyone except the email service provider that sends the messages on our behalf as a processor. That provider has not been chosen yet; we will update this section when it has been.

Signing up works by double opt-in: we first send a single confirmation email, and your signup only counts once you click the link in it. Until then you receive nothing but that email. Every email we send for the list carries an unsubscribe link, and using it deletes your entry immediately.

To be straightforward about the current state: sending of these emails has not started yet. Until it does, no confirmation email will arrive and your signup simply stays pending; nothing else is done with it in the meantime. Since you have no unsubscribe link yet during this period, you can withdraw by contacting us as described below, and we will delete your record.

How long we keep an entry: if it is not confirmed and the confirmation email has already been sent, it is deleted 7 days later; if the confirmation email has not been sent yet, the pending entry is kept until we send it; a confirmed entry is kept until you unsubscribe, or until we have sent the release notification and closed the list. Unsubscribing always means deletion. The list is stored in Cloudflare D1.

Feedback and crash reports

The website offers a feedback form for reporting a problem or suggesting a feature, and a page that fails with an error offers a crash report button. When you submit either, we collect exactly what you typed (your description and, if you choose to leave one, your email address so we can follow up), the interface language, the page path, and your browser's user agent, which our server records. A crash report additionally contains the error name and a truncated error stack, both shown to you on screen before you send anything. Nothing from your media — no files, file names, folders, or edits — is ever attached automatically; what leaves your browser is what you see and choose to submit.

We use feedback only to fix problems and improve the product, and we do not link it to the pseudonymous identifier used for product analytics. To limit abuse, submissions are rate-limited: your IP address is compared against recent submissions in memory only, for a short time, and is never written to the database.

How long we keep a report: there is no automatic expiry. We keep entries until the matter has been handled, then delete them manually. An email address you left is used only to follow up on your report and for nothing else.

When you contact us

If you email us, we receive your email address and whatever you write. We use it only to reply to you and keep it only as long as needed to handle your request. Please do not send us media files unless you have a specific reason to.

Children

The Service is not directed at children, and we do not knowingly collect personal data from children.

Changes to this policy

We will post any change on this page and update the effective date above. If a change affects how your data is handled, we will make it clearly visible on the site before it takes effect.

Language

This policy is available in English and Simplified Chinese. If the two versions differ, the English version prevails.

Contact

Questions about this policy or your data: support@cutcull.com.