Skip to content

Privacy

The desktop app does not phone home. This page explains the parts that do talk to a server, and what they send.

Last updated 6 August 2026

The local edition collects nothing

The open-source local edition of Premation makes no network requests of its own. There is no account, no telemetry and no crash reporter. Your projects are .motion bundles on your disk, and your media stays where you put it.

You can verify this rather than take our word for it: the source is published under GNU AGPL v3.0.

This website

The marketing pages use Google Analytics 4 to count page views and referrers. It sets cookies. It does not receive your name, email, or anything you type into the app.

The documentation and journal pages serve no analytics beyond the same page-view measurement.

The waitlist

If you ask to be notified about a build, we store your email address, which platform you asked about, and the date. It is used for exactly one message: the one telling you that build is downloadable. There is no newsletter, and the list is not shared or sold. Reply to that email and we will delete your entry.

Accounts and the cloud edition

The cloud edition is optional and separate. Signing up stores an email address, a hashed password or an OAuth identifier, and the projects you choose to sync. Sessions are held as refresh tokens that you can revoke by signing out.

Deleting your account removes the account record and its synced projects. Backups age out on their own schedule, so allow up to 30 days for copies to disappear entirely.

AI keys

The assistant runs on your own provider key. The key is encrypted before it is stored and is only ever decrypted to sign a request to the provider you chose. We do not train on your prompts, and we do not keep the generated output beyond the response that reaches your editor.

Contact

Questions about any of this, or a deletion request, go to the Discord or the issue tracker.