Purpose
Himaya inspects email, attachments and workspace data in order to protect it. This policy describes how we keep that data secure while we process it, whether it is stored by Himaya or inspected in transit.
Scope
It covers customer data Himaya handles to deliver the service: message content and metadata, attachments, outbound mail held by data loss prevention, workspace and cloud findings, and the analysis results and audit records we create from them.
Data minimization
We process only what is needed to secure your workspace. Where a decision can be made from a fingerprint rather than the content itself, we keep the fingerprint.
- Outbound inspectionText extracted from outbound mail and attachments for data loss prevention is not stored. Only a SHA-256 digest and length are kept for each part of a message.
- FindingsSensitive values such as secrets and card numbers are reported in redacted form.
- Connected sourcesWorkspace and cloud connectors request the access needed for the checks you enable, and read-only access wherever the provider offers it.
Encryption
Customer data is encrypted in transit with TLS 1.2 or higher and at rest with AES-256. Encryption keys are held in a dedicated key management service with scheduled rotation.
Tenant isolation
Each customer runs in a logically isolated tenant. Data, agent memory and models never cross tenant boundaries, and every request is scoped to the tenant of the signed-in user.
Your data is never used to serve, analyze or train for another customer.
Access control
Access inside the Himaya platform follows a permission model with separation of duties:
- Mail contentReading message content, quarantine and held mail requires an explicit content permission.
- ConfigurationSettings and integrations are managed under a separate permission. Settings administrators cannot read mail content.
- AuthenticationSSO/SAML is supported for every workspace, and multi-factor authentication is enforced.
- Audit trailEvery administrative action is logged.
Personnel access
Himaya staff access customer data only when it is needed to operate, support or secure the service, under least-privilege access with audit logging.
Handling hostile content
Suspicious links and attachments are opened only in isolated, throwaway sandbox environments, never on production systems. Content from inspected messages and pages is treated as untrusted data, not as instructions to our systems or models.
When inspection is incomplete
Content Himaya could not fully inspect is never treated as clean. Outbound mail that cannot be inspected is held for review, and gaps in coverage are recorded.
Review
This policy is reviewed at least annually and whenever the way we process customer data changes materially.