Privacy & removal

Civic Synthesis is a public civic prototype. Participation is advisory. Please avoid publishing addresses, contact details, or sensitive personal information.

What we collect

We store journal text, your optional display name, publication time, extracted needs and labels, and optional location. Real journal locations are stored in approximate 0.01° map cells (about 1 km), rather than exact coordinates. Public journal responses omit coordinates and tile IDs; the needs map shows aggregated cells. Location names or addresses you type into text are still public.

A signed anonymous browser ID cookie links new entries and civic votes to your browser. It lasts up to one year and is not proof of identity. We store an ownership hash for entry deletion. Clearing cookies, switching browsers, or cookie expiry can prevent access to your earlier entries and votes. Older entries without secure ownership records cannot be claimed by choosing their display name.

We also store votes, priority allocations, ideas, published proposals and discussion comments. Proposal drafts are kept in your browser until you publish them. Repository voting has separate browser or authenticated GitHub identities, PR revision records and audit history.

What is public and who processes it

Published journal text, display names, times, source labels and extracted needs are public, including through APIs that other sites can read. Published proposals and comments are public. Civic response totals are public; browser IDs and journal ownership hashes are not included in public entry responses. Your own choices are returned to your browser. Repository voting may display anonymous aliases and verified-vote audit records.

Journal text may be sent to a configured Gemini, OpenAI or Claude service to extract needs; without configured credentials, local extraction is used. Map requests go to the configured map provider. Hosting providers process requests, and operational logs may include request metadata. These providers may have their own retention policies.

How long we keep it

Published content and votes are kept until removed; there is currently no automatic expiry. Entries become less influential over time, but that does not delete them. Browser drafts remain until removed from that browser. Operational logs, backups and copies made by other people may outlast deletion from the active site; this prototype has no guaranteed backup or log deletion schedule.

Delete an entry or withdraw a vote

In the same browser you used to publish, open Journal, find your entry, and choose Delete my entry. Deletion removes the entry from the active feed, public APIs and future needs calculations. Independently published proposals retain their reviewed text and source entry ID; deleting the journal does not rewrite a proposal or its ballots.

On civic voting, click your selected choice again to withdraw it; save option changes with Save votes. Citizen proposals also let you remove your response. Withdrawal updates the current totals. Historical repository vote snapshots and revision records are separate audit records.

If you lost the publishing browser, have a legacy entry, or want other data removed, open a removal request with only the entry link or ID and the type of removal requested. GitHub requests are public and require a GitHub account. Do not repeat private text, cookie IDs, or other sensitive details. A maintainer must review requests that cannot be verified through the original browser; removal is not automatic. No private contact channel is currently published.