Security & compliance
SpiderLabs handles protected health information, so protecting patient data is part of how we run and how we launch. This page is written for the buyer and the compliance reviewer: the BAA process, how access to patient data is controlled and audited, how we handle data, and the gate before any live patient data flows.
At a glance
- We sign a BAA as part of onboarding, and a signed BAA is required before you go live.
- Access to patient content is audited: every transcript view and recording playback is logged.
- The minimum, by default: we store the least we need to run your front desk, and we never train shared models on your data.
- A hard gate for live patient data: it flows only after the BAA and a verified compliant environment are in place.
We describe only what we run
No vendor names on your screens
Your team works in one clean dashboard that shows SpiderLabs and your own business, with no other company’s branding, and access to patient data is audited. You get this by default; there is nothing to set up.
The BAA process
SpiderLabs signs a business associate agreement (BAA) as part of onboarding. The BAA is the contract that governs how we handle patient data for you under HIPAA, including our duties around safeguards, permitted use, and breach notification. A signed BAA is a launch requirement: no patient data flows until it is signed and on file. You can read the agreement itself on the HIPAA & BAA page.
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 your account is active and verified during onboarding.
Until both are in place, a business can still launch on staff confirm, with the minimal data handling below. See Getting started for how this fits into a launch.
No shortcuts on the gate
Audited access to transcripts and recordings
Reading a call transcript or playing a recording is a logged event. Each access is recorded with who viewed it and when, so there is an accountable trail over patient content. Content is fetched when a teammate opens a call rather than copied in bulk into the dashboard, which keeps exposure to the minimum and every view traceable.
How we handle data
We keep to the minimum needed to run your front desk and give you an audit trail. In practice:
- We store operational data (identifiers, timestamps, event types, appointment and callback status, and safe metadata), not bulk copies of raw transcripts or recordings.
- Access goes by role, 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.
Who owns the data
Your patient data is yours. We process it to run your AI front desk under the BAA, keep it to your own account, and return or dispose of it as the BAA sets out when our relationship ends. Questions about data handling and requests from the people whose data it is go to privacy@spiderlabs.ai.
Reporting a security concern
Everything a reviewer needs, in one place
- HIPAA summary: this page on one sheet, written to be checked.
- HIPAA & BAA: the agreement text itself.
- Trust center: how we protect data across the platform.
- Privacy policy and terms of service.
- Status page: how the platform is running right now.
Was this page helpful?
Keep exploring

