Emissary carries conversations with candidates and employees for teams that answer to legal, IT and the people they text. Data is encrypted at rest and in transit, access follows least privilege, texting numbers are 10DLC-registered, and our controls are audited against SOC 2 Type 2 every year.
Everything Emissary stores is encrypted at rest with AWS KMS using AES-256, and everything in motion travels over HTTPS with TLS 1.2 or 1.3. Inside the app, every entity is pseudonymized with URL hashing. Emissary runs on AWS with a redundant configuration — the main server sits in us-east-1 (Northern Virginia) and backups are stored automatically across multiple availability zones in the United States.
Access controls at Emissary follow the Principle of Least Privilege and Role-Based Access Control, so people see only what their role requires. Your users sign in with a username and password and can turn on MFA through SSO integration. On our side, personnel reach internal systems exclusively through SSO with MFA, and developer access runs exclusively over SSH paired with a VPN and firewalling that filters by IP and port.
Your numbers are 10DLC-registered with the carriers, and the STOP keyword is honored automatically — when someone opts out, the texts stop. Every conversation keeps a full audit trail, and transcripts sync to the candidate or employee record in your ATS or HCM, so legal, HR and recruiting all look at the same history.
Emissary follows SOC 2 Type 2 standards and is externally audited against them every year. Infrastructure, code and dependencies are scanned continuously and an independent penetration test runs annually. Written security policies and procedures are in place, read-only event logs are retained for at least 365 days, and physical security is handled by our hosting provider, AWS.
Emissary follows SOC 2 Type 2 standards and is audited against them on an annual basis.
GuardDuty watches the AWS infrastructure, HostedScan scans from outside, SonarCloud reviews our code and GitHub Dependabot checks library dependencies.
Policies are written down, events are logged read-only for at least a year, and the data centers are run by AWS. The full detail lives in our Technical and Organizational Measures.