Product notice / Privacy

Product privacy.

This notice covers ChartSplice accounts and sign-in. Customer reporting data remains subject to the organization’s agreed data-handling arrangements.

Scope and responsibility

ChartSplice is an Operandus product. This notice describes account and authentication information processed for invitation-only ChartSplice reporting workspaces, including approved testing environments. Available sign-in methods and reporting connections depend on the workspace and deployment.

The public marketing website has a separate website privacy notice. Your organization’s written agreement and data-handling arrangements govern its reporting data; this notice does not replace those arrangements or establish a compliance certification.

Account information

We process your email address, display name, authentication-provider identifiers, basic profile information returned by your chosen sign-in provider, and account verification status. Provider information may include a profile-image URL. ChartSplice does not need your mailbox, calendar, files, advertising account, or directory contents to sign you in.

Account administration also processes workspace memberships, roles, dashboard view/export/access-management permissions, invitations and their delivery state, session-revocation state, and minimal access-audit events. These records establish who may access a workspace and what they may do.

If you use a password or authenticator, the authentication service processes the credentials and factors needed to verify you. Passwords, authenticator codes, recovery tokens and factor secrets are not intentionally written to the application’s access-audit records or reporting data.

Google and Microsoft sign-in

Google and Microsoft sign-in request identity-only access: OpenID identity, basic profile and email. We use the resulting identity information to authenticate you, check verification, and match you to an approved invitation and current workspace membership.

Signing in through a provider does not grant reporting access by itself. A workspace administrator must authorize access. A matching email domain is not an invitation, and provider consent is not a grant to the organization’s data platform.

We do not use information received through Google or Microsoft sign-in for advertising, sell that information, or use it to train artificial-intelligence models. Google sign-in does not request access to Gmail, Google Drive or Google Ads; Microsoft sign-in does not request mailbox, directory-content or Fabric data permissions. Provider account administration and the provider’s own processing are governed by its terms and privacy notice.

How account information is used

We use account information to provide sign-in, invitations, account recovery, workspace authorization, administrator verification, requested exports, access revocation, and security or operational support. Minimal audit events record the acting/target account identifiers, action, relevant workspace/dashboard identifier and time—not report contents or authentication secrets.

Transactional invitation and recovery emails contain the address and information needed to deliver the requested account action. They are not marketing subscriptions. Do not forward invitation or recovery links; they are intended for the invited account holder.

Service providers and sharing

Supabase provides the separate account/authentication stores. Vercel hosts the application and processes requests. Resend delivers transactional account emails. Google or Microsoft processes your chosen provider sign-in. These services may process technical request information, such as IP addresses, browser information, access times and operational logs, as part of operating their services.

Authorized workspace administrators can see account-directory and access information needed to administer the workspace. Other permitted users may see names, roles and dashboard-access indicators; account-directory email access is restricted to authorized administration.

We use account information for the purposes described here and may disclose information where required by applicable law or necessary to investigate abuse, protect accounts or fulfill an authorized support request. We do not place patient/source-system records in the account-profile or membership tables.

Customer reporting is separate

Reporting connections use the organization’s configured data platform and governed reporting contracts. The account store manages application access, not data-warehouse administration. Customer reporting information is not obtained from Google or Microsoft identity-only sign-in.

Current configured reporting paths return reviewed aggregates rather than exposing a general-purpose warehouse query interface. Aggregates and authorized exports can still be confidential. Your organization controls permitted use, recipients and retention of its reporting information under the applicable engagement and data-handling arrangements.

Do not put patient information, medical records, passwords or other confidential source data in account names, invitation fields or ordinary support emails.

Cookies, sessions and security records

The application uses necessary authentication/session cookies and short-lived confirmation or sign-in state. Reporting requests and private account responses are configured not to be stored in shared browser/CDN caches. Authentication cookies are separate from marketing measurement.

The application uses keyed hashes and request counts to limit repeated authentication actions. Authentication and hosting providers may retain additional operational/security records under their service arrangements. Security controls reduce risk; this notice does not promise that any system is risk-free.

Retention and account requests

Account and authorization records are retained as needed to operate the workspace, maintain access history, handle security incidents and meet agreed or legal retention requirements. Disabling a membership revokes access but is not the same as deleting the account or its access history. Provider-held logs and records follow the relevant service arrangements; no universal deletion period is implied.

Contact your workspace administrator to change workspace access. For questions or requests to access, correct or delete ChartSplice account information, contact hunter@operandus.co. We may need to verify the requester and coordinate with the organization before acting. Describe the request without including passwords, recovery links or patient records.

You may also manage or revoke ChartSplice’s provider authorization through your Google or Microsoft account settings. Revoking provider authorization is separate from requesting deletion of ChartSplice account/access records.

Changes and contact

We update this notice when account processing changes. Questions about this notice can be sent to hunter@operandus.co.

Updated: October 7, 2026.