Dekree handles records that are public when they should be and private when they must be. Here is how we keep that line clear, in plain English, for the IT director your supervisor will forward this page to.
Every table in Dekree carries an org_id and a row-level security policy. One township cannot read another township's data, even by accident, even via the API.
TLS for every request. AES-256 for data at rest. Customer documents in private storage with signed URL access for previews.
Every FOIA, every meeting, every document action is recorded with timestamp and user. Audit log entries are append-only — they cannot be edited or deleted.
Sensitive content gets redacted server-side and permanently. We scrub PII from error reports automatically. Original documents are admin-restricted.
Clerks draft. Supervisors approve. Council views. Each role gets only the surface area it needs. Invites carry one-time tokens.
Inbound webhooks verify their source via shared secrets and signed payloads. No deserialization of untrusted input.
No mystery vendors. Forward this section to your IT director and they can run their own checks.
Dekree is a Michigan-only company at the start of our scaling journey. Some certifications take time to earn responsibly. We are direct about what we hold today and what is on the roadmap.
For sensitive deployments, talk to us. We are happy to walk through specific compliance questions on a call.
Records governed by Michigan retention rules per category at upload.
Server-side redaction, append-only access logs, Sentry PII scrubbing.
Audit prep underway. Available in 2026 for enterprise customers on request.
Pursued as we scale into state-agency deployments.
Email security@dekree.ai. We respond within one business day. We do not pursue legal action against researchers reporting in good faith.
Talk to us about your security questions