Security research makes Brello safer for everyone who uses it, and we welcome it. If you find a weakness in Brello for Mac or on brello.ai, please tell us privately first, so we can fix it before anyone can misuse it.
How to report
Email security@brello.ai. Please write in English, and include:
- what you found, and what someone could do with it: read files they shouldn’t, make Brello act without a yes, send something off the Mac, get around the license, or anything else;
- the steps to reproduce it, with the Brello version (in Brello ▸ About Brello) and your macOS version, and your Mac’s chip;
- any proof of concept, kept to what’s needed to show the issue;
- how you’d like to be credited, if you’d like to be.
If the details are sensitive, say so in a first email without them, and we’ll agree how to send them.
What’s in scope
- Brello for Mac, as downloaded from brello.ai and signed by Stuvio Digital Private Limited: the app, its login helper, its Services item, its Shortcuts actions, the way it handles files, its undo record, the private index, the license check, and every request it makes.
- The brello.ai website, including its download.
Of particular interest:
- anything that makes Brello delete, send, quit or go online without the question it should ask;
- anything that makes Brello read or change a file outside what the request named;
- a request that leaves the Mac without being written to the Privacy page first;
- a file name, a document’s contents or a web page that changes what Brello does (prompt injection that gets past its code’s checks);
- a tampered copy of Brello that macOS or Brello itself accepts.
Out of scope
- Polar’s checkout and customer portal are Polar’s; report issues there to Polar.
- Apple’s software, including macOS, Apple’s on-device model and Image Playground: report to Apple.
- Reports from automated scanners with no demonstrated impact, missing headers with no exploit, and anything that needs physical access to an unlocked Mac or an administrator’s password the attacker already has.
- Social engineering of our people, and denial of service.
What we ask of you
- Test only on Macs and accounts you own, or have permission to test.
- Don’t access, change or delete other people’s data. If you reach someone else’s data by accident, stop, and tell us.
- Don’t run tests that slow down or break the site for others.
- Give us reasonable time to fix the issue before you share it publicly, and tell us before you do.
What we do
We read every report and reply to say we’ve received it. We look into it, tell you what we found, and fix confirmed issues in a new version of Brello, posted on the download page.
Our security, in brief
Brello is signed with our Apple Developer ID and notarized by Apple, with the hardened runtime; only one part of the app may reach the network, and a test fails the build if network code appears anywhere else; risky actions are held for your yes by Brello’s code, not by a model. The security page has the details.
This page is also published as security.txt.
Updated October 28, 2026. Questions about your data: privacy@brello.ai. A security issue: security@brello.ai.