Aria Back to the site

Privacy Policy

Effective 28 August 2026

Aria is a video editor that runs on your machine, and this policy is written around that fact: your footage, your projects, your transcripts and your exports never leave your computer unless you send them somewhere yourself. What follows is the short list of what does reach us, why, and how to turn each part off.

The editor

Everything the editor does to your media, including transcription, translation and face detection, runs locally. Aria does not upload media, project files, file names, prompts or transcripts to us or to anyone else.

• Anonymous usage statistics. The app counts a handful of events: it was opened, the first-run setup was finished, a project was created or opened, footage was imported, an export was started and how it ended, an offline model was installed or used, and an AI agent connected to the editor. Each carries the app version, the operating system and its version, and the interface language. There is no account, no device identifier and no content of any kind in these events: no file names, no paths, no footage, no project names, and nothing in them can identify you. They are processed for us by Aptabase, a privacy-first analytics service. You can switch this off in Preferences inside the app, and the switch takes effect immediately.
• Update checks. The app periodically asks our release server whether a newer version exists. Like any web request, that involves your IP address and the app version; we do not use it to build any profile.
• Optional model downloads. If you choose to install a local intelligence feature (transcription, translation, face detection), the model files are downloaded to your machine and run there. The download is a plain file request and carries nothing about you or your projects.
• Agents you connect. If you connect your own AI tools to Aria, what those tools send to their own providers is governed by their policies, not this one. Aria itself sends them nothing.

The website

• Cookie-free analytics. We measure visits with Plausible Analytics, which uses no cookies and stores no identifier on your device. We see aggregate counts: pages, referrers, countries, which sections of a page readers reach, and how the download went, meaning which button was pressed, whether the sign-in dialog was completed or closed, the error code when a sign-in fails, and whether the file was fetched. We cannot see who you are, and neither can Plausible.
• No advertising. There are no ad networks, no cross-site trackers and no sale of data, in any form, to anyone.

Downloading Aria

The download asks you to leave an email address or sign in with Google or Apple. This is the one place we knowingly collect personal data, and it is limited to:

• Your email address and sign-in provider, stored with the language of the page you used. Sign-in is handled by Google Firebase Authentication; we never see or store a password. We use the address to send occasional product news. Every mail includes a one-click unsubscribe, and the list is never shared or sold.
• Ordinary server logs. The file itself is served from our storage provider (Cloudflare R2), which processes your IP address to deliver it, as any file host does.

The browser storage that sign-in itself requires (a Firebase session, and a small flag so we do not ask you twice) is functional storage, used for nothing else.

Retention and your rights

Anonymous statistics are kept as aggregates and cannot be traced back to you, by us or by anyone, which is the point of collecting them that way. Your email address is kept until you unsubscribe or ask us to delete it. You can ask at any time what we hold about you, ask for it to be corrected, or ask for it to be deleted, by writing to hello@ariaeditor.com.

Children

The website and the app are not directed at children under 16, and we do not knowingly collect personal data from them.

Changes

If this policy changes, the new text will be published here with a new effective date. A change that affects what is collected will also be noted in the app's changelog.