Resources
Editorial Principles
How we write — and how we decide not to write.
Why this page exists
Documentation philosophy
AI privacy is a noisy category. Most of the content in it is either generic explainer material, fear marketing or vendor puffery. Privian's docs, articles and resources are written to a different bar. This page is the bar.
We publish it so readers can hold us to it, and so the people who write these pages have something concrete to refer back to.
Principles
What we follow
Implementation grounded
Every technical claim on the Privian site maps to a real file, function or configuration in the codebase. We do not describe features that do not exist, and we do not imply behavior the implementation does not have.
Honest about limitations
Pages list what Privian does not do as explicitly as what it does. If a control is missing, planned or partial, we say so. A short list of honest limitations is more useful than a long list of optimistic claims.
Educational first, product second
Articles teach the topic before they mention Privian. If the topic does not actually need Privian, the article still does its job. The product fits where it fits.
No unsupported claims
We do not claim certifications we do not hold (SOC 2, HIPAA, PCI, ISO). We do not claim to block prompt injection. We do not claim governance, audit logging or self-hosted inference unless and until they exist in the product.
Plain language over jargon
We prefer the smallest word that works. We avoid stacked qualifiers, vendor-coined acronyms and security-theater vocabulary. If a sentence needs three adjectives to feel meaningful, it usually isn't.
Citable by reviewers
Pages are written so that an enterprise security reviewer can quote a paragraph as-is. That means short claims, named scope and dated updates — not marketing maximalism.
No fear marketing
Incidents and risks are described as case studies, not as scare tactics. We do not invent threat models to justify features.
Updated when the product changes
When the implementation changes, the pages that describe it change too. The 'Updated' date on each article reflects the last time we re-read it against the code.
Authorship
Who writes this content
Articles, docs and resources on this site are written by the Privian team. We do not invent founder credentials or external bylines. When a page is updated, the date on the page is the date the team last reviewed it against the implementation.
Corrections
If something is wrong
If a page on this site describes Privian or a related topic inaccurately, the page is the bug. We would rather hear about it — corrections take precedence over feature requests.