Narzim
New: AI Medical Scribe now available for healthcare organizations.
Narzim

Remedy Sys LLC

Av. Insurgentes Sur 1602, Mexico City, MX · Austin, TX, USA
privacy@narzim.com · +1 (800) 664 9073

Effective: June 25, 2026
Version 2.0

Data Encryption Statement

Remedy Sys LLC (operating as “Narzim”) protects customer and patient data with strong, industry-standard cryptography at every layer — at rest, in transit, and in use. This statement describes the encryption practices applied across the Narzim platform.

1. Our commitment

Encryption is a baseline control in our security program. We design our systems so that sensitive data, including electronic Protected Health Information (ePHI), is encrypted by default rather than as an optional setting.

2. Encryption at rest

All data stored by Narzim, including ePHI and backups, is encrypted at rest using AES-256 (or equivalent strength). Storage volumes, databases, and object storage are encrypted using managed keys.

3. Encryption in transit

All connections to and within the Narzim platform use TLS 1.2 or higher with modern cipher suites. Data exchanged between clients, services, and integrations is encrypted end to end across untrusted networks.

4. Key management

  • Keys are generated and stored in a dedicated key management service
  • Regular key rotation and strict, least-privilege access to key material
  • Separation of duties between key management and data access

5. Application-layer protection

Especially sensitive fields can receive additional application-layer encryption beyond storage-level encryption, providing defense in depth for the most critical data.

6. Resilience & isolation

  • Logical tenant isolation between customer environments
  • Encrypted, regularly tested backups for recovery
  • Continuous monitoring of key usage and data access, with audit logging

For questions about this statement or to request supporting documentation, please email security@narzim.com.

Narzim Privacy & Security Office

Remedy Sys LLC

This statement is provided for informational purposes and does not constitute legal advice or a warranty. Specific cryptographic implementations may evolve as standards and best practices change.