Privacy notice

Voluntary registration

Joining the Distribution Map is operator-initiated through the @thierry-gilgen-ict/engawa-map CLI only (for example npx engawa-map register after installing from npm). Engawa-powered websites do not phone home or send adoption data from normal application runtime.

Public listing purpose

The map is a community showcase of Engawa-powered public sites. Only sites in the LISTED state appear on this page and the public API.

Public fields

For each listed site, the registry may publish:

• Display name
• Canonical HTTPS origin URL
• Declared Engawa package versions
• Optional hints: framework, Bring Your Agent enabled flag, locale count
• Listing and update timestamps

PENDING and DELISTED records are not shown on the public showcase.

Site token model

• The CLI generates a site-scoped bearer token and retains it client-side (for example .engawa-map.local.json or ENGAWA_MAP_TOKEN in dedicated CI).
• Registration sends only a SHA-256 hash of the token; the server stores the hash only.
• The server never returns or logs the raw token.
• The CLI does not print the raw token on successful registration.
• Protected routes authenticate with Authorization: Bearer <raw-token>.

Lifecycle and retention

• New registrations start as PENDING until manually approved.
• Approved sites become LISTED and appear here.
• Delisting (DELISTED) removes public visibility immediately and revokes the stored token hash (NULL).
• unregister is not a hard delete: non-secret registry rows may remain under the v1 retention policy until maintainer deletion. A bounded hard-deletion period is not defined in v1.

Removal and contact

• Operators with a valid site token: use engawa-map unregister.
• Security-sensitive reports, private ownership, removal, or identity details: info@thierry-gilgen-ict.ch
• Non-sensitive public bug or abuse reports: GitHub issues on engawa-map-registry

Do not post secrets, site bearer tokens, or sensitive abuse details in public GitHub issues.

What we do not collect

• No visitor page-view telemetry on this showcase
• No MCP query logging, prompts, or Bring Your Agent session context
• No automatic crawling or HTTP fetch of listed canonical URLs
• No Traefik access logs retaining raw client IP addresses at the edge

Abuse and rate limits

The registry applies operational rate limits at the edge and application layer. Maintainers may delist abusive entries manually. There is no public admin HTTP API.