The Flossy Organization
Privacy
Short version: we publish the issue, not the person.
This is a plain-language draft for residents. It is not legal advice and should be reviewed by counsel before it is treated as a final privacy policy.
What goes on the map
Each public report shows the issue type, an optional photo and description, an approximate location, the date, status, civic districts, and any timeline updates you or Flossy staff add. It does not show your name, email, phone, or the exact pin you dropped.
Location
The pin you confirm is stored privately so staff can follow up. The public map uses a short offset or a block-level point, and a label like “1300 block of East 93 Street.” Housing and noise reports are shown more coarsely because they often sit at someone’s home.
Photos
Photos are optional. Before they are saved they are re-encoded, resized, and stripped of EXIF metadata — including GPS. Do not photograph faces, license plates, or the inside of a home if you wouldn’t want that on a public map.
Who represents this block
Districts and officeholders are matched to the issue location, not your home. Messages to elected offices are written and sent from your own email. Flossy does not send mail on your behalf and does not store the body of those messages.
Voter registration
Checking registration is optional and happens only after you report. It opens the NYC Board of Elections site. Flossy does not ask for, infer, or store date of birth, party enrollment, or registration status. Use your home address there — it may be different from the issue location.
NYC 311
A Flossy report is not an official 311 request. 311 records on the map come from NYC Open Data. If you file with 311 yourself, you may attach the request number to your Flossy report so both can be tracked together.
Analytics
If analytics are enabled, they record coarse product events (for example, that a report was submitted) without names, emails, addresses, coordinates, or voter information.
Questions: theflossy.org