01
Where our facts come from
Every statement we make about Brello 1.0 traces to one internal reference, compiled from the app’s source code at version 1.0.0 (commit 18dc2f5, 4 October 2026).
The reference records what the app does, the numbers it uses and the text it shows. Where the reference and the app disagree, the app is right: we correct the reference, then the pages that rely on it. We describe Brello 1.0 in the present tense, as it ships, and quote its interface exactly, in quotation marks and in its own spelling, so the last setup step is ‘Optimize for this phone’.
Privacy statements stay within what the app does. Wherever we mention web search, we say what leaves the phone: the search text and the page requests, which the search engine and websites receive as normal requests, including the phone’s IP address. So we don’t describe web search as hiding who is searching, we don’t say that Brello never goes online, and we make no encryption claims, because the app makes none.
02
How we describe work in progress
Brello Super Intelligence is in development, so we describe it only as intent: what it is being designed to do, never what it does.
We write about it with intent verbs, such as ‘is being designed to’, ‘we intend to’ and ‘will’, and we give it no results, benchmarks, release dates, partners, customers or user experiences. A single sentence never mixes what Brello 1.0 does with what Brello SI is designed to do. Table 1 lists the labels that mark the difference.
| Label | Meaning |
|---|---|
| In Brello 1.0 | Shipped in Brello 1.0, version 1.0.0. Written in the present tense, with the app’s real numbers. |
| In development | Being designed for Brello Super Intelligence. Written with intent verbs, with no results or dates. Glossary entries of this kind are marked ‘Brello SI: intended, not shipped’. |
| Planned | A process or safeguard we intend to put in place for Brello SI, with a date only once we have committed to it. |
| System description | A research article that describes how Brello 1.0 works, as built. |
| Design note | A research article that sets out design intent for Brello SI. It opens with a line saying that it describes intent, not results. |
We use absolute dates, such as ‘5 October 2026’, and give no forward date that we haven’t committed to.
03
How we write comparisons
Every statement about another company’s product quotes or closely paraphrases that company’s own published page, links to it and gives the date we checked it.
If we can’t find such a source, we don’t guess: the cell says that the provider’s documentation doesn’t state it, with the date we looked. We include the rows where the other product is stronger, sourced the same way, and we use no logos, no adjectives about competitors and no speculation about how another company works internally.
Each of our comparisons shows when its sources were last checked. We re-check them at least every 90 days and whenever a provider changes its policy, and log each check in the page’s version history. Comparisons appear only in that section. Research articles and Learn explainers don’t compare Brello with named products, though they may cite another company’s published work as a reference, with credit.
04
References and citations
We cite only works we are certain exist, and we prefer primary sources: specifications, papers and official documentation.
Research articles number their references, giving the author or organisation, title, venue, year and link, with the date we accessed each web page, and end with a suggested citation. Learn explainers list their sources. Technical pages link to the Brello 1.0 system card for the full description of how the app works.
Brello is built on open models from Google and Alibaba. We name each base model with its owner and licence, for example ‘Brello Vision is based on Gemma 4 E2B by Google, released under Apache 2.0’, and we state that Brello is not affiliated with or endorsed by either company. We don’t place their logos beside ours or describe them as partners. Our licences page credits the open-source work Brello and this website use.
05
Numbers and units
Sizes are decimal, as they are in the app: 1 GB is 1,000,000,000 bytes, and 1 MB is 1,000,000 bytes.
Where precision matters, we give the exact byte count once: Brello Core is a 977 MB download (977,184,032 bytes). We use the app’s own figures and mark estimates as estimates, so Brello Core uses about 1.95 GB of storage once its speed cache is built.
We don’t state user numbers, speed comparisons or accuracy rates that we haven’t measured. When we publish a measurement, we give the method, the sample size, the date and which direction is better, and we never present a base model’s published scores as Brello’s. Dates appear in full in the text, such as ‘5 October 2026’, and in ISO 8601 form (2026-10-05) in page data and feeds.
06
Screenshots and demos
Screenshots on this site are captures of Brello 1.0 running on an Android phone, and animated demonstrations are labelled as demos.
In each screenshot, the Android status bar (time, signal and battery) is blanked in the screen’s own background colour. Apart from that, the images are only resized and compressed: we don’t alter what the app shows. Our press kit has the same screenshots.
Animated demonstrations, such as the chat on our home page, are scripted recreations of the Brello 1.0 interface built for this website, and each is labelled as a demo where it appears. Figures and diagrams use the app’s real parameters, and a figure about Brello SI shows a design, not a measurement.
07
Corrections and version history
When we get something wrong, we correct it openly: the page records what changed and when, and we never change a number silently.
Research articles carry a version number. A material correction raises it, for example from 1.0 to 1.1, adds an ‘Updated’ date to the header and adds a dated line to the version history at the end of the article. Learn explainers keep the same kind of history. Corrections that don’t change meaning, such as a spelling fix, are made without a new version.
News posts aren’t rewritten after publication: a correction is added to the post with its date. Comparison pages record each source check, and any change it causes, in their version history. The Brello Charter changes only through a new version, published with a dated note and a redline before the change takes effect.
08
Bylines
Research articles and Learn explainers are published as ‘Brello Research’, news posts as ‘Brello’, and the Brello Charter is signed ‘The Brello team at Stuvio’.
Stuvio, the company that makes Brello, is named as publisher in citations and in the structured data that search engines read. We don’t name individual authors or give job titles or credentials: what we publish is the team’s work, and the team is responsible for correcting it. About Brello describes who we are and how we work.
09
Contact the editors
To report an error, email us with ‘Correction’ in the subject line, the address of the page and what you believe is wrong.
Email a correction. The link opens your email app with the subject filled in, and we use your address only to reply; our privacy policy explains how we handle email. If you can, include a source for the correct figure. We check each report against the app and our sources, and if the page is wrong, we correct it as section 7 describes.
Security and privacy problems in Brello itself belong on our security page, which explains how to report them safely. Journalists will find facts, images and contacts in our press kit.