Security
Shared responsibility, written down.
VisitSDK is software you run. It is not a hosted video service, and this page is not legal advice. Your privacy officer should read it against your own risk analysis.
| Data |
Where it lives |
| Live audio and video |
Amazon Chime, between the devices. The VisitSDK server does not see it. |
| Recordings and transcripts |
Your S3 bucket, encrypted with your KMS key. |
| Visit state |
Your DynamoDB table. An opaque visit id, meeting handles, and pipeline ids. No names and no chart data. |
| Webhooks |
Your backend. Visit reference, status, and S3 keys, signed with a secret you hold. |
| Logs |
Your CloudWatch Logs. Join tokens, meeting JSON, and secrets are not logged. |
What you own
- The AWS BAA for the account, covering Chime SDK, Transcribe, S3, KMS, DynamoDB, Secrets Manager, SQS, EventBridge, ECS, Fargate, the load balancer, CloudWatch Logs, and ECR.
- Patient notice and consent for recording, including two-party-consent states.
- Who may read recordings. The raw capture prefix is not a place for people to browse.
- Authorizing the user before your backend mints a token. VisitSDK trusts the token’s role.
- CloudTrail, GuardDuty, and someone who will answer an alarm.
Chime client telemetry is off by default in every SDK. There is no license server, so a running install has no reason to contact VisitSDK.