QSP Central ← Back to home

Security & Trust

Last updated: July 21, 2026

QSP Central handles the records that run a care agency — including protected health information (PHI) — so security is designed in, not bolted on. This page is written for the person your director forwards it to: it says what we actually do, in plain language. Questions or something to verify? Email qspcentral@gmail.com and we'll walk through it with you.

Encryption, everywhere

Your agency's data is isolated — enforced by the database itself

Every record carries your agency's identity, and PostgreSQL row-level security enforces the boundary at the database layer. The application connects as a least-privilege role that the isolation rules apply to, and the server verifies this posture at every startup. One agency's staff can never query another agency's data — even a bug in application code can't cross that line.

Access control

Everything is on the record

QSP Central keeps an append-only audit log: every create, change, archive, sign-in, and bulk view of client data is recorded with who, when, and what changed — including who opened which document. At the infrastructure level, AWS CloudTrail writes to write-once storage with a 7-year retention lock, and Amazon GuardDuty watches for anomalous access continuously.

Hosting & backups

HIPAA posture

QSP Central is designed to support HIPAA compliance: we sign a Business Associate Agreement with every agency before PHI is processed, and the safeguards above map to the HIPAA Security Rule's technical requirements. We're an early-access product and we say so plainly — if your compliance reviewer wants specifics beyond this page, we'll answer directly.

Reporting a concern

If you believe you've found a security issue, email qspcentral@gmail.com with the details. You'll hear back quickly — usually the same day.

See also: Privacy Policy · Terms of Service · Business Associate Agreement