Privacy, at street level.
We collect the information needed to operate community surveys, accounts, moderation, and cleaning contributions. We do not sell personal information.
iPhone field notebook
The native app uses foreground location to suggest nearby blocks and sends coarse coverage queries to Supabase. Exact GPS coordinates are not stored in survey records. Capture metadata includes block ID, timestamp, image orientation, and a coarse self-reported location check. Native Apple Maps may process the viewed map area under Apple’s policies. Credentials use iOS Keychain; drafts and photographs remain in the private app sandbox until uploaded or discarded. Unsent work is lost if the app is uninstalled. Background GPS tracking is not enabled. Queue retries run while the app is open and resume on reopening. Account deletion can be requested from the app’s You screen and enters the same operator review queue as website requests.
Accounts and contributions
When connected, Supabase processes your account email and authentication information. Survey records include account ID, selected block, component ratings, notes, capture time, submission time, and photographs. Stripe processes payment details; StreetQ does not receive or store full card numbers.
Location and photographs
The optional map location button uses browser permission to center the map. Your exact location is not sent to our survey API or published. Images are re-encoded to remove EXIF metadata. Visible details can still identify people; do not include faces, plates, private interiors, or personal information.
Publication and service providers
Approved photos and aggregate StreetQ Scores are public. Pending photos, review requests, contact details, and payment records are restricted. Map tile requests disclose your IP address and viewed map area to OpenStreetMap’s tile service. Supabase, hosting providers, and Stripe process data needed for their respective services.
Cookies and analytics
Authentication uses necessary session cookies. This MVP has no third-party behavioral analytics or advertising pixels. The analytics interface is inactive until a provider is deliberately configured. The offline shell never caches profiles, admin pages, API responses, or uploads.
Retention and requests
Account and survey records are kept while needed to operate the service and resolve integrity disputes. Payment records may need to be retained for bookkeeping. Use a score challenge to flag personal information in a published observation. A verified account privacy-request flow is available on your profile when accounts are connected. Requests are reviewed before deletion so legally required records are retained.
Demo mode
Demo survey photos remain in your browser. Demo contribution forms validate your selection without saving the submitted contact details or creating a payment.
Updated September 8, 2026.