- Version
- 1.1, October 21, 2026
- Effective
- From the release of Brello for Mac. Version 1.0 took effect on
- Applies to
- Stuvio; Brello for Mac; Brello 1.0, our app for iPhone and Android; Brello Super Intelligence, our research direction; this website
- Changes
- Published before they take effect, with a dated note and a redline (section 7.5). Version 1.0 is kept, and every change is marked
01
Mission and scope
Our mission is to build capable intelligence that answers only to the person using it, with privacy that can be verified rather than promised.
That means Brello works for the person using it, not for advertisers or for us; what they share is used only to answer them; and where Brello runs, and what it keeps, can be checked by someone other than us.
This charter binds Stuvio, the company that makes Brello: “we” means Stuvio, and “Brello” means the software. It covers three products, written about in two tenses:
- Brello for Mac, an app that makes the Mac easier, with an agent that does the work you ask for on your Mac, with Brello’s own code and Apple’s on-device model, described as it ships.
- Brello 1.0, an app for iPhone and Android that runs its language model entirely on the phone, described as it ships.
- Brello Super Intelligence (Brello SI), our research direction, described as intent: what it is designed to do.
02
Why privacy must be architectural
A privacy policy states what a provider has decided to do with your information; a system’s architecture decides what it is able to do. That is where we make our privacy commitments.
What people ask an AI, and the files they give it, can be deeply personal: a symptom, a contract they can’t share, a photo of their home. A policy can change after you have shared something, but it can’t reach what was never sent.
So we follow one rule: work runs on your device whenever it can, and when it can’t, Brello’s servers must keep nothing, and someone other than us must be able to check that. Brello for Mac and Brello 1.0 meet the first half: both do their thinking on the device. Brello SI is designed to meet the second. Brello for Mac’s Privacy page, in the app, and our privacy policy set out what stays on the device, what leaves and when.
03
Three lessons from building Brello 1.0
Before asking anyone to trust a larger system, we built the strictest version we could: Brello 1.0, an app that answers with no server of ours and no account. It taught us three things.
- Useful AI can run entirely on a phone. After a one-time download of 977 MB to 3.66 GB, Brello 1.0 answers on the phone’s GPU, falling back to the CPU, and works offline. We believe many everyday questions can be answered this way, but we haven’t measured how many.
- Ordinary code around the model can make it more careful. While web search is off, Brello 1.0 asks “Search the web for this?” before looking up a question that seems time-sensitive. It cites web sources inline as [1] and [2], and stops a reply that starts repeating itself. Because small models copy the shape of their instructions, its base system prompt is four sentences long.
- A phone has hard limits. Brello Pro, the most capable of the three models, is recommended for phones with 12 GB of RAM. Each answer draws on only the last six messages of a chat, and a model small enough for a phone is far smaller than frontier cloud models and can be wrong.
Brello for Mac carries the second lesson furthest: code around Apple’s on-device model reads each request, checks each change on the disk and decides what needs your yes (section 09). Brello Super Intelligence, our research direction, keeps the device as the place where work runs first.
04
Three layers, with the device first
Brello Super Intelligence is designed for deep reasoning, long-term personal context and tasks done on a person’s behalf, in three layers, with information moving outward only when a task needs it. The first and the third are how Brello for Mac and Brello 1.0 work; the second, sealed compute, is Brello SI’s design.
- Your device. Work runs on your device whenever it can. Brello for Mac thinks on the Mac, with its own code and Apple’s on-device model, and Brello 1.0 processes every question, photo and answer on the phone.
- Sealed compute. When a task needs more than a device can give, Brello SI is designed to run it on hardware-isolated, stateless servers that keep nothing: no logs, no retention, no human access. Your device verifies a server before sending it anything.
- The open web. Fresh facts come from the web only when a request needs them and you allow it. Brello for Mac asks once, the first time a request needs the internet, sends only words you typed, and writes every request in its ledger before it leaves. Brello 1.0 keeps web search off until you turn it on and asks before going online; the search engine and sites it reads see the search text and page requests as normal web requests, including the phone’s IP address.
Section 4 · Published architecture
We will publish a description of Brello Super Intelligence’s architecture, including what runs where and what each layer can and cannot see, before anyone outside the team uses it.
- Scope
- Brello SI
- Check
- The description itself, published on this site with a version number and date, and linked from section 7.1.
05
Eight commitments
Each commitment says what we will or will not do, where it applies and how you can check it.
Commitment 01
We will not use your conversations to train models.
We will not use your requests, files, questions, photos, answers or chats to train or fine-tune any model, or for anything except answering you. Brello for Mac does its work on your Mac and learns nothing from your data (section 9.6). Brello 1.0 never sends your chats to us: it processes and stores them only on the phone, and excludes them from Android cloud backups and device-to-device transfer. With web search on, the search text and requests for up to four result pages go directly from the phone to a search engine and those sites, which see normal web requests.
- Scope
- Stuvio, Brello for Mac, Brello 1.0, Brello SI
- Check
- For Brello for Mac, the ledger of every request that leaves the Mac (section 9.5), and Private by construction. For Brello 1.0, our privacy policy says what leaves the phone, when and to whom. None of your questions, photos, answers or chats goes to Stuvio, and any other request is a security issue to report to security@brello.ai. For Brello SI, the architecture description (section 4) will state where conversations go and how long each layer keeps them.
Commitment 02
We will not run advertising.
We will not show advertising in Brello or on this website, or use advertising to pay for Brello. An advertising business would reward learning more about the people who use Brello, which Brello is designed not to do. Brello for Mac is paid for with a license, sold through Polar, and each store shows Brello 1.0’s price.
- Scope
- Stuvio, Brello for Mac, Brello 1.0, Brello SI, this website
- Check
- Brello for Mac has no advertising, analytics or crash reporting (its system card). Brello 1.0 contains no advertising, analytics or crash-reporting software, as our privacy policy states. This website shows no advertising. Since November 12, 2026 it counts visits with Google Analytics and measures our own ads on X with X’s pixel, each asked first in the European Economic Area, the United Kingdom and Switzerland and never loaded for a browser that sends a Global Privacy Control signal; its cookies page lists everything it stores, which your browser’s developer tools will show.
Commitment 03
We will collect only what a task needs.
We will ask only for the information and permissions a task needs, and Brello SI will keep nothing it processes off your device once the task is done. Brello for Mac asks for a permission only when a request needs it, and a request leaves the Mac only with words you typed. Brello 1.0 has no account, and it reaches the camera and photos only through Android’s system picker, when you choose them.
- Scope
- Stuvio, Brello for Mac, Brello 1.0, Brello SI
- Check
- Brello for Mac’s Privacy page and Private by construction list what can leave the Mac and what each request carries. Brello 1.0’s store listings show each permission it asks for. For Brello SI, the architecture description will state what each layer receives and how long it keeps it.
Commitment 04
We will evaluate each new capability before release, and publish what we find.
Before Brello can do something new, we will test how it could fail or be misused, and hold the release until it meets criteria set before testing began. The release will come with an evaluation summary: what we tested and how, the criteria and when they were set, what we found, and what the release still gets wrong. If we withhold a detail, such as a test that would work as instructions for an attack, the summary will say so and why.
- Scope
- Brello for Mac, Brello SI, Brello releases after 1.0.0
- Check
- The evaluation summary, published with the release: Brello for Mac’s is in section 09 and its system card. The first ten minutes and Safety and privacy set out the approach.
Commitment 05
We will ask before Brello spends money, sends a message or deletes something on your behalf.
Brello for Mac keeps this in code, and has no way to spend money or send a message (section 9.2). Brello SI is designed to draft, suggest and prepare work for you. It will not spend money, send a message or delete anything on your behalf until it has shown you the action in plain terms and you have confirmed it.
- Scope
- Brello for Mac, Brello SI
- Check
- Undo everything sets out what each question shows and what a yes covers. For Brello SI, the architecture description will set out the confirmation step, and the evaluations under commitment 04 will test it. An action taken without your confirmation is a security issue to report to security@brello.ai.
Commitment 06
We will build Brello to say when it isn’t sure, and to cite its sources.
Brello for Mac does both in code: when it cannot tell what a request means, it says what it could not tell and changes nothing, and a summary or a research brief is made of quotes, each checked word for word against the source it names. Brello 1.0 does both by instruction. Its system prompt says: “If you are not sure about something, say so instead of guessing.” With web results, the model is told to cite them inline, like [1] or [2], and each citation links to its page. An instruction is not a guarantee: a small model can still be wrong.
- Scope
- Brello for Mac, Brello 1.0, Brello SI
- Check
- Code first, model second shows what Brello for Mac says when it cannot tell, and how each quote is checked. This section quotes Brello 1.0’s instruction. Brello SI’s evaluation summaries will report how often it says it isn’t sure when it should.
Commitment 07
We will let you see, correct, export and erase what Brello remembers about you.
Brello SI is designed to carry long-term personal context. It will not remember anything about you beyond a single chat unless you can see, correct, export and erase what it holds.
- Scope
- Brello SI
- Check
- Long-term memory never comes without the four controls, and the architecture description will say where that memory is stored.
Commitment 08
We will make Brello SI’s privacy verifiable by independent researchers.
Brello SI is designed so that independent researchers can verify what runs, where it runs and what it keeps, and we will publish what they need before anyone outside the team uses sealed compute.
- Scope
- Brello SI
- Check
- The architecture description (section 4) will describe how a device accepts only software published in a public transparency log. Researchers can report what they find to security@brello.ai.
06
Five things we will not do
These lines bind Stuvio, and like the rest of this charter they change only through the process in section 7.5.
We will not sell, rent or trade your information.
- Check
- Section 9 of our privacy policy says the same. Brello for Mac sends us none of your files, and Brello 1.0 none of your questions, photos, answers or chats.
We will not build advertising profiles, or let anyone else build them through us.
- Check
- As for commitment 02: Brello for Mac, Brello 1.0 and this website contain no analytics or advertising software.
We will not widen what we collect without telling you first, in plain words.
- Check
- A note on our news page, published before the change takes effect.
We will not release a new capability that we haven’t evaluated.
- Check
- The evaluation summary required by commitment 04: Brello for Mac’s is in section 09.
We will not imply an endorsement we don’t have, or a capability we haven’t shipped.
- Check
- Our research says how and when each number was measured, and the system card lists what Brello for Mac still gets wrong. A statement that breaks this line can be reported to press@brello.ai.
07
Accountability mechanisms
Five mechanisms let people outside Stuvio check whether we keep this charter. Each says how it works in practice for the products this version covers.
7.1
Published architecture
We will keep a current, dated technical description of how Brello handles what you give it: what runs where, and what each part can see.
- In practice
- For Brello for Mac, Private by construction, Safety and privacy and the system card; for Brello 1.0, our privacy policy. Brello SI’s comes before anyone outside the team uses it (section 4).
7.2
Published evaluations
We will publish the evaluation summaries that commitment 04 requires, with every release of Brello SI and every new capability in any Brello release.
- In practice
- Brello for Mac’s evaluation summary is in section 09, and in full in its system card.
7.3
Transparency reports
We will publish a report on the legal requests for user information that we receive, by category, and how we responded: the first before anyone outside the team uses Brello SI, then at least once a year.
- In practice
- Our servers keep none of your files, questions, photos or chats, so a legal request could reach only what you send us by email and the purchase details Polar shares with us when you buy Brello for Mac (privacy policy, section 5).
7.4
Access for independent researchers
We will keep an open route for security and privacy researchers to report what they find, with a safe harbor for research done in good faith.
- In practice
- security@brello.ai, for Brello for Mac, Brello 1.0 and this website, and the security.txt file at /.well-known/security.txt.
7.5
Plain-language notes on changes
If this charter changes, we will publish the new version before it takes effect, with a dated note on what changed and why, and a redline against the previous version. Earlier versions will stay available at their own addresses, and no change will apply weaker terms to anything you have already shared.
- In practice
- Version 1.1 is dated in section 11, with its note; version 1.0 keeps its own address, and the redline marks every change.
08
Where the commitments apply
Brello for Mac is an app for the Mac, from brello.ai. Section 09 sets out the commitments it keeps, each with its check, and its evaluation summary.
Brello 1.0 is an app for Android and iPhone, on Google Play and the App Store. Its three models are built on open models from Google and Alibaba, released under Apache 2.0, and Brello is not affiliated with or endorsed by either company.
Brello Super Intelligence is our research direction. All eight commitments apply to it before anyone outside the team uses it. Table 1 shows how they apply to Brello 1.0.
| Commitment | Brello 1.0 |
|---|---|
| 01 No training on conversations | In effect |
| 02 No advertising | In effect |
| 03 Only what a task needs | In effect |
| 04 Evaluation before release | Partly. Applies to new capabilities. Version 1.0.0 predates the charter and has no published evaluation. |
| 05 Confirmation before acting | Not applicable. Brello 1.0 can’t spend money or send messages. |
| 06 Uncertainty and citations | In effect, by instruction, without a guarantee. |
| 07 Control of memory | Partly. Version 1.0.0 kept no memory across chats. Since version 1.0.2, Brello can remember what you tell it, on the phone; you can see, add and erase each item or turn memory off, but not export it. Chats can be read and deleted, one at a time or all at once, but not exported. |
| 08 Independent verification | Not applicable. No Brello server takes part in an answer, so there is none to verify. |
09
Brello for Mac
Brello for Mac makes the Mac easier, and its agent does the work you ask for on it, from an expense report to a tidy Desktop to a setting changed. It is the first Brello that acts on your behalf, so it keeps this charter in code.
Its own code reads each request first, and Apple’s on-device model reads the rest. Six commitments shape all of its work, each with the commitments above that it keeps and a way to check it.
9.1
It thinks on your Mac.
Brello reads your request and plans the work on the Mac, with its own code and Apple’s on-device model, and makes images there with Apple’s Image Playground. It never uses Apple’s cloud model, has no account, and sends no analytics or crash reports.
- Keeps
- Commitments 01, 02 and 03
- Check
- Brello’s privacy tests read every source file on every build, and fail if network code appears outside the one module that may reach the network or if Apple’s cloud model is named: how it is checked.
9.2
It asks first.
Before Brello deletes anything, quits an app, restarts the Mac or empties the Trash, it shows exactly what will happen, every item named, and waits for your yes. It asks once before a request first needs the internet. A no changes nothing, and while nobody is at the Mac, nothing is deleted and nothing goes online. It writes email as a draft for you to send, and has no way to spend money.
- Keeps
- Commitment 05
- Check
- Undo everything shows what each question names and what a yes covers. A change made without the yes it needed is a security issue to report to security@brello.ai.
9.3
Every change can be undone, and anything final is named before you say yes.
Moves, renames, copies, new files, deletions, settings and routines can all be undone, even after a restart, and what Brello deletes goes to the Trash, where Undo puts it back. What cannot come back, such as emptying the Trash or a restart, is labeled before you say yes.
- Check
- Undo everything lists the way back from each kind of change, and the benchmark that checks it byte for byte.
9.4
Code checks the work.
Brello never takes the model’s word for what it did. Code checks every change on the disk before the reply says done, reads every document back before keeping it, reads every setting back from macOS, and checks every quote in a summary or a brief word for word against its source. The model writes; code decides what is safe.
- Keeps
- Commitments 04 and 06
- Check
- Code first, model second shows each check, and the evaluation below scores every run by what it left on the disk, never by what Brello said.
9.5
Every request that leaves is in the ledger.
The Privacy page lists every request that leaves your Mac: where it went, when, and what it carried. The line is written before the request leaves, and if it cannot be written, the request is not made. A request carries only words you typed.
- Keeps
- Commitments 01 and 03
- Check
- Compare the ledger with any network monitor. A request that leaves the Mac without its line is a security issue to report to security@brello.ai.
9.6
It learns nothing from your data.
Brello keeps no record of your approvals, refusals or undos to learn from, and nothing you do in Brello is sent to us to train a model. The one model inside the app, which finds your work by meaning, is an open model used as it was released: your files fill the index on your Mac, and never train it.
- Keeps
- Commitment 01
- Check
- The system card names the model and its license; the ledger, compared with any network monitor, shows no request carries your work to us.
Evaluation summary
Commitment 04 asks, before release, for what we tested and how, the bar each result had to clear and when it was set, what we found, and what the release still gets wrong. This is Brello for Mac’s; the system card has it in full. The first-use suite and every held-out set were written before their first run.
| What we tested | The bar | What we found |
|---|---|---|
| First use: 250 requests a new person types in their first ten minutes, each played on the whole product in its own made-up home, on the command line and in the app window | Each handled as a good agent would, by what the run changed: answered, asked about once, done, or plainly refused | 250 of 250 on both, with no wrong action and no refused request; played as a Mac without the agent, 250 of 250 again, 145 done by code alone |
| Work done end to end: 65 tasks, three trials each | Every run reaches its goal, and removes or makes nothing it was not asked to | 195 of 195 runs |
| Undo, after every run that changed something | Back as it was, byte for byte | 138 of 138 runs |
| Routing: 64 requests about storage, the internet and research write-ups, and their near misses | Every request sent where it belongs | 64 of 64 |
| Answers from your work: 35 questions about a made-up work week, among 2,130 other items | Every quote found word for word in the item it names | 35 of 35 fully quoted, with 98.6% of the right items in the first five |
| Privacy: the tests that read every source file, on every build | Every test passes | Every test passes |
Where it falls short
- Given 21 requests about files worded afresh, after its reading of file work was finished, Brello carried out 11. For the other 10 it said what it could not tell and changed nothing.
- A request Brello’s code does not read whole is routed by Apple’s on-device model, a median of 1.18 seconds on the test Mac.
- An answer that rests on Wikipedia’s second article, not its first, shows that article without its picture.
- Among 2,130 other items about the same subjects, search by meaning found 18 of 36 answers in the first five.
- Text someone else wrote, in a file or a web page, still reaches the model. Code keeps it from changing anything your request did not name, at the price of more questions.
- The tests use made-up files, calendars, mailboxes and apps on one test Mac. Real work is messier, and we expect it to find failures these tests did not.
10
Open questions
We don’t yet know how far on-device intelligence can go, or how to make verifiable privacy simple enough for people who aren’t experts. Three questions shape the work this charter governs.
- How much can run on a device. We don’t know how much of Brello SI’s work will fit on a phone or a Mac, and how much will need sealed compute. The answer decides how often information leaves the device at all.
- Verification for people who aren’t experts. Researchers can audit a transparency log, but most people will rely on someone else’s check, and we don’t yet know how to make that reliance simple and well founded.
- Evaluating personal context without personal data. Commitment 01 rules out testing long-term memory on real people’s conversations, and commitment 04 requires testing it before release. We test with made-up work weeks, mailboxes and calendars, as Brello for Mac’s evaluation does (section 09), and we expect them to miss much of real life.
We will publish what we learn in our research.
11
Version history
Each version is listed with its date and what changed. Earlier versions are kept at their own addresses, each with a redline against the version that replaced it.
- Version 1.0, . First published.
- Version 1.0, . Editorial corrections to how the charter describes Brello 1.0: it is on the App Store and Google Play, for iPhone and Android; since version 1.0.2 it can remember what you tell it, on the phone. Brello Super Intelligence is described as our research direction. No commitment changed, and this was not a new version.
- Version 1.1, . Adds Brello for Mac, the first Brello that acts on your behalf, so that the charter binds it from its first day. Section 09 sets out the six commitments it keeps, each with its check, and its evaluation summary under commitment 04. Commitments 01 to 06 and lines 1, 2 and 4 name it in their scope, and section 07 says how each mechanism works for it. The old sections 09 and 10 are now 10 and 11. Nothing in version 1.0 is taken away. Published with Brello for Mac, and in effect from its release. Read version 1.0, and every change, marked.
- Version 1.1, . The check under commitment 02 now says what this website does: it counts visits with Google Analytics and measures our own ads on X with X’s pixel, each asked first where the law asks for consent. It still shows no advertising. Until this date the website set no cookies and loaded nothing from other sites. No commitment changed, and this was not a new version.
The Brello team at Stuvio · Version 1.1 · October 21, 2026