Skip to main content

Overview

Moss implements multiple layers of data protection to ensure your information remains secure throughout its lifecycle. For customer-managed deployments, see Deployment Scope.

Encryption

In Transit

Public Moss service endpoints use HTTPS:
  • TLS 1.2+ - Encrypted public API connections
  • Certificate Validation - Strict certificate verification

At Rest

Data stored in Moss databases is protected:
  • Database Encryption - AES-256 encryption at rest for Moss-hosted databases
  • Credential Protection - API-key verification hashes and encrypted reusable credentials
  • Secure Key Storage - Encryption keys managed separately from data

Input Validation

API request schemas validate inputs before processing:

Schema Validation

Pydantic schemas define request fields and validation rules:

Validation Rules

Rejection Behavior

Invalid requests receive clear error responses:

Sensitive Data Handling

Automatic Redaction

The request-log sanitizer redacts known credential fields before storage: Redacted Fields:
  • api_key, apiKey
  • authorization
  • password
  • secret
  • token
  • x-api-key
How It Works:

Recursive Sanitization

Redaction applies to nested objects and arrays:

Credential Storage

API Keys

API keys are never stored in plaintext:

JWT Signing Keys

JWT secrets receive enhanced protection:

Password-Like Secrets

End-user passwords and login secrets are managed by the deployment’s identity provider; Moss does not collect or store them. Reusable integration credentials are encrypted at rest.

Secure Defaults

Authentication is enforced on every SDK request in production; it cannot be disabled outside isolated development environments.

Domain Whitelisting

Restrict SDK usage to approved domains:

Configuration

Set allowed domains in the Dashboard under Settings > Security:

Enforcement

When an allowlist is configured, requests from unlisted domains are rejected during SDK initialization.
Remember to include all environments (production, staging, development) in your whitelist.

Data Minimization

Moss follows data minimization principles:

Collected Data

For Moss-hosted service data, use the applicable agreement, documented customer instructions, and Privacy Policy to determine the period. Capture settings control collection; a signed URL’s expiry controls access and does not delete an object. Confirm that the deletion schedule is active for the intended application and storage destination before relying on an automatic retention period. Recordings and support copies require their own scope and deletion treatment. Input-field redaction does not redact screenshot pixels. Recording controls and screenshot capture are configured separately.

User Control

Users can control data collection via SDK configuration:
To apply the same settings after the SDK has loaded, pass them to window.MossSDK.boot(...):

Next Steps

Audit Logging

Review recorded system activity

Compliance

GDPR, data deletion, and certifications