---
title: "Privacy"
description: "Privacy is defense by not knowing."
canonical: https://moa.giglabo.com/strategies/privacy/
locale: en
---

# Privacy

> Markdown twin of https://moa.giglabo.com/strategies/privacy/ — the same content as the HTML page, a fraction of the bytes.
> Every page of this site has one: append `.md` to any URL, or `index.md` to a directory URL.
> Site structure and the full page list for agents: https://moa.giglabo.com/llms.txt

Category: Defense · Role: Holds · Depth: 4

Gist: protection against information disclosure

## Moats

- [#7 Compliance](https://moa.giglabo.com/moats/7/) (direct, depth 3 · Drill rig) — Privacy law turns the promise into paper, processing agreements, certifications and audits, and a regulated buyer cannot sign with a vendor who lacks them.
- [#8 Brand and trust](https://moa.giglabo.com/moats/8/) (direct, depth 4 · Mine) — The record of never having read, sold or surrendered the customer's data is the trust asset; it takes years to form and one disclosure to lose.

## Summary

Privacy is defense by not knowing. A product that cannot read, sell or hand over what the customer puts into it is chosen by people who have something to lose from disclosure. The edge holds through the same two channels as security: the legal proof that you meet the rules on data, and the reputation of never having leaked or surrendered anything.

## How it works

The mechanism is a credible inability. A promise not to look is worth little; an architecture that cannot look, end-to-end encryption, no logs, data that never leaves the device, is worth a lot, because it survives your own change of heart, a buyer of your company and a subpoena. The customer fears disclosure to three parties: criminals, the vendor itself, and the state. A privacy product removes the first with security, the second with architecture, and the third with jurisdiction and a design that leaves nothing to hand over.

The edge is strongest where the rules are strict and the buyer is liable: a hospital, a law firm, a European company under GDPR chooses the vendor whose data-processing paper it can sign. Everywhere else privacy sells to the minority who care, and that minority is loyal for as long as you have never been caught.

## Why it holds — or only takes

Holds, through paper and through standing. The paper is #7: data-protection rules turn privacy into audits, processing agreements and certifications a regulated buyer must have, and each costs a rival the same year it cost you. The standing is #8: a messenger that has never handed over a message, a VPN whose no-logs claim survived a police visit, holds a belief in the buyer's head that a newcomer cannot buy and one disclosure destroys. The encryption itself holds nothing; a rival ships the same library in a week. What holds is the proof that you meet the rules and the record that you have never broken the promise.

## Do you have it

- Customers cite your data handling, not your features, as the reason they chose you.
- A court order or a data request came, and you had nothing to give; the case is public.
- Regulated buyers sign your data-processing agreement without redlines.
- Your no-logs, on-device or end-to-end claim has been audited by an outside party and published.

## How to dig it

- Design so the promise cannot be broken: encrypt at the client, keep no logs, hold no keys.
- Get the claim audited and publish the report; a promise nobody has checked is marketing.
- Put yourself under a jurisdiction and a legal structure that back the promise, and say which.
- Publish a transparency report on every request received and what was handed over.
- Sell first to buyers who are liable for disclosure; they pay for the paper, the rest follow.

## How it erodes

- One leak, one silent hand-over, one 'we were logging after all'; the record does not recover.
- Privacy becomes the platform default, encryption switched on by the device, and stops being a reason to choose.
- The law changes: a mandated backdoor or a data-retention order voids the architecture.
- The certification is rented and every rival has the same letters.
- Convenience wins: the customer wants the search, the sync and the AI that privacy forbids.

## Solo, without capital

A solo builder can ship a private product this quarter: on-device data, client-side encryption, no analytics, an honest privacy page. Those choices are free, and for the customers who care they are the product. What you cannot do alone is hold the compliance moat: certifications and audits are marked no for solo and cost a year. The trust half is partly yours; start the record now, publish every request you receive, and never quietly change the terms.

What the matrix says of its moats:

- [#7 Compliance](https://moa.giglabo.com/moats/7/) — Solo: ✗ no · Capital: ● high · AI: ↑ AI-resistant · Rent: ✓ rentable
- [#8 Brand and trust](https://moa.giglabo.com/moats/8/) — Solo: ~ partly · Capital: ◐ medium · AI: ↑ AI-resistant · Rent: ~ partly

## In nature, in business

Nature: —

Business: encrypted messengers, VPNs

- **Signal** — Signal encrypts messages end to end and keeps almost no metadata, so subpoenas have come back with little beyond the dates an account was created and last used.
- **Apple** — Apple put iPhone data behind on-device encryption and refused to build a bypass for the FBI in the San Bernardino case; the refusal became part of the brand.
- **Mullvad** — Mullvad runs its VPN without logs and takes cash by post; when Swedish police raided the office they left with nothing.

## Combines with

- [Security](https://moa.giglabo.com/strategies/security/) — A promise not to look is worthless if a thief can; the two are one architecture sold to the same buyer.
- [Transparency](https://moa.giglabo.com/strategies/transparency/) — A published transparency report is how a claim of not disclosing becomes a record a buyer can check.
- [Specialization](https://moa.giglabo.com/strategies/specialization/) — The buyers who pay for privacy are a narrow, liable segment; owning that niche is where the strategy earns.

[This strategy on the map](https://moa.giglabo.com/strategies/?view=lanes&hl=privacy)
[Map this combination](https://moa.giglabo.com/strategies/?view=lanes&hl=privacy,security,transparency,specialization)

## Fights with

- [Low-friction](https://moa.giglabo.com/strategies/low-friction/) — Client-side keys, no account recovery, no server search: the things that make it private make it harder to use.
- [Aggregation](https://moa.giglabo.com/strategies/aggregation/) — An environment built to collect broad participation collects broad data; privacy is a refusal to hold it.

[Map this tension](https://moa.giglabo.com/strategies/?view=lanes&hl=privacy,low-friction,aggregation)

## Source

Strategy taxonomy © kepano (Steph Ango), paraphrased with attribution. Role and moat mapping © Moat Atlas. https://stephango.com/

## Related

- HTML version of this page: https://moa.giglabo.com/strategies/privacy/
- Русский: https://moa.giglabo.com/ru/strategies/privacy/
- Previous: Security — https://moa.giglabo.com/strategies/security/
- Next: Durability — https://moa.giglabo.com/strategies/durability/
- Atlas: https://moa.giglabo.com/
- Catalogue: https://moa.giglabo.com/moats/
- Calculator: https://moa.giglabo.com/calculator/
- Strategies: https://moa.giglabo.com/strategies/
- Site map for agents: https://moa.giglabo.com/llms.txt