Sub-processors
Last updated August 2026. Every third party that processes customer data on behalf of Promatics Technologies Inc. in the course of providing Attergo.
| Category | What it does | Can it reach protected health information | Where |
|---|---|---|---|
| Cloud infrastructure | Compute, managed database and object storage for the production environment. | Yes. Encrypted at rest and in transit; the provider holds no application credentials. | United States |
| Clearinghouse | Transmits 837P claims and returns 277 acknowledgements and 835 remittances on the customer's behalf. | Yes, and necessarily. A medical claim is protected health information by definition. | United States |
| Transactional email | Delivers account, security and notification email. | No. By design no message we send contains a patient name, date of birth, prescription number or any re-identifying value. | United States |
| Error and performance monitoring | Captures application exceptions and latency so faults are found before customers report them. | No. Payloads are redacted before they leave the application by a field registry the build enforces. | United States |
| Website analytics | Measures which pages visitors read on the public marketing site, and which lead to a demo request. | No, and it cannot. The tag loads on the marketing site only and is absent from every authenticated page of the application. | United States |
| Offsite backup storage | Holds encrypted database backups for disaster recovery. | Yes, encrypted. Keys are held by us, never by the storage provider. | United States |
Categories rather than vendor names, because a named vendor on a public page is a starting point for someone attacking our customers. The specific entities, their certifications and their agreements are provided in full under the business associate agreement and any mutual non-disclosure agreement, before you sign anything.
How this list changes
We notify customers at least thirty days before adding a sub-processor that can reach protected health information, in writing, to the contact on the account. A customer who objects on reasonable security grounds within that window may terminate the affected services without penalty and takes a complete export with them.
Replacing a sub-processor in a category that cannot reach protected health information is not notified individually, but this page is updated and the date at the top changes.
What every sub-processor is bound to
Each is engaged under a written agreement that imposes obligations no weaker than those we owe you: confidentiality, purpose limitation, security measures appropriate to the data, breach notification to us without undue delay, and deletion or return of data at termination. Where the sub-processor handles protected health information, that agreement includes the business associate terms HIPAA requires.
What is not on this list, deliberately
There is no advertising network, no data broker and no model provider. No customer data of any kind is used to train a model for a third party, and no third-party script of any kind loads on an authenticated page of the application.
An earlier version of this page said the website carried no tracking scripts at all, and promised that if it ever changed it would change here first rather than quietly. It has changed: the public marketing site now runs Google Analytics, recorded in the table above and described in the privacy policy. It processes visitor telemetry only. It reaches no customer data, no protected health information and no part of the application.
Questions
Write to privacy@attergo.com for privacy and sub-processor questions, or security@attergo.com for security correspondence.