Skip to main content

Public record

Privacy policy

What civicstatus.com collects, what it doesn't, and exactly where your information goes. Written in plain language because that is how we intend to operate.

Last updated August 2, 2026

The short version

This website collects personal information in exactly one place: the pilot-inquiry form. What you submit there is delivered as an email to the founder and used only to respond to you. There are no analytics, no advertising, no tracking cookies, and no marketing lists. The demo application contains only fictional data.

What the pilot-inquiry form collects

If you submit the form, we receive what you typed: your name, work email, role or title, municipality or organization, an approximate count of active capital projects, and — if you choose to provide them — a phone number and a message. This is used to answer your inquiry and for no other purpose. It is read by the founder, not routed into a sales-automation system, and replies come from ian@civicstatus.com.

Inquiry emails are retained as ordinary business correspondence in that mailbox. If you would like yours deleted, email us from the same address and we will delete it.

What this site does not do

No analytics scripts. No advertising or ad pixels. No selling or sharing of personal information with anyone, for any reason. No newsletter you were silently added to.

Cookies

Public pages on civicstatus.com set no cookies — none for tracking, none for advertising, none for analytics. The only cookies this product ever uses are strictly-necessary session cookies created when authorized municipal staff sign in to the application, used solely to keep that person signed in. There is no cookie banner because there is nothing to consent to.

Service providers that touch the data

Three infrastructure providers process data on our behalf, each for a narrow purpose: Vercel hosts the website, Resend transmits the inquiry-form email, and Google Workspace operates the founder's mailbox where inquiries arrive. Standard server logs (IP address, request path) exist at the hosting layer for security and reliability; we also apply short-lived, per-network rate-limit counters to the form to deter abuse. We do not combine any of this into profiles.

All processing occurs in the United States. If you contact us from elsewhere, your information will be transferred to and handled in the United States as described on this page.

How the data is protected

The controls protecting this site and the product — transport security, a production content-security policy, rate limiting, database-enforced isolation — are described plainly on the security & data handling page.

Children's privacy

This site is a business service for municipal governments and their contractors. It is not directed at children under 13, and we do not knowingly collect personal information from children. If you believe a child has submitted information here, email us and we will delete it.

The demo application

Everything inside "Explore the demo city" — the City of Riverview, its projects, contractors, and submissions — is fictional and clearly labeled as such. No real municipal data exists anywhere in the product today. When CivicStatus takes on a real municipal customer, that engagement will be governed by a written agreement and a customer-data addendum to this policy, published here.

Your choices and requests

Email ian@civicstatus.com to ask what information we hold about you, to correct it, or to have it deleted — or with any question this page doesn't answer. You will get a reply from a person, not an automated system.

Changes to this policy

If this policy changes, the change and its date are published here; a material change to how inquiry information is handled will be noted prominently at the top of this page. The "last updated" date above always reflects the current version.

Questions a page can't answer? They go straight to the founder.

Discuss a municipal pilot