Why Fairly exists.
The data economy is broken in a specific way: the people whose data fuels it don't see any of the money, can't meaningfully consent to its use, and can't reliably get it back. Fairly was built to fix that.
A different question, asked seriously.
Every consumer data product on the market is built around the same answer to the same question. The question is: how do we extract more value from user data? The answer is some combination of better tracking, broader collection, smarter inference, and more aggressive monetization. Users are an input. The deal is take-it-or-leave-it. The money flows past them.
Fairly was built around a different question.
What if users were partners in the data economy instead of products?
It's a simple flip with non-trivial consequences. If users are partners, consent has to be granular and reversible — not a buried checkbox. If users are partners, they have to share in the upside — not just see vague terms about how their data “may be used.” If the model is supposed to give back, the giving has to be structural — encoded in the schema, not promised in a press release.
We built the rest of this site as the answer to that premise. The product, the pricing, the charity model, the audit log, the consent toggles, the export-everything button, the published annual charity report — each of those exists because the alternative would have made the premise hollow.
Four disciplines we hold ourselves to.
The hard part of a privacy-first product isn't writing the marketing — it's holding the line when commercial pressure pushes the other way. These are the disciplines we use to hold it.
We design for verifiability, not trust.
Every commitment on this site corresponds to something users can check — a toggle in the dashboard, a row in the audit log, a number in our published annual report. Claims that can't be falsified don't make the marketing.
Consent is architecture, not interface.
Toggles in the product correspond to real branches in the code. Turning a category off doesn't hide it from view — it clears the underlying data and writes the change to an immutable log. UI alone doesn't constitute consent; structure does.
Users are partners, not product.
Users receive the full advertised reward for what they share — no platform fee deducted, no tier-based clawback. The 15% charity commitment is calculated on our annual profit, never taken out of what a user earns. When the model creates tension between commercial outcomes and user trust, we resolve it in users' favor — or we change the model.
Published numbers outrank private promise.
Charity disbursements are published openly every year, alongside the revenue and cost figures they were computed from. Audit logs and consent records are exportable in full. None of what we claim on this site depends on our word alone.
Built around one model.
Fairly is built around the long-term integrity of one specific model: consent-first data, paid fairly to users, with a structural commitment to give back. That model is more constrained than what most platforms in this space operate under. We accept the constraint because the alternative — softening the model under commercial pressure — would make the rest of the product hollow.
Concretely: we don't ship features that can't be defended on this site. We don't accept advertiser contracts that require working around user consent. We don't measure success in attention metrics or user-minutes. We measure it in consenting users, charity dollars disbursed, and the distance between what we say on this site and what the product actually does.
When commercial outcomes and user trust create tension, the user side wins or the model changes. That's not because we're noble — it's because the user side is the actual product. If we softened it, we'd be selling the same thing as everyone else, and we wouldn't be worth anyone's data.
If anything you encounter in the product contradicts what's on this site, it's a bug — and we want to hear about it.
Curious enough to try it?
Or have something to ask first?
Install if it makes sense. Email if it doesn't, or if anything about the page raised a question we should answer better.
[email protected]