00:00:00 LEGAL · PRIVACY
Privacy policy.
Your projects, footage and renders never leave your computer unless you choose to share them. No ads, no usage analytics, and nothing is sold to anyone.
Last updated 12 November 2026
Who's responsible
Brio and brio.art are run by Jeffery Russell. For anything about your data, including asking what I hold or to have it deleted, email jeff@jefferyrussell.com.
What the Brio app sends, and when
Brio works on your computer. It only connects to the internet for the things below, and every one of them is for a feature, not for tracking you.
- Licence activation and checks
- Your licence key and the name you give the computer go to the licence server when you activate, deactivate or check a licence.
- Update checks
- Brio asks GitHub, where releases are hosted, whether a newer version exists. GitHub sees your IP address and the request.
- Crash reports (off unless you turn them on)
- Brio asks once. If you say yes, crashes and errors go to Sentry with the app version and operating system. They don't include your projects, project file paths or personal details, and you can turn them off in Settings.
- Content from brio.art
- The welcome screen, the image library, lessons and the manual load from brio.art, which sees an ordinary web request.
- Optional AI models
- Speech detection and AI Matte download their models from Hugging Face the first time you use them. After that they run entirely on your computer; your footage and audio are never uploaded.
- Assistant panel (only if you use it)
- Your messages and the project details you share with it go to Anthropic using your own API key, under your account with them. The key is stored in your system's keychain, never on my servers.
- Figma import (only if you use it)
- Brio fetches the Figma file you choose using your own Figma token, which is also kept in your keychain.
- Plugins
- A plugin can only reach the internet if it declares network access and the hosts it talks to. What it sends is up to its author.
Brio Community
Publishing a project to Brio Community is opt-in and public. What's stored: a one-way hash of your licence key (not the key itself), the display name you choose, and the post itself (title, description, tags, the project file, previews and thumbnails), plus download and like counts. It's hosted with Supabase and Vercel. Ask and I'll delete your posts and creator profile.
Buying Brio
Purchases are handled by the reseller named at checkout, which acts as merchant of record and processes your payment details under its own privacy policy. I never see your card number. I receive your name, email address, country and order details so I can deliver your licence and support you.
The website
- brio.art is hosted on Vercel, which keeps standard server logs (such as IP address and pages requested) for security and operations.
- There are no analytics, advertising or tracking cookies on the site.
- Fonts load from Google Fonts, which sees your IP address when they load.
- The mailing list runs on Buttondown. It stores your email address and sends only Brio news. Every email has an unsubscribe link.
- The contact form sends your message to my inbox through FormSubmit.
How long things are kept
Order records are kept as long as tax and accounting law requires. Support emails are kept while they're useful for helping you. Mailing-list addresses are kept until you unsubscribe. Crash reports expire under Sentry's retention settings.
Your rights
Wherever you live, you can ask what data I have about you, ask me to correct it, or ask me to delete it. Email me and I'll answer myself. If you're in the EU or UK you also have the right to complain to your data protection authority.
Children
Brio isn't aimed at children under 13, and I don't knowingly collect their data.
Changes
If this policy changes, the new version will be posted here with a new date.