Digital Consent Hackathon · Montreal · Sept 4

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.

The event

Digital Consent Hackathon at Sensorica Montreal

September 4 · Sensorica, Montreal

A hands-on build day for engineers, designers, and privacy people who want to make digital consent real, not theatre.

We build the pieces of the transparency signal together: notice before identification, controller identification records, and notice receipts you can keep and verify. Bring a laptop, bring a question, leave with working code and a receipt you issued yourself.

  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.

Friday webinar
To be announced

Digital-ID Consent for Access Management, AI, and Age Assurance

An online session on how digital-identity consent works across access management, AI systems, and age assurance, and how the transparency signal binds them together. The date is being confirmed. Register below to be notified as soon as it is set.

Date to be announced. Register through the gateway below and toggle "notify me about next events".

Sign up with Trustparency

The gateway is the demo

Your signup is itself a one-factor notice. You see the notice before any field is asked, then you get a receipt you can keep and verify. That is the standard, working.

passport control · notice served before entry
Transparency Gateway Notice before identification Lv0 · self-asserted
ControllerGlobal Privacy Rights Public ID URIdid:web:globalprivacyrights.org CIR IDbaked snapshot Statusactive

Controller identifier and status are self asserted at Level 0.

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