Community Map

Community Mapping Data & Privacy Policy

This Privacy Policy outlines our commitment to user privacy and our philosophy regarding the collection and use of non-personal data gathered through our platform, which facilitates Community Mapping. We believe that data is a good thing when handled responsibly and applied toward public benefit.

1. Our Commitment to Privacy and Low Friction

We prioritize privacy and a low friction experience for all participants.

No Storage of Private Information:

We are committed to the principle that we will not store private or personally identifiable information (PII). Our system is designed to facilitate community contribution without requiring traditional accounts or storing personal identifiers.

"No Login" Experience Security:

While we aim for a low-friction experience, the use of "no login" via magic links still involves an authentication flow. To ensure maximum privacy and security without storing private information, we implement technical fixes to protect users:

  • We use short token TTLs (time-to-live).
  • Tokens are generally limited to one-time use.
  • We employ IP and User Agent binding.
  • We utilize security services (such as Cloudflare Turnstile) and implement rate limits by IP and category to maintain security.

2. The Value and Purpose of Gathered Data

The data we generate is geospatial data produced through collaborative group work. This data is not personal; it is designed to serve the community mission.

Data is a Tool for Community Improvement:

We strongly emphasize the value of the information gathered for the benefit of the community. Community Mapping is defined by the intentions of EDUCATION, ENGAGEMENT, and EMPOWERMENT.

The data collected is essential for the following purposes:

  1. Issue Resolution and Analysis: Using mapping technology to identify, understand, analyze, resolve, and disseminate community issues.
  2. Empowerment: Participants are equipped with information or data to apply to a community problem or issue.
  3. Education and Engagement: Allowing participants to learn about issue(s) important to their community and become more actively engaged in public processes.

3. Use of Front-Facing Data for System Improvements

The geospatial and usage data generated through this collaborative process is continuously leveraged for system and community improvements. This front facing data should be used for improvements.

  • Platform Optimization: Aggregated data informs necessary technical enhancements, ensuring a better user experience, such as addressing potential lag from heavy zooming on mobile devices or optimizing data storage using PostGIS with GiST indexes.
  • Performance and Scalability: We use aggregated usage data to make key decisions regarding the geospatial stack, such as fixing clustering issues using server-side queries, or shoring up edge-to-DB latency by choosing optimized regions and using caching.
  • Enhancing Community Service: Improvements are made to better facilitate the core community mapping process, ensuring the data generated is reliable and available for community analysis and dissemination.

Last updated: October 16, 2025