Explicit publication choice
The public heatmap queries observations that have publication consent recorded. Internal case data should not be assumed public.
Trust requires transparent processes, human review and careful decisions about which community insights should become public. This page explains the platform's design safeguards and what requires operational verification.
Publication decisions remain subject to documented municipal policy, permissions, consent and human moderation.
The public heatmap queries observations that have publication consent recorded. Internal case data should not be assumed public.
Public map groups require an approved moderation status and timestamp rather than publishing submissions automatically.
The map API uses reduced coordinate precision and a minimum group size. Individual reports, comments and identifiers are not returned by the public endpoint.
Fictional example markers appear only when a visitor deliberately chooses the labeled demonstration mode.
Citizen, representative, municipal and platform administrator permissions must be tested for each tenant before production use.
Webhooks, payment processing, messaging, AI and voice services require configured credentials, valid signatures and end-to-end tests.
Grouping three observations and rounding coordinates does not guarantee anonymity. A deployment needs a formal privacy impact assessment, publication policy, retention rules and review of sensitive or sparsely populated areas before releasing actual citizen data.
Municipal teams need trained moderators, consent procedures, access reviews, breach response processes and methods for checking published information. Responsible participation combines the system with local governance.
See the proposed pilot roadmap ↗