Privacy Policy
Last updated August 25, 2026Civron is a data hub for public safety agencies. This page explains, in plain language, what we collect, why, and what control your agency keeps over it.
Who this policy covers
This policy applies to Civron's website, our incident-management product, and anyone who submits a demo request. If you're a member of an agency staff using Civron day to day, this also covers the account and incident data your agency stores with us.
What we collect
We collect three kinds of information:
- Staff accounts: name, work email, role/title, and the agency you belong to. Your password is stored as a one-way hash; we never store it in plain text.
- Incident records: whatever your agency chooses to log: type, location, date, a written description, and optional details like injuries, fatalities, or a source. This is operational public-safety data your agency reports, not data we collect about you personally.
- Demo requests: if you fill out our "Request a demo" form, we collect your name, work email, agency, role, region, and whatever you write in the message field.
We don't run advertising trackers or sell data to third parties. There's no ad pixel on this site.
How we use it
Account and incident data exists to run the product for your agency: logging in, viewing your own records, and nothing more. Demo request details are used to reach out about scheduling a call and are not added to any marketing list without your consent.
Who can see your data
Your agency's incident data is scoped to your agency by default. No other agency using Civron can see it. Nothing is made public unless your agency explicitly turns on a sharing setting we provide for that purpose.
We use a small number of service providers to run Civron, including hosting infrastructure and, for demo requests, a CRM tool we use internally to keep track of conversations. None of them are permitted to use your data for their own purposes.
As Civron develops, our goal is to partner with government agencies too. When that happens, this section will expand with named subprocessors and formal data-processing terms, and we'll note the change below.
How we protect it
Login sessions use an httpOnly cookie, which means it can't be read by scripts running in your browser. That's a common way session tokens get stolen. Traffic between your browser and Civron is encrypted in transit.
How long we keep it
We keep your agency's data for as long as your account with Civron is active. If your agency stops using Civron and asks us to delete its data, we will, outside of anything we're legally required to retain.
Your choices
You can ask us to access, correct, or delete your personal account information at any time by contacting us below. If you're staff at an agency, your agency administrator can also manage this directly.
Changes to this policy
Civron is early. As we bring on pilot agencies and, eventually, larger government partners, this policy will get more formal and more detailed. When it changes, we'll update the date at the top of this page.
Contact us
Civron doesn't have a dedicated privacy contact yet. Reach out to the same address we use for everything else, and you'll get a real, direct answer.
kevon.studio@gmail.com