Security Architecture
Attergo is a business associate to every customer, and the platform is built so the strongest security claims are architectural facts, enforced by the database and the build pipeline rather than by policy documents. Every control on this page is verifiable in diligence, and we invite that verification.
Technical Controls
Every table carrying customer data runs forced row-level security keyed to the organization. A query that is not scoped returns nothing: the system fails closed. The application connects as a role that cannot bypass those policies, and the isolation test suite asserts that property before it asserts anything else.
Two independent mechanisms: a build-time gate that fails the release if a protected field reaches a logging call, and a runtime redactor that scrubs protected data from anything serialized. Notifications say that something needs attention and link into the platform; clinical detail never travels outbound.
Every access to protected data is written to a log the application has no permission to alter or delete; those grants are revoked at the database. An audit log the application can rewrite is not an audit log.
Every event is stored exactly as your system sent it, before interpretation, on storage the application cannot modify. This is what makes an audit response evidentiary: what you produce is what you received.
Every account touching protected data or financial figures authenticates with a second factor. There is no administrative opt-out. Credentials are hashed with argon2id; TOTP seeds are encrypted with AES-256-GCM.
TLS 1.2 or higher on every connection, including the per-store webhook your pharmacy system posts to. Encryption at rest across the data layer. Webhook credentials are hashed, per store, and individually revocable.
Assurance and Governance
Promatics Technologies Inc. executes a BAA with every customer before protected data flows. Subcontractors with any exposure to PHI are bound to equivalent terms.
The raw evidence archive is retained for ten years, the horizon audit defense actually requires. Full export in open formats at any time; deletion on termination is contractual.
Attergo operates a formal security control program aligned to SOC 2 Type II criteria, maintained as audit evidence: change management, structured logging, access reviews, and documented, exercised backup and restore. Security documentation is available to customers under NDA.
Contractual breach notification timelines backed by a documented, rehearsed incident response runbook. Customers hear from us with facts and actions, fast.
Security questions and vulnerability reports reach the engineering team directly at security@attergo.com.