Trust information should be specific to the product and deployment.

CivicTally is the portfolio brand for CivicReport and CivicMeeting. The products handle different public-information jobs, so privacy, accessibility, data, AI, security, retention, and service details should be evaluated for the product and configuration under consideration.

What we will distinguish

• Portfolio statement versus product behavior: an umbrella description is not a technical guarantee for every product.
• Public availability versus official status: a public community experience does not by itself establish municipal operation, authorization, sponsorship, or purchase.
• Navigation aid versus source: CivicMeeting summaries, topics, and transcripts help discovery; source video is used for verification.
• Public observation versus service request: CivicReport workflow, routing, visibility, and response expectations depend on the local experience and its stated terms.

Product-specific review

For CivicReport, review the local reporting experience, its privacy and terms notices, what becomes public, moderation behavior, and any stated municipal routing or response expectations.

For CivicMeeting, review available source coverage, freshness, categorization, AI disclosures, correction paths, collection notices, and the relationship between summaries or transcripts and source video.

Procurement and evaluation

Before making a product or deployment commitment, ask for the current scope of implementation, support, data handling, retention, accessibility evidence, security controls, subprocessors, service expectations, and exit or export options.

Those materials should identify what is available now, what is configurable, what remains under validation, and what is not included.