0PN: the Online Openness Code of Practice
The rules the operator is bound by, stated as testable conditions rather than intentions. It is the counterpart of the Internet Transparency Code of Practice: the ITCoP specifies what controllers publish about themselves; this code binds the operator of the service that publishes it.
0PN is a registry brand operated by Global Privacy Rights (GPR). The 0PN Directory service is operated by TCIEG UK, which is itself also a registrant. GPR is the badge issuing authority only: credential attribution, not a controller or processor of the records.
Records are held in the United Kingdom under UK GDPR, with no dependency on Canadian adequacy and no UK Article 27 representative required.
did:web:0pn.orgissuer brand (0PN)did:web:0pn.org:operatorGPR accountability anchordid:web:tcieg.orgservice operator (Directory)Scope
Applies to every read path that serves controller transparency records, notices, receipts, event log entries, signal state and the register index. It does not apply to the operator dashboard or to write paths, which stay private and authenticated.
The commitment, six conditions
All six hold together. Any one of them failing makes the service closed, whatever the marketing says. Each is numbered so a record, the licence, or the constitution can cite a specific article.
0PN-1No fee to readNot a free tier. No read path metered by identity or by volume in a way that functions as a price.
0PN-2No login to readAuthentication on a read is identification before inspection, which is the posture this service exists to reverse.
0PN-3No contract to readNo click through terms, no API key, no acceptable use agreement between a person and a published record.
0PN-4No dependency on a paywalled standardEverything published can be parsed and checked using only freely available specifications.
0PN-5Machine readable and human readable as peersBoth forms published, neither one a paid or delayed upgrade of the other.
0PN-6No observation of the readerNo analytics on read paths, and no record of who inspected which controller beyond the stated operational floor below.
Who this code binds
This code binds the operator of the 0PN service. 0PN is a registry brand operated by and accountable to Global Privacy Rights (GPR) as interim UK accountable operator, with 0PN UK CIC (a community interest company, in incorporation) as the named successor UK registrar, authority, and accountable operator once it incorporates and accepts the role. GPR is the badge issuing authority only, meaning credential attribution, not a controller or processor of the records. Records are held in the UK under UK GDPR, with no dependency on Canadian adequacy and no UK Article 27 representative required. Every condition above binds the operating entity of the node serving the read; badge attribution binds GPR.
Checking a record without buying a standard
Although the record structure aligns with ISO/IEC TS 27560:2023, checking a published 0PN record shall not require purchasing any standard. The record structure is free to read: the ANCR TS 27560 free extension and the DPV vocabulary define the fields, and Convention 108+ provides the free legal anchor. Condition 0PN-4 is met by the free path, not the ISO document. A served 0PN JSON schema for machine validation is publication-pending.
Free validation path: ANCR TS 27560 extension, DPV vocabulary, Convention 108+. Served 0PN JSON schema: publication pending
Reads versus the alpha directory
Reads of published records require no login. Registration and write operations are permission-gated. During the alpha the public index is served partially: this is a named, dated, temporary exception (alpha window, review by 21 August 2026), not a standing authentication requirement on reads. Full unauthenticated read access to every published record is the launch target.
Conformance
A short conformance check is published alongside the code so a mirror or a second operator can claim to serve under 0PN and be tested on the claim. Conditions 0PN-3, 0PN-4 and 0PN-5 do not yet have a named automated probe: their check is honestly marked pending. The live probe wiring is a later phase.
Reader logging floor
No analytics on read paths, and no record of who inspected which controller beyond a minimal operational floor. Aggregate request counts only; no retention of addresses or identifiers beyond a short stated operational window; never used to profile inspectors, to build a picture of who is checking whom, or to notify a controller that it has been inspected. A controller learning who looked at its record would turn an inspection into an exposure, which would deter exactly the inspection this service is for.
Operational retention window: days: pending decision
Mirrors and stability of addresses
Anyone may take a full copy of the published read side and serve it, subject to the licence being finalised. A mirror should state its own last synchronisation time and must not represent itself as the origin. Because the event log is hash chained, a mirror is checkable rather than merely trusted. Addresses are stable: a moved address is a broken record, and where a rename is unavoidable the old address redirects permanently.
Licence
The record licence is being finalised. Until it is settled this page states that rather than imply terms that have not been agreed.
Record licence: being finalised
Change control
Changes are versioned and dated, with the previous version remaining readable. A change that narrows any of the six conditions is a breach of commitment, and since 18 August 2026 also a breach of the adopted charter, which entrenches this code. It is described as a breach, not as a revision.