Subprocessors
Last updated September 3, 2026
In plain terms
Three providers, and only one of them can reach clinical data — the host that runs the databases. Payments and email never see a chart number.
This summary is for orientation. The terms below are what apply.
These are the third parties that process data on our behalf. Each is bound by contract to process it only on our instruction, and to apply safeguards at least equivalent to our own. Where a business associate agreement is in place, equivalent obligations flow down to any subprocessor that can reach protected health information.
| Provider | What it handles | Location | Clinical data? |
|---|---|---|---|
| Application and database hostingRuns the application and stores every facility database, including clinical and inventory records. | All customer data | United States | Yes |
| StripeTakes subscription payments and issues invoices. Card details go directly to Stripe and never reach our servers. | Billing contact, address, tax id, payment method, invoices | United States | No |
| Email deliverySends account email: invitations, password resets, trial and billing notices, and expiry alerts you have asked for. | Recipient name and email address, message content | United States | No |
Changes to this list
We will update this page before adding a subprocessor that can reach customer data, and email workspace owners who have a BAA with us at least 30 days beforehand. If you object to a new subprocessor on reasonable grounds, tell us and we will work with you — including letting you cancel without penalty if we cannot resolve it.
To be notified of changes, email support@surgi-sys.com and ask to be added to the subprocessor notice list.
What is deliberately not on this list
There is no analytics provider, no advertising network, no session recorder and no customer-messaging widget embedded in the application. A page your staff use while a case is open should not be sending anything to a third party, and it does not.