Skip to content
Green Blue Nexus

Privacy

This is a mostly static institutional site. It does not operate user accounts and does not designate a Secretariat address. The Join form and the readiness assessment do, however, now submit what you enter to the founding-phase Secretariat's system.

What is collected when you submit a form: the data you enter (e.g. organisation, name, role, note, optional email, and assessment answers), together with ordinary technical metadata (IP address, user agent, timestamp) for security and abuse prevention. Data is stored on this initiative's own server (a NAS behind Cloudflare), is not sold or shared with third-party advertisers, and is used only to follow up on your intent and to send notifications if you provide an email. To request access to or deletion of your data, use an existing working channel with the proposed Founding Convener.

The site also records aggregate page views (page path, referrer host, and timestamp) with no cookies and without storing IP addresses, only to understand usage.

The edge provider (Cloudflare) and the origin gateway may record ordinary technical request logs (IP address, user agent, path) for security and reliability. Gateway logs are not intended as a participant database.

Outbound links to setap.gbnexus.id lead to a separate readiness product with its own data governance. Visiting that product does not make this site the controller of readiness submissions.

There is no partner logo wall and no third-party advertising tracker installed by this site.

This notice will be updated again if the scope of data collection changes or when a public Secretariat address is designated.

Processing boundary: Join-form and initial self-check data remain in the GBN system and are not automatically transferred to SETAP B2. Any transfer or SETAP invitation requires participant notice and a stated processing basis. THC is the data controller for SETAP activity.

Asking for your data to be erased

No public Secretariat email address has been designated, so erasure requests go through a dedicated channel: Data erasure request. That page sets out what may be held and what happens after a request is sent.