Five pages, one browser, no surprises.

The browser is the most intimate piece of software you own.

It sees every page you visit. Every search. Every half-finished sentence in a private doc. Every small act of curiosity you would rather not explain. We think a thing like that ought to be small, auditable, written by people who read the source, and never sold to you as a free product with a hidden price.

AliBrowser is a fork of Gecko (the engine Firefox uses). It strips out the parts that phone home, keeps the parts that make the modern web actually work, and ships under MIT. It is built by AliOne — a small, deliberate company in Istanbul — in the time between other things.

We are not trying to compete with Chrome. We are trying to make a browser that you can trust — the way you trust a good knife, or a faithful calendar, or a friend who doesn’t bring up your search history.

Promises, in writing.

We will:

• Keep the source code public, buildable, and forkable forever.
• Patch Gecko security advisories within seven days of upstream.
• Show you exactly what leaves your device. Spoiler: nothing.
• Maintain a public threat model, updated each quarter.
• Take donations. Refuse venture capital. Refuse acquisition offers.

We will not:

• Add telemetry. Ever. The kill switch would be a print statement, and we won’t write one.
• Default-on sync to our servers. Sync, when it ships, will be peer-to-peer.
• Bundle a “recommended” shopping, news, or search partner. You are not inventory.
• Ship a cryptominer in the installer. Yes, this has to be said.
• Run growth-hacked onboarding. The first screen is the URL bar.

What we collect, what we don’t, and why.

Nothing leaves your device unless you, the human at the keyboard, explicitly send it. There is no analytics SDK, no “anonymized” telemetry, no crash reporter that pings a server, no A/B testing framework. There is no background process phoning home to check for updates — updates check in when you open the app, and only then, and only against the GitHub releases endpoint, which you can read.

We keep no data. There is no analytics, no telemetry, no user database. The only thing that exists is the code and this page. That is the entire data policy. It will stay that way.

When you install AliBrowser, the only outbound network request the app makes is the one you make — to the URL you typed. We have verified this on a clean machine with a packet sniffer and a notebook. It is, in a meaningful sense, a private browser.

The threat model is published on the almanac and updated every quarter. The current version is dated 2026.Q1. Read it. Disagree with it. Send a patch.

How a free browser stays free.

AliBrowser is and will remain free of charge, free of ads, free of telemetry, and free of “pro” upsells. There is no business model that requires your data. The business model is small and boring, on purpose.

The funding, in order of size:

• Donations from people who use the browser. Roughly $4,200/month at the time of writing.
• A small grant from the Open Source Collective, earmarked for security audits.
• Personal savings. Mine. The rest of the runway.

There is no venture capital. There will be no acquisition. If, at some point, the donation total is not enough to keep the lights on, we will say so — publicly, with a date and a number — and ask the people who use the browser to chip in. The whole budget fits in a spreadsheet you can read.

If you would like to donate, the link is in the footer. It is a plain Open Collective page. We will not email you about it.

Pull requests, opinions, and one specific spreadsheet.

We are a tiny project. The list of things that would actually move the needle is short, and we keep it short on purpose.

• File issues. Especially the gnarly, reproducible kind, with a HAR file.
• Translate. We have a Weblate, and the strings are short.
• Read the threat model. Send a patch if you find a hole.
• Run the alpha on a weird machine. ARM, PowerPC, an old ThinkPad, your cousin’s PC.
• Tell a friend. Or don’t. There is no list, but word of mouth works.

If you would like to write code, the good first issues are tagged good-first-issue on the repo. None of them are glamorous. Several of them are important.