2026.10 · Account scope clarification
Clarified
- Resolved an issue where elected officials believed disabling their account would disable observation.
- Account closure now states separately whether reviewer access, billing, or municipal enrollment is affected.
- Official responses remain attached to the original observation after account closure.
The Riverton council office correspondence informed this clarification. Read the released record →
2026.09 · Retention and review
New
- Fourteen-day organization-wide retention preset.
- Required approver and expiration for retention holds.
- Upcoming deletion view for records administrators.
- Export receipts now include purpose, approver, and file hash.
Improved
- Faster event list loading for accounts with more than 500 devices.
- More descriptive notices when a policy prevents a search.
- Additional SAML attribute mapping for department assignment.
Resolved
- Corrected a time-zone display issue in scheduled transparency reports.
- Fixed a rare case where a revoked API token could appear active for up to sixty seconds.
- Reviewer notes now accept more than 2,000 characters, following the Lakeside wellness review.
2026.08 · Corridor Heat
- Added aggregate corridor comparison with minimum-count privacy thresholds.
- Added scheduled aggregate reports for public transparency portals.
- Added reviewer warning before moving from aggregate data to event-level detail.
2026.07 · Integration controls
- Added signed webhooks and customer-managed signing-secret rotation.
- Added per-token geography and device-group restrictions.
- Added API activity to the standard audit export.
Planned deprecation: API version 2025-03 will stop accepting new integrations on December 1, 2026 and retire on March 2, 2027.