Trust Center

Beacon Acceptable Use

The nMyCity Beacon API provides aggregate, place-level civic intelligence for research, planning, and product features — not for individual surveillance or automated harm.

Permitted uses

Aggregate neighborhood trajectory analysis and dashboards
Research, journalism, and civic transparency with appropriate caveats
Product features that surface block- or city-level trends with human review

Prohibited uses

Individual targeting, stalking, or enforcement against specific people
Automated lending, insurance, or employment decisions without human review
Uses that violate fair housing, fair lending, or equal credit opportunity law
Re-identification of individuals from aggregate civic records

Technical requirements

Every Beacon REST request must include attestation header X-nMyCity-Attestation: prohibited-use-accepted-v1 (legacy alias X-InMyCity-Attestation)
Beacon MCP (@inmycity/beacon-mcp) requires the same attestation via env NMYCITY_BEACON_ATTESTATION=prohibited-use-accepted-v1 (legacy alias: INMYCITY_BEACON_ATTESTATION) — the server will not start without it. Setup: Developer docs
Business, Analyst Firm, or Enterprise tier with recorded account attestation
Responses include prohibited-use notices; misuse patterns are monitored

Appeals & takedown

If you believe Beacon data is being misused, or your access was restricted in error, contact info@nmycity.com with your account ID, the endpoint involved, and a brief description. We review appeals within five business days and may suspend accounts that violate this policy.