Clear about what we build — and how.

We collect as little personal information as each product needs, and we design public-facing tools so residents can participate without identifying themselves.

• CivicReport does not require residents to create an account or provide a name or email address to submit a report.
• Resident notes and photos are screened before they appear publicly; staff can hide or remove content from the dashboard.
• Planning scenarios in CivicMaps are private to authorized accounts by default.
• Each public application publishes its own privacy policy and terms describing exactly what it collects and why.

Staff tools and private plans sit behind authenticated sign-in, and public pages show only what is meant to be public.

• Administrative tools, such as the CivicReport dashboard, require staff sign-in.
• CivicMaps scenario editing and collaboration require an authorized municipal account; a public guest view, where enabled, shows reference data only.
• Public forms, including this website’s contact form, use automated spam and abuse protection.
• Access for staff is set up during implementation and can be changed as your team changes.

Our products are built on information your municipality already publishes, and we make sources visible so anyone can check them.

• CivicBudget cites the official budget documents behind every figure.
• CivicMeeting links each meeting to its source recording and official minutes, and vote records cite the page they come from.
• CivicMaps shows the source and stated limitations of each reference location.
• We discuss data ownership, retention, and export expectations with each municipality before launch.

AI helps make long meetings navigable. It never replaces the official record.

• AI-generated summaries are labelled as such, may contain errors, and direct readers to the source recording.
• Summaries and newsletters are never presented as official meeting minutes.
• Vote records are drawn from official minutes, not inferred from AI summaries.
• Residents can report errors so they can be reviewed and corrected.

Public information should be usable by everyone. We design our products and this website following WCAG 2.2 AA practices.

• Semantic structure, keyboard navigation, visible focus states, and sufficient color contrast are part of our design standards.
• Public tools are designed to work on phones, without app downloads.
• We do not currently publish a formal accessibility conformance claim. Ask us about testing for the product and configuration you are evaluating.
• If you encounter an accessibility barrier on any CivicTally site, please tell us so we can fix it.

We want municipalities to evaluate CivicTally with clear, accurate information.

• We can describe product scope, implementation steps, staff involvement, and data handling for your evaluation.
• We clearly separate what a product does today from what depends on your available records or configuration.
• We don’t list certifications, guaranteed uptime, or contractual commitments on this website. If your process requires specific documentation, ask us and we’ll tell you plainly what is available.
• Pricing is discussed directly, once we understand the product and scope you need.

civictally.com is a static marketing site. It does not use advertising trackers.

• When you use the contact form, we receive the information you enter — name, work email, organization, role, product interest, and message — and use it only to respond to your inquiry.
• The contact form uses Cloudflare Turnstile to protect against spam and automated abuse.
• To ask about or remove information you’ve sent us, email sales@civictally.com.