Effective Date: November 7, 2026 Last Updated: November 7, 2026
1. Introduction and scope
CaseFlo, Inc. ("CaseFlo," "we," "us," or "our") provides practice operations software for surgical, medical, and dental practices and residency programs, beginning with oral and maxillofacial surgery. This Privacy Policy describes how we collect, use, disclose, and protect information when you use our web application and mobile application (collectively, the "Service") and our public website.
CaseFlo operates as a Business Associate under the Health Insurance Portability and Accountability Act of 1996 ("HIPAA") when we process Protected Health Information ("PHI") on behalf of healthcare organizations that use our Service. This Privacy Policy applies to all users of our Service, including clinicians, practice managers, administrative staff, and residents and fellows, whether they use the Service through a healthcare organization's account or through a no-fee account.
By accessing or using the Service, you acknowledge that you have read and understood this Privacy Policy. Our handling of PHI is also governed by the Business Associate Agreement between CaseFlo and your healthcare organization. If this Privacy Policy and a Business Associate Agreement conflict, the Business Associate Agreement controls.
2. Information we collect
2.1 Information from healthcare organizations
When healthcare organizations use our Service, we process the following categories of patient information on their behalf:
Patient identifiers and contact details:
- Patient names, dates of birth, and sex
- Medical record numbers (MRN)
- Phone numbers, email addresses, and mailing addresses
Case and clinical information:
- Procedures and diagnoses, including CPT, CDT, and ICD-10 codes
- Surgery dates, scheduling, and case status
- Care team assignments and tasks
- Clinical notes and case documentation
- Registry information the organization records about a case
Insurance and billing information:
- Payer, plan, member, and group numbers
- Eligibility and prior authorization information
- Charges, claim denials, and appeals
Documents and messages:
- Documents and files the organization uploads
- Messages between care team members, including attachments
The Service has no fields for Social Security numbers or payment card numbers. This patient information is PHI under HIPAA, and we process it solely as a Business Associate under Business Associate Agreements with healthcare organizations.
2.2 Information from users
When your organization invites you and you create an account, or when you open a no-fee account, we collect:
Account information:
- Full name
- Email address and phone number
- Role, program, and facility affiliation
- Profile photo (optional)
Agreement records:
- Your acceptance of our Master Services Agreement and Business Associate Agreement, including the version you accepted, the date and time, and any organization you accepted for
- Your answers to the confirmations about your status and institutional permissions, and the institutions you identify to us
Authentication data:
- Sign-in credentials, which are managed by our identity provider and never stored by CaseFlo in readable form
- Multifactor authentication enrollment status
- Biometric unlock settings in the mobile app (such as Face ID, Touch ID, or Android fingerprint or face unlock). Biometric data stays on your device and is never transmitted to or stored by CaseFlo.
Device information:
- Device identifiers used to deliver notifications
- Device type, operating system version, and app version
2.3 Information collected automatically
When you use the Service, we automatically collect:
Audit trail data (required for HIPAA compliance):
- The user who performed each action
- The time of each action
- The type of action (for example, sign-in, view, create, edit, or delete)
- The records accessed or changed
- IP address and browser or app information at the time of access
Technical data:
- Server error logs and performance metrics
2.4 Information from our public website
If you join our waitlist or contact us, we collect the information you provide, such as your name, email address, role, training level, and program. This information does not include patient information.
2.5 Information from our product demo
Our product demo contains only made-up patient data. If you use it, we collect the name, email address, organization, role, and interests you provide. We also record how you use the demo, including the actions you take and session recordings of the demo screens, so we can understand and improve CaseFlo. We use PostHog to collect and analyze this demo activity.
3. How we use information
3.1 Service delivery
We use information to:
- Provide case, task, scheduling, document, and messaging features
- Coordinate work among care team members
- Send notifications about tasks, status changes, and messages
- Provide customer support
3.2 Compliance and security
We use information to:
- Maintain audit logs as required by HIPAA
- Detect and prevent unauthorized access and security incidents
- Investigate potential violations of our Terms of Service
- Respond to legal requirements
- Fulfill our obligations under Business Associate Agreements
3.3 De-identified and aggregated information
As our Business Associate Agreements permit, we may de-identify PHI under the HIPAA de-identification standard (45 CFR 164.514(a)–(c)). De-identified information is not PHI. We may use and disclose de-identified information, including in aggregated form, for any lawful purpose, including to:
- Improve and develop the Service
- Produce benchmarks for healthcare organizations
- Support registry reporting and research
De-identified information does not identify any patient. We do not attempt to re-identify it, and we do not identify a healthcare organization or user as its source without the healthcare organization's prior written consent.
We may also use PHI to provide data aggregation services for a healthcare organization's health care operations, such as benchmarking, quality assessment, and registry reporting, as HIPAA permits.
3.4 Communications
We use contact information to:
- Send service-related announcements and security alerts
- Provide customer support
- Notify users of policy changes
- Contact waitlist members and demo users about access to the Service
4. Legal basis for processing
4.1 Business Associate Agreement
Our basis for processing PHI is the Business Associate Agreement between CaseFlo and each healthcare organization using our Service. Under HIPAA, a Business Associate may use and disclose PHI only as its Business Associate Agreement permits or as required by law.
4.2 HIPAA compliance
We process certain information to meet our obligations under HIPAA, including:
- Maintaining audit logs of PHI access (45 CFR 164.312(b))
- Implementing security safeguards (45 CFR Part 164, Subpart C)
- Helping healthcare organizations respond to individual rights requests (45 CFR 164.524, 164.526, and 164.528)
4.3 Legitimate business interests
We process user account information and usage data based on our legitimate interests in:
- Providing and improving our Service
- Keeping the Service secure and preventing fraud
- Communicating with users about the Service
4.4 User choice
You choose whether to:
- Turn on biometric unlock in the mobile app
- Allow notifications on your device
5. Information sharing and disclosure
5.1 Healthcare organizations
We share PHI with the healthcare organization that owns it, as its Business Associate Agreement provides. Healthcare organizations may access the patient data and audit logs for their programs and facilities.
5.2 Service providers (subcontractors)
We use service providers that process information on our behalf. Any service provider that handles PHI must first sign a Business Associate Agreement with CaseFlo.
Current service providers:
- Amazon Web Services, Inc. (AWS): Hosting, database, file storage, sign-in and multifactor authentication, email delivery for account messages, security monitoring, and backups, in the United States. AWS is the only service provider that handles PHI.
- Airtable: Stores waitlist sign-ups from our public website. It receives no patient information.
- PostHog: Records activity and sessions in our product demo, which contains only made-up patient data. It receives no patient information.
We will update this list before any new service provider handles PHI.
5.3 Legal requirements and business transfers
We may disclose information:
- When required by law, including in response to a subpoena, court order, or lawful request by public authorities
- To protect the rights, property, or safety of CaseFlo, our users, or others, as permitted by law and by our Business Associate Agreements
- In connection with a merger, acquisition, or sale of assets, subject to the same protections for PHI
5.4 AI features
CaseFlo includes an AI assistant that is turned off. If it is turned on in the future, it will be optional for each healthcare organization, it will run on Amazon Bedrock within CaseFlo's AWS environment, and it will be able to read the patient and case information it needs to complete a task a user asks for. Amazon Bedrock does not share prompts or responses with AI model providers, and they are not used to train AI models. We will not use PHI, or let any service provider use PHI, to train any AI model made available to third parties. The AI assistant can propose changes, but a person must confirm any change before it is made. We will update this Privacy Policy and notify healthcare organizations before the AI assistant is turned on.
AI-generated content is informational only and must be checked by a qualified professional before use. CaseFlo does not submit licensed CPT content to AI models.
5.5 Commitments we make
We do not:
- Sell personal information or PHI, or receive payment in exchange for PHI
- Use PHI for marketing or fundraising
- Share PHI with third parties for their own purposes
- Use health information for targeted advertising
6. Data security measures
We maintain administrative, physical, and technical safeguards to protect information in line with the HIPAA Security Rule (45 CFR Part 164, Subpart C) and our written Information Security Policy.
6.1 Encryption
- Data in transit: All connections use TLS 1.2 or higher.
- Data at rest: The database, uploaded files, logs, and backups are encrypted with AES-256 keys managed by CaseFlo in AWS Key Management Service.
6.2 Access controls
- Unique accounts: Every user has their own account, created by invitation.
- Multifactor sign-in: Users sign in with a password and an authenticator app code.
- Role-based access: Access depends on the user's role, program, and facility.
- Automatic sign-out: Every session ends after 24 hours. We are rolling out automatic sign-out of idle sessions after 15 minutes on the web and 30 minutes on mobile.
- CaseFlo staff: CaseFlo support staff have no standing access to patient records.
6.3 Audit controls
- Access logging: Access to patient records and security events are logged.
- Protected logs: Audit logs are append-only. The application cannot change or delete them.
- Retention: Audit logs are kept for at least six years.
6.4 Mobile security
- Secure storage: Sign-in tokens are stored in the device Keychain and are available only when the device is unlocked.
- Local biometrics: Biometric data never leaves your device.
- Secure connections: The app connects only over HTTPS.
6.5 Infrastructure security
- Hosting: The Service runs on AWS in the United States, with backups copied to a separate AWS account in a second US region.
- Network and threat protection: Web application firewalls, threat detection, and malware scanning of uploaded files.
- Monitoring: Security monitoring and alerting for configuration and application errors.
- Vulnerability management: Automated scanning of our code and dependencies for known vulnerabilities.
6.6 Incident response
We follow a written Incident Response and Breach Notification Policy. We notify the affected healthcare organization of a breach or suspected breach of its unsecured PHI without unreasonable delay and no later than 72 hours after we discover it, and of a successful security incident involving its PHI no later than 10 business days after discovery, as HIPAA and its Business Associate Agreement require.
7. Data retention
7.1 PHI retention
We keep PHI for as long as the healthcare organization's agreement and instructions require, and as applicable law requires.
When a Business Associate Agreement ends, PHI stays available for the healthcare organization to export for 60 days, and we then destroy it promptly, unless retention is required by law. PHI in backup systems is destroyed on our regular backup retention schedule and stays protected until then. If return or destruction is not feasible, we continue to protect the remaining PHI and limit its use to the purposes that make return or destruction infeasible.
7.2 Audit log retention
Audit logs documenting access to PHI are kept for at least six years from the date they are created.
7.3 User account data
User account data is kept while the account is active. When an account is closed:
- Access is turned off immediately
- Account and activity records needed for audit and security purposes are kept for the periods HIPAA and our retention policy require
- Records of your acceptance of our agreements and your confirmations are kept for at least six years after the later of your acceptance and the end of the Business Associate Agreement
- Other profile information, such as a profile photo, is deleted when it is no longer needed
7.4 De-identified data
De-identified data may be kept indefinitely, because it does not identify any patient.
7.5 Waitlist and demo information
We keep waitlist and demo information until you ask us to delete it or we no longer need it to contact you about CaseFlo.
8. Your rights
8.1 HIPAA rights (for PHI)
If you are a patient whose information is processed through our Service, you have rights under HIPAA, including:
- Right to access: Request copies of your PHI
- Right to amendment: Request correction of inaccurate PHI
- Right to an accounting of disclosures: Request a list of certain disclosures of your PHI
- Right to request restrictions: Request limits on certain uses and disclosures
- Right to confidential communications: Request communications through alternative means
Important: You exercise these rights through the healthcare organization that maintains your records. As a Business Associate, CaseFlo helps healthcare organizations respond to these requests.
8.2 User rights (for account information)
As a user of our Service, you may:
- Access: Request access to your account information
- Correction: Update or correct your profile information
- Deletion: Request deletion of your account, subject to audit log retention requirements
- Portability: Request an export of your account data
To exercise these rights, contact us at support@getcaseflo.com.
8.3 California residents (CCPA/CPRA)
If you are a California resident and the California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA), applies, you have the following rights:
- Right to know: Request information about our data collection practices
- Right to delete: Request deletion of personal information
- Right to opt out: We do not sell or share personal information
- Right to non-discrimination: We will not discriminate against you for exercising your rights
Information processed under HIPAA may be exempt from the CCPA/CPRA.
To exercise California privacy rights, contact us at support@getcaseflo.com.
9. Children's privacy
CaseFlo is designed for healthcare professionals and is not intended for anyone under 18. We do not knowingly collect personal information from anyone under 18.
Patient records processed through our Service may include information about minor patients. Healthcare organizations manage this information under HIPAA, state law, and their own policies for minor patients' health information.
10. Third-party links and integrations
Our Service may link to third-party websites or services. We are not responsible for their privacy practices, and we encourage you to review their privacy policies.
We plan to offer integrations with practice electronic health record (EHR) systems, including software installed on a practice's own server with the practice's written consent. We will describe each integration to the healthcare organization, and cover it in its agreements, before it is turned on.
11. Changes to this Privacy Policy
We may update this Privacy Policy to reflect changes in our practices, technology, or legal requirements.
For material changes:
- We will notify users by email or a prominent notice in the Service
- We will notify healthcare organizations as our Business Associate Agreements require
- We will update the "Last Updated" date at the top of this policy
Continued use: Your continued use of the Service after a change takes effect means you accept the updated Privacy Policy.
12. Contact information
If you have questions, concerns, or requests about this Privacy Policy or our privacy practices, contact us:
Privacy inquiries: Email: support@getcaseflo.com
General support: Email: support@getcaseflo.com
Mailing address: CaseFlo, Inc. Maple Grove, MN
HIPAA-related requests: If your request relates to PHI, contact your healthcare organization directly. Healthcare organizations may contact us at support@getcaseflo.com for help with HIPAA-related requests.
Response time: We respond to privacy inquiries within 30 days. Requests involving HIPAA rights are handled within HIPAA's required timeframes.
13. State-specific disclosures
13.1 California
Categories of personal information collected:
- Identifiers (name, email address, phone number, device identifiers)
- Professional information (role, program, and facility affiliation)
- Internet activity (audit and session information, and activity in our product demo)
- Approximate location based on IP address
Business purposes for collection:
- Providing the Service
- Security and fraud prevention
- Service improvement
- Legal compliance
Sale of personal information: We do not sell personal information as defined under the CCPA/CPRA.
Sensitive personal information: We process health information as a Business Associate under HIPAA, which is exempt from certain CCPA/CPRA requirements.
13.2 Other states
We comply with the state privacy laws that apply to us. Health information processed under HIPAA may be exempt from certain state privacy law requirements.
13.3 Illinois (BIPA)
Biometric unlock in our mobile app uses your device's built-in biometric features, such as Face ID and Touch ID on Apple devices or fingerprint and face unlock on Android devices. CaseFlo does not collect, store, or process biometric identifiers or biometric information. Biometric data is processed on your device by its operating system and is never transmitted to CaseFlo.
14. Additional information
14.1 International users
CaseFlo is designed for use in the United States. All data is processed and stored in the United States. If you access the Service from outside the United States, your information will be transferred to the United States.
14.2 Do Not Track
Our Service does not currently respond to "Do Not Track" browser signals because there is no consistent industry standard for them.
14.3 Automated decision-making
We do not use automated decision-making or profiling that produces legal or similarly significant effects on individuals.
*This Privacy Policy is effective as of the date listed above and supersedes all prior privacy policies.*
CaseFlo, Inc.