Security and privacy
YMSL Automations protects patient data with business associate agreements, TLS encryption, set deletion dates for AI scribe audio and transcripts, and nightly backups that are restore-tested every quarter.
Introduction
YMSL Automations LLC builds clinical automation for independent medical practices. Our automation platforms handle protected health information (PHI) across a wide variety of clinical workflows.
Core commitments
Practice data
- We process PHI as each practice's business associate, for the services that practice uses.
- Each practice's data is separated by account.
- On request, and when a contract ends, we return or destroy a practice's data as its business associate agreement (BAA) directs.
Security
- Every address that serves PHI requires TLS 1.2 or higher.
- Every AWS S3 storage bucket is encrypted by default and blocks public access.
- Every product offers multi-factor sign-in.
- Databases are backed up every night to a second region, and backups are restore-tested every quarter.
Privacy principles
Data ownership
Each practice controls its patients' data. We sign a BAA with the practice and use its data to run the services it has chosen. Our staff open a practice's data only when a support need requires it.
Encryption
Retention
AI scribe audio is deleted after 7 days and AI scribe transcripts after 90 days. Practice records are kept for the term of the contract.
| Data | Retention |
|---|---|
| AI scribe visit audio | Deleted 7 days after upload |
| AI scribe transcript at AssemblyAI | Deleted right after processing |
| AI scribe transcripts in our database | Purged at 90 days |
| Database backups | 400 days |
| Practice records | Term of the contract, then returned or destroyed as the BAA directs |
Security infrastructure
Cloud
PHI is stored in AWS United States regions. Primary storage runs in us-east-2 (Ohio) and backups are kept in us-west-2 (Oregon). AWS also runs Amazon Textract, which reads text from documents.
AI processing
Two AI vendors process PHI for specific tasks. AssemblyAI transcribes AI scribe visits and deletes each transcript right after processing. Anthropic provides AI processing.
Subprocessors
| Vendor | Role | BAA |
|---|---|---|
| Amazon Web Services | Hosting, storage and Amazon Textract, United States regions | Executed |
| Neon | Database | Executed |
| Anthropic | AI processing | Executed |
| AssemblyAI | Medical transcription | Executed |
Application security
Compliance and certifications
HIPAA
We work as a business associate under the HIPAA Privacy and Security Rules and sign a BAA with each practice. If a breach of unsecured PHI occurs, we notify the practice as the BAA and 45 CFR 164.410 require: without unreasonable delay, and within 60 days of discovery.
SOC 2 and other certifications
We hold no SOC 2 report or other security certification today. SOC 2 is on our roadmap. We complete security questionnaires and walk your reviewers through each control.
California practices
California adds state duties on top of HIPAA.
- The Confidentiality of Medical Information Act (CMIA) sets state privacy rules for medical information, and patients can sue under it directly.
- California Civil Code section 1798.82 requires notice to affected residents in the most expedient time possible and without unreasonable delay.
- Penal Code section 632 requires consent from every party before a confidential conversation is recorded. A recorded visit in California needs consent from everyone in the conversation.
Deployment
Each product is a hosted web application at its own lazers.ai address. Practice staff sign in from a browser. PHI is stored in AWS United States regions, with backups in a second region.
Data governance
Confidentiality
- Each practice's data is separated by account.
- Our staff access practice data only when a support need requires it.
Audit and transparency
- Our clinical platforms keep an audit trail of which user acted on which record.
- We list our subprocessors, their roles and their BAA status.
- We restore-test every PHI database each quarter.
- We answer security questionnaires and walk reviewers through our controls.
Business continuity
Databases are backed up every night, encrypted, to a second AWS region and kept for 400 days. Every quarter we restore a backup to prove it works. Each PHI database passed its most recent restore test, and the latest ran on 2026-11-02.
Frequently asked questions
Do you sign a business associate agreement?
Yes. We sign a business associate agreement (BAA) with each practice before its patient data enters our products. We can sign your form or provide ours.
Who can access our data?
Your staff, and our staff only when a support need requires it. Each practice's data is separated by account. Our clinical platforms keep an audit trail of which user acted on which record.
Which third-party services process our data?
Four vendors. Amazon Web Services (AWS) provides hosting, storage and Amazon Textract. Neon runs the database. Anthropic provides AI processing. AssemblyAI provides medical transcription.
Where is our data stored?
In AWS United States regions. Primary storage is in us-east-2 and backups are in us-west-2.
How long do you keep our data?
AI scribe audio for 7 days and AI scribe transcripts for 90 days. AssemblyAI deletes its copy of each transcript right after processing. Database backups are kept for 400 days. Practice records are kept for the term of the contract.
Can we export or delete our data?
Yes. On request, and when the contract ends, we return or destroy your data as the BAA directs.
What happens to a recorded visit?
The audio is deleted 7 days after upload. Our AI scribe uploads visit audio to encrypted AWS storage. AssemblyAI transcribes it and deletes its transcript right after processing. Our copy of the transcript is purged at 90 days.
How is our data encrypted?
With TLS in transit and default encryption on AWS storage. Every address that serves PHI requires TLS 1.2 or higher and offers TLS 1.3. Every AWS S3 storage bucket is encrypted by default with AES-256 or AWS Key Management Service keys and has all four public access block settings on. Database backups are encrypted.
Do you support multi-factor authentication?
Yes. Every product offers multi-factor sign-in with an authenticator app.
What security certifications do you hold?
We hold no SOC 2 report or other security certification today. SOC 2 is on our roadmap. We complete security questionnaires and walk your reviewers through each control.
What happens if there is a breach?
We notify you as our BAA and 45 CFR 164.410 require: without unreasonable delay, and within 60 days of discovering the breach.
Contact
Email us for a security questionnaire, a BAA or a walkthrough of our controls.
Summary
PHI in our products travels over TLS 1.2 or higher, is stored in AWS United States regions, and is backed up nightly with 400-day retention and quarterly restore tests. AI scribe audio is deleted after 7 days and AI scribe transcripts after 90 days.
In place today
- TLS 1.2 minimum on every PHI address, TLS 1.3 offered
- Default encryption and public access blocks on every S3 bucket
- Multi-factor sign-in on every product
- Audit trails of which user acted on which record
- Nightly cross-region backups kept 400 days
For your reviewers
- A BAA with each practice
- Subprocessor list with BAA status
- Completed security questionnaires
- A walkthrough of each control