HIPAA summary
Our HIPAA controls on one page a reviewer can check. Each line names the control, how it is enforced, and where its limits are. For the longer version, see Security and compliance; for the agreement itself, see the HIPAA and BAA page.
At a glance
- The PHI boundary is enforced in code: outbound requests in the integration layer must pass a boundary check, and an automated test fails the build if one does not.
- Every transcript view and recording playback is logged with the account, the person, and the time.
- Raw transcripts and recordings are not stored by default. Content is fetched on demand, and that fetch is itself audited.
- Live patient data has a hard gate: a signed BAA on file plus a verified compliant data environment, for each customer, before any live PHI flows.
The summary
SpiderLabs acts as a business associate to the covered businesses we serve. The table below is the whole summary; the sections after it explain each line.
- Business associate agreement
- Signed at onboarding
- PHI boundary on integration calls
- Enforced in code
- Transcript and recording access
- Logged on every access
- Raw transcript or recording storage
- Off by default
- Subprocessor names on customer screens
- Never shown
- Dashboard access
- By role, for each account
- Training shared models on your data
- Never
- Live patient data
- Gated for each customer
The PHI boundary is enforced in code
Every outbound network request in our integration layer that could carry patient data must pass a PHI boundary check before it runs. The check confirms the destination is an approved endpoint for that kind of data. This is not a policy document: an automated test scans the integration code and fails the build if any outbound call skips the check.
Access to patient content is audited
Reading a call transcript or playing a recording writes an audit event that records which account, which person, and when. The trail is built so a practice owner or a reviewer can answer “who saw this patient’s content, and when?” without guessing.
Minimal storage is the default
Your team works in a clean SpiderLabs dashboard, while the heavier records stay with the voice service that produced them. By default we do not keep bulk copies of raw transcripts or recordings. What we store is operational: identifiers, timestamps, event types, appointment and callback status, and safe metadata. When a teammate opens a call, the content is fetched on demand through our own servers, the access is audited, and turning on any broader raw storage would be a deliberate change to the platform, never a default.
Access control and isolation
Dashboard access goes by role (owner, admin, member, viewer; see Team and roles), so each teammate sees only what their role allows. Each business’s data is kept to its own account by row level security in our database. We do not use your patients’ data to train shared models.
The BAA and our subprocessors
We sign a business associate agreement with each covered business as part of onboarding, and a signed BAA is a launch requirement. The agreement text is public on the HIPAA and BAA page. Beneath us, a signed BAA with our data platform provider is on file today, and business associate agreements with the remaining covered subprocessors in the voice and hosting stack are signed or in progress. We do not name subprocessors on customer screens, and we treat vendor coverage as a launch check for each customer: before live patient data flows for a new account, the coverage for that account’s stack is verified and evidenced.
Ask us where each item stands
The live patient data gate
For a new customer, live patient data is not switched on until two things are true: the BAA is signed and on file, and the compliant data environment for that account is active and verified during onboarding. Until both hold, a business launches on staff confirm with the minimal storage above. The gate is not optional, and we hold launches on it.
What we do not claim
- We do not claim certifications we do not hold. If a specific attestation (SOC 2, for example) matters to your review, ask us directly rather than reading between the lines.
- We do not claim that HIPAA compliance is a product feature you can buy. It is shared: our controls above, your BAA, and your own staff practices together.
- We do not claim every subprocessor agreement is filed until it is. The current state is always available from us on request.
Verify it yourself
The fastest check is to ask. Security questions, vendor status requests, and vulnerability reports all reach a monitored mailbox, and breach notification terms are covered in the BAA.
Security contact
security@spiderlabs.ai
For the longer version, read Security and compliance. For the agreement text, read the HIPAA and BAA page. For how data moves in practice, read Booking modes and Analytics and reporting.
Was this page helpful?
Keep exploring

