PlatformSolutionsPricingSecurityAboutRequest a walkthroughSign in

Security & compliance

Compliance-first, by construction.

DaycareLogix handles sensitive data about children and aging adults, and federal reimbursement money. Isolation, access, and the audit trail aren’t features bolted on. They’re how the system is built.

Audit log entryTamper-evident
entityMealCount
actionupdate
actorcoordinator
before → afterhashed
timestamp08:41:07
chain hash7f3a…c1

Strict tenant isolation

Global query filters scope every record to its tenant, so one organization can never read another's data. Even background jobs and the kiosk pass explicit facility and tenant scoping, never an ambient default.

Role-based access

Six roles (owner, facility director, CACFP coordinator, classroom staff, auditor, and family) are enforced through authorization policies, in the nav, the API, and the command handlers alike. Access is never the client's decision.

Tamper-evident audit log

Every auditable change emits an append-only log entry with a hashed before/after state. Persisted enum values are append-only and never reordered, so the history you show an auditor can't be quietly rewritten.

Sensitive-data gating

Eligibility (Free/Reduced/Paid) is a classification, not a badge to flash. Category and income basis render only for users who hold the permission to view them, and are masked for everyone else.

CACFP audit-readiness

Meal counts captured at the point of service, checked against the meal pattern, validated for disallowances, and locked. Sponsor review and monitoring are built in, so the claim is defensible before it's filed.

Accessible by default

WCAG 2.1 AA contrast, real semantic controls, visible keyboard focus, a senior mode, and multilingual labels. State is never encoded by color alone: pills carry words, severities carry shape.

The rule underneath

The server is the authority. The UI only reflects it.

Locks, permissions, and gating you see on screen are conveniences. The design never implies the client is in charge. Meaning is enforced server-side, so a locked claim stays locked and a masked field stays masked no matter what a browser does.

Claim lifecycleenforced · server
Opendone
Data capturedone
Validationdone
Lockedread-only
Exported

Bring your auditor

See the audit trail for yourself.

We'll walk your compliance and IT teams through isolation, access, and the audit log in the product, not on a slide.