Transparency Gateway demonstration · from the Digital Consent Hackathon, Montreal, 4 September 2026

Build the transparency signal

A hands-on build day advancing digital consent and the Internet Transparency Code of Practice. Then register the way the standard demands: notice before identification.

Where this came from

The Digital Consent Hackathon at Sensorica Montreal

Held 4 September 2026 · Sensorica, Montreal

A hands-on build day for engineers, designers, and privacy people who wanted to make digital consent real, not theatre. The gateway below is what came out of it, and it is still running.

The day built the pieces of the transparency signal together: notice before identification, controller identification records, and notice receipts you can keep and verify. Everyone left with working code and a receipt they had issued themselves. The demonstration below is that work, kept running so anyone can walk the same three steps.

  1. Disclose who is accountable and what they intend to do, before any field is asked.
  2. Let the individual decide whether to identify, share, or refuse.
  3. Issue a receipt the individual keeps as evidence.
The campaign

Campaign for the Internet Transparency Code of Practice

The hackathon feeds a larger effort: the Campaign for the Internet Transparency Code of Practice (ITCoP). The Code sets a single rule for the open internet: transparency comes first. A controller must be identifiable, and structured notice must be served, before any identification or consent is asked of a person. It aligns with Convention 108+, ISO/IEC 27560, 29184, and 29100.

Notice first

Disclosure comes before identification. No surveillance first.

Inspectable

Every disclosure is machine readable and can be checked.

Receipts you keep

The individual keeps the evidence, not just the controller.

Sign up with Trustparency

Transparency Gateway Demonstration

This signup for the hackathon is itself a one-factor notice with a standard transparency signal. This first instance of the transparency signal displays that the Controller is not collecting, inferring and processing data, until you know who the Controller is, and where your data is going, so you can make the choice to trust yourself. Called Trustparency.

passport control · notice served before entry
Transparency Gateway Transparent first, for a consent-capable internet Lv0 · self-asserted

Before you sign up, review why your information is requested and the digital policy that governs this form. Global Privacy Rights identifies the accountable controller, the purposes for processing, and the applicable authority before any identification is demanded.

Notice typeFirst Factor Notice (1FN), minimum notice disclosure Accountable controllerGlobal Privacy Rights (did:web:globalprivacyrights.org) Lawful basisConsent RecipientTCIEG RetentionKept only for as long as the stated purpose is active NoticeController Identification Record v0.3.0, effective 2026-06-20

What each field is for

First namerequired
Administer your hackathon registration and address you. Lawful basis: consent.
Emailrequired
Administer your registration and reply about it. Lawful basis: consent.
TCIEG newsletteroptional
Send occasional transparency-standards updates. Separate affirmative opt-in. Lawful basis: consent.
Event notificationsoptional
Tell you about future events. Separate affirmative opt-in. Lawful basis: consent.
Register transparency badgeoptional
Start a Level 0 transparency badge for your own service. Separate affirmative opt-in. Lawful basis: consent.

Optional campaign updates are kept separate from the information needed to administer your registration, and each requires its own affirmative choice. No box is preselected.

Exercise your privacy rights

Computed in your browser and sent nowhere. Nothing here is logged, stored, or transmitted. This is the pre-identification surface: what is already visible before you enter anything.

Records notice acknowledgement only. An entry event, not consent. No identification is required to view this notice.
loading live CIR...