Houston Civic Prototypes
Privacy notice
Last updated September 26, 2026. This plain-language notice describes the data used by this landing page and by the CleanHOU and DayBurn prototypes.
Browsing and sign-in
You can browse the public maps without an account. CleanHOU and DayBurn ask you to sign in only for actions that need an account, such as submitting a streetlight report, confirming or sending a report, claiming a cleanup spot, joining a group, expressing interest in a project, or posting completion information.
Sign-in uses Google Identity Services. The apps verify the Google ID token on the server and use the verified email address, Google account subject identifier, and display name to create or find an app account. The account record can include the email, name, account timestamps, and the linked Google identity. These apps request identity information only; they do not request additional Google API access.
After sign-in, the app creates a server-side session. The session stores the app user identifier in PostgreSQL and is represented in the browser by an HTTP-only cookie. In production the cookie is Secure and SameSite=Lax, with a rolling maximum age of 30 days. Signing out destroys the app session and clears the cookie.
Information you submit
DayBurn reports. A report can include the light's map location and optional location accuracy, light type and count, description, pole or road information, timestamps, status events and notes, and up to three JPEG, PNG or WebP photos. Reports and non-hidden photos are designed to be public. A public report does not display the reporter's Google email or name.
CleanHOU cleanups. A claim can include your name, email and/or phone number, cleanup date, party size, group, and note. Completion information can include a note, bag count, volunteer count, hours, before and after photos, and completion timestamps. Group records can include a group name, description, members, and member contact details. Interest in a cleanup project can include your name, email, phone, party size, group, and message.
CleanHOU shows public cleanup status, names, group information, and completion details where the feature calls for them. Contact fields are restricted to the participant, relevant group owner or members, organizers, or other authorized staff views. The apps also record audit events for sign-ins and account actions so changes can be operated and reviewed.
Where data is stored
App account, session, civic report, cleanup, group, project, interest, completion, and audit records are stored by the app backends in PostgreSQL on the server infrastructure that runs these prototypes. Uploaded photos are stored on the server's persistent upload volume and are served from the app while the related record and photo remain visible. The prototypes do not publish a fixed automatic deletion schedule.
Other services
Google processes Google sign-in under its own privacy policy. The apps also load map or civic-data services, including Esri, OpenStreetMap, City of Houston 311 data, and DayBurn's Nominatim address lookup. Requests to those services are handled under their own policies.
Questions, corrections, and deletion requests
To ask what information is associated with your account, request a correction, or request deletion of account or submitted content, email tehtech1337@gmail.com. Include the app, the relevant report or cleanup identifier, and the Google account email used to sign in. We may need to verify that you control the account before acting. Some public civic history or audit information may need separate review before it can be removed.