[your-domain]/publishingpolicy
A public, checkable record of your publishing standards. Host your policy with us, tell your readers to install the browser extension to verify it, and keep your site design clean. Readable by humans, structured for machines.
Bring the standards you already wrote, or write them here.
Free. No credit card required.
For Platforms · Publications · Institutions · Corporations · Nonprofits · Governments
A publishing policy is a public statement of the standards someone holds themselves to when they publish.
You write the rules. Whether you run a tabloid or an academic journal, what matters is stating your commitments clearly.
Move beyond hidden style guides. Your policy lives on a verified profile, built specifically for the audiences who rely on your work.
Every policy is timestamped and CC-BY licensed. Anyone can reference your commitments, in your current version and past versions.
Is it like a Privacy Policy?
Similar — and both work because of a public promise you can be held to. A privacy policy covers what information you collect from your users. A publishing policy covers what you put in front of them.
In a low-trust web, a published standard is your best defense.
Fact-checkers, ratings, moderation boards.
When your standards are internal, readers assume the worst. Every editorial decision looks like bias, and every mistake looks intentional. The argument is always about your motives.
Written by you, dated, in public.
When your standards are public and versioned, you control the narrative. Readers can see what you promised, and you have the receipts to prove you kept it. The argument becomes about the facts.
Nobody has to agree on what good publishing is. Only that you should do what you said.
A standard URL can't prove what you said yesterday. Our registry uses cryptography to give you the receipts—proving to your audience that your standards are rock solid.
Every time you publish, we generate a unique mathematical fingerprint of the exact text. It proves your policy is exactly what you claimed it was on that specific date.
All versions are recorded on a transparent timeline. When someone questions your standards, you can point to the exact historical record.
Readers don't have to take our word for it—or yours. They can independently verify the seal, turning your policy into an ironclad trust signal.
Verify ownership with a single DNS record. No engineering required.
Bring your existing standards, select a community template, or test drive the Sandbox.
Let readers verify you natively with the Browser Extension. No badge required.
Every organization that wants to give its audience a trust signal they can check.
Facebook, TikTok, Reddit, AI tools
Newsrooms, podcasts, newsletters
Federal agencies, municipalities, libraries
Universities, journals, think tanks
PR, marketing, internal comms
Foundations, advocacy orgs, faith orgs
Attorney advertising, bar compliance, legal marketing
FDA guidelines, patient communications, health information
Personal sites with their own domain
AI systems now read the web on people’s behalf — summarizing sites, comparing them, answering questions about them — and they look for signals they can actually check. Almost nothing out there gives them one. We’re building the infrastructure so they can. By structuring your standards as a machine-readable record, you ensure AI models understand your credibility, not just your content.
GET /.well-known/publishing-policy.json
If the platform you create on has nothing on record here, ask them to put it there. Audiences deserve a clear record of the public promises an organization has made — and the ability to see when something changes, and to understand the difference.
Free. No credit card required.