Security

MinnAI is built for Minnesota CFSS agencies, which means it holds protected health information about the people your support workers visit. This page describes the controls that are in the product today. It makes no certification claim: HIPAA has no certifying body, and this product holds no third-party security attestation.

• HIPAA-aligned safeguards
• BAA before any data
• HHAeXchange aggregator integration in progress

Client records stay in the United States, encrypted in transit and at rest. Access is limited by role, down to the individual worker. Every edit is stamped with who made it and when. Your data is yours. We do not sell it and we do not train on it.

Before any data moves

No subprocessor carries protected health information until its Business Associate Agreement is executed, and no real client data goes into a MinnAI environment until the agreement covering that environment is signed. Until then, every environment runs on synthetic seed data. Ask us for the current agreement and the subprocessor list at compliance@minnai.com.

Tenant isolation

Every table carries row-level security, evaluated by the database against the caller’s own token on every request rather than by application convention. A cross-tenant test is a merge gate: break an isolation policy and the build stops, so it cannot ship broken.

Where the data is, and what is encrypted

Client records are held in the United States, encrypted in transit and at rest. Fields that identify a person directly, a Social Security number among them, are encrypted at the column with a per-tenant key rather than relying on disk encryption alone, so they are not readable from a database dump.

Who can see it, and what is recorded

Access is limited by role, down to the individual support worker. Every write is stamped with who made it and when, and reads of protected health information are recorded as well. Audit metadata carries record identifiers only and never the health information itself, which is asserted by test rather than left to review.

Logs and error reports

Protected health information is redacted at the boundary, in both the logger and the error reporter, and that redaction is asserted by test. Credentials are held on a separate redaction list from health information, so nothing can be added to one and miss the other.

Integrations

Minnesota designates HHAeXchange as its EVV aggregator, and the integration with it is in progress rather than certified. Until certification passes, this site says “integration in progress” and nothing stronger. No payroll provider and no accounting system is integrated today, so none is named anywhere on the site.

Accessibility

Every colour pair in the product is checked against WCAG AA contrast by a test that fails the build below the floor, in both light and dark themes, and mobile body text is held to the stricter AAA ratio because a clock-in screen gets used outdoors on an inexpensive phone.

Reporting a problem

If you believe you have found a vulnerability or a data-handling problem, email compliance@minnai.com with enough detail to reproduce it. We will confirm receipt within two business days.