WordSentinel™Contact Sales

Trust & Security

Built for regulated industries.

Security controls

Authentication & access

JWT enforcement, MFA support, least-privilege principles

Data security

AES-256 at rest, TLS 1.3 in transit, regional deployments

Integrity & provenance

Full audit trails, version control, immutable release sets

Evidence signing

ES256 via Cloud KMS, cryptographic signatures, tamper-proof

Compliance posture

SOC 2 program

Comprehensive security controls audited by third-party assessors

No customer data for training

Your documents and data are never used to train AI models

No redistribution

Your information stays within your organization's boundaries

Verification guide for auditors

How to verify signatures

Every Evidence Pack contains a cryptographic signature that auditors can independently verify:

  • • Extract the JWT signature from the Evidence Pack header
  • • Use our public key (available via JWKS endpoint)
  • • Verify the ES256 signature matches the payload
  • • Confirm the document hash and rulebook versions

What's verifiable

The signature covers all critical validation data:

  • • Document content hash (SHA-256)
  • • Validation verdict and findings
  • • Rulebook version and SHA
  • • Code release SHA and timestamp
  • • Supplement versions (lexicons, etc.)

Need more security details?

Security BriefingDownload Security Overview PDF