Protecting client records.
Where client records live, who can open them, and what gets logged when they do.
Sign-in takes a second factor.
Admins can require it for everyone, and idle web sessions end on their own.
- EncryptedOn the way in and at rest
- Your center onlyAnother center's record answers as if it does not exist
- By roleEach person's role decides what they can do
- LoggedWho opened it, when, and from where
Protected health information
Your center is the covered entity. Acquire is your business associate, under a signed business associate agreement.
We use records only to run and secure the service and meet legal obligations. We never sell them or use them for advertising.
What that covers
Names, dates of birth, assessment results, targets, trial data and notes.
If a breach occurs
If a breach of unsecured protected health information occurs, we notify your center as HIPAA requires.
How we work
We build and test on synthetic data, and on copies of production data that are sanitized before they leave production.
How long we keep records
While your agreement is in force. Then they are returned or destroyed as it sets out.
Each center is its own organization.
Every account and client belongs to one organization. A record from another center answers as if it does not exist.
Inside it, each person's role decides what they can do.
Scroll sideways to compare roles.
| Action | Organization Admin | BCBA | RBT |
|---|---|---|---|
| All roles | |||
| Record and undo trials | Yes | Yes | Yes |
| Read clients and their targets | Yes | Yes | Yes |
| Organization Admins and BCBAs | |||
| Write and change targets | Yes | Yes | No |
| Add and edit skills in the library | Yes | Yes | No |
| View reports | Yes | Yes | No |
| Organization Admins only | |||
| Set up assessments | Yes | No | No |
| Invite staff and assign roles | Yes | No | No |
| Read the audit log | Yes | No | No |
Acquire support
Acquire support uses a separate role to help you, and Acquire's own audit log records that access.
Other providers
A few providers run parts of the service, such as hosting and error monitoring. Each is bound by contract, and those that can touch protected health information have signed business associate agreements. The privacy policy names them.
Where client data lives
Acquire runs on Amazon Web Services in the United States.
Connections
Encrypted on the way in.
TLS 1.2 or newer, behind a web application firewall.
Application
Off the public internet.
The application runs in private subnets with no public addresses.
Database
Encrypted at rest and backed up.
A managed database on a private connection, with point‑in‑time recovery.
Documents
Private files, short-lived links.
Encrypted storage with no public access, shared through expiring links.
The audit log records each access.
Each entry says who did what to which record, when, and from where.
What it records
Sign-ins, including failed attempts; access to clients, targets and documents; recorded trials; target changes; staff invitations and role changes.
Who reads it
Organization Admins read it in the app.
Sign-in and shared iPads
Several staff may share an iPad, sometimes without a connection.
Sign-in takes a password and a second factor.
An authenticator app or emailed code, with backup codes. Admins can require it for everyone.
Repeated wrong passwords lock the account.
Too many failed attempts pause sign-in, and every attempt is logged.
An idle web session ends on its own.
After 15 idle minutes the session ends, enforced by the server.
Data on the iPad is encrypted.
Client data is encrypted, with its key in the iOS Keychain, and kept out of device backups. Trials waiting to sync are encrypted too.
The app locks when idle.
After 15 idle minutes it locks. Each person unlocks with their own PIN.
A lost iPad can be cut off.
We revoke it. When it next connects, it signs out and wipes client data.
- Assessment
- Teaching
- Maintenance