What we collect
Account and workspace data
Rounds processes account and clinic workspace data required to operate Home, Feed, Config, and
Copilot for the signed-in operator. This may include account identity, clinic profile details,
connector state, operational events, attention items, and Copilot history associated with the
active workspace.
How we use data
Service operation and workspace synchronization
Rounds uses workspace data to render operational read models, maintain connector state, surface
follow-up items, and support review of clinic operations. Rounds does not present Copilot as
clinical decision support, and Copilot is not medical advice.
Connector boundaries
Primary app authentication and connector authorization
Primary app authentication at launch uses Clerk email/password. Google OAuth is connector-only in
v1 and is used solely for supported connectors. During App Review, the review workspace may use
seeded or sandbox-backed review data so no third-party credentials are required for baseline
testing.
AI and data use
Copilot data processing limitations
Copilot is read-only, operations-only, and not medical advice. When Copilot is used, selected
clinic context may be processed by third-party AI services to generate a response. Copilot should
not be used as the sole basis for time-sensitive or patient-impacting decisions.
Deletion and retention
Account deletion and retention
Rounds includes in-app account deletion. Deleting an account removes the current Rounds
workspace data controlled by the app and deletes the active sign-in. Certain operational records
may be retained temporarily where required for security, fraud prevention, or service integrity.
Third-party services
Third-party service providers
Rounds currently relies on third-party services for core product functions, including account
authentication, backend data storage/sync, connector authentication where supported, and AI
response generation where Copilot is used.
- Clerk for primary app authentication
- Convex for clinic workspace data and sync
- Google for supported connector OAuth flows
- Third-party AI providers for Copilot responses
Review environment
App Review environment
The App Review environment uses seeded review data and no real patient data. Reviewers are placed
into a preconfigured clinic workspace with a stable operational dataset for baseline testing.
Contact
Privacy and support inquiries
Privacy and data-use inquiries should be directed to the privacy contact published for the active
deployment. General product and operator-support inquiries should be directed to the support
contact published for the active deployment.