Trust & Security

AetherCut is built privacy-first: your video never leaves your device. This page explains the controls behind that promise, honestly — including what we have not yet certified. Last reviewed: June 2026.

Our security model: local-first by design

The single most important security property of AetherCut is architectural: editing, rendering, and export all run in your browser using HTML5 Canvas, WebCodecs, and FFmpeg.wasm. Your source video is never uploaded to our servers — so it cannot be breached, subpoenaed, or leaked from a place it never was.

You can verify this yourself: open your browser's DevTools → Network tab while you edit and export. You will see zero outbound video bytes. See /network-traffic-analysis for a request-by-request breakdown.

Encryption

Data minimization

We collect the minimum needed to run the product. No advertising IDs, no device fingerprinting, no cross-site tracking cookies, no full IP storage.

The complete, honest inventory lives on two pages: /what-data-we-collect and /what-data-we-do-not-collect. If something exists in our database that isn't on the first list, treat it as a bug and report it.

Authentication & access control

Payments

Payments are processed by Stripe. AetherCut never sees or stores your card number — Stripe collects it directly. We retain only non-sensitive references (customer ID, payment-intent ID, amount, status) so we can grant and revoke Pro access. Card handling (PCI DSS scope) is delegated to Stripe.

Subprocessors

A subprocessor is a third party that may process data on our behalf. Because your video stays on your device, most of ours only ever receive small derived inputs (e.g. a few seconds of extracted audio, a text prompt, or timeline metadata) — and only when you explicitly trigger that feature.

The full, current list is published at /subprocessors.

Availability & resilience

Compliance posture (stated honestly)

We would rather under-claim than mislead you, so here is exactly where we stand:

Vulnerability reporting (responsible disclosure)

Found a security issue? We want to hear about it. Email AethercutAdmin@gmail.com with details and steps to reproduce. Please give us reasonable time to fix before public disclosure; we will not pursue good-faith researchers who follow this policy.

Incident response

If a security incident affecting user data occurs, we will investigate promptly, remediate the root cause, and notify affected users and regulators as required by applicable law. Because we hold so little user data and no video content, the blast radius of any incident is deliberately small.

More AetherCut pages