What data we collect

Below is every category of data AetherCut collects. If something exists in our database that isn't on this list, treat it as a bug and report it to AethercutAdmin@gmail.com.

AetherCut collects your email, Google account ID, display name, avatar URL, signup date, tier, Stripe billing and payment records, limited page view data, and AI feature outputs, but not your video content. It does not store full IP addresses, does not set cross site tracking cookies, and Privacy Mode disables third party AI feature processing.

Account data (only if you sign in)

What payment data does AetherCut collect?

AetherCut stores Stripe payment intent ID, session ID, and customer ID, plus purchase amount, currency, timestamp, and refund or dispute status. Stripe handles card details directly, so AetherCut does not receive your card number.

Does AetherCut store my IP address or track me across sites?

AetherCut does not store your full IP address and does not set cross site tracking cookies. It logs visited paths, referrer host, UTM tags, device type bucket, and timestamps, without joining page views to your account.

We do NOT store the full IP address. We do NOT set cross-site tracking cookies. The page-view row is not joined to your account record.

What happens to my data when I use AI features?

When you use an AI feature, the relevant input is sent to a third party model, but AetherCut keeps only the output. For auto captions, audio is deleted within seconds, and Privacy Mode disables these features.

When you trigger an AI feature, the relevant input is sent to a third-party model. We retain only the OUTPUT (e.g. the generated subtitle text), not the input.

Privacy Mode disables all of these at the toggle.

How this looks in practice

In day-to-day use, the easiest way to understand AetherCut’s data collection is to separate “account and billing records” from “editing content.” If you sign in with Google, AetherCut needs enough information to recognize your account later, show basic profile details in the app, and determine whether you have free or Pro access. If you upgrade, it also needs the Stripe identifiers and transaction status required to confirm payment and handle refunds or disputes correctly. That is very different from storing the actual media you work on. AetherCut’s policy here is narrow by design: it keeps the account, payment, and limited product-operation data it needs, while avoiding storage of your raw video content and full IP addresses.

A common misunderstanding is assuming that any AI-assisted action means all project materials are permanently copied into a database. The important distinction is between temporary processing and retained records. For example, generating captions requires audio to be processed so text can be produced, but the retained item is the resulting subtitle text, not a permanent archive of the extracted audio. The same logic applies to other AI features: the system keeps the useful result you asked for, rather than the full source input wherever possible. If you want to avoid that third-party processing entirely, Privacy Mode is the setting to check before using those tools.

Another practical point is that analytics-style page view data is intentionally limited. Seeing that someone visited a path from a referrer host at a certain time helps operate and improve the site, but that record is not tied back to your signed-in account profile. That means browsing data and account identity are kept more separate than many users expect, which matters if you are trying to evaluate how much of your activity is actually being linked together.

Sources

  1. WebCodecs (W3C Working Draft) W3C Accessed 2026-10-20
  2. Web Audio API MDN Web Docs (Mozilla) Accessed 2026-10-20
  3. File API MDN Web Docs (Mozilla) Accessed 2026-10-20
  4. Using OAuth 2.0 to Access Google APIs Google for Developers Accessed 2026-10-23
  5. OpenID Connect OpenID Foundation Accessed 2026-10-23
  6. Checkout Session object Stripe Accessed 2026-10-23
  7. PaymentIntent object Stripe Accessed 2026-10-23
  8. HTTP State Management Mechanism IETF Accessed 2026-10-23
  9. OpenID Connect UserInfo Endpoint 1.0 OpenID Foundation Accessed 2026-10-24
  10. OpenID Connect Core 1.0 incorporating errata set 2 OpenID Foundation Accessed 2026-10-24
  11. Data protection by design and by default (Article 25 GDPR) EUR-Lex Accessed 2026-10-24

More AetherCut pages