Skip to main content

Overview

Moss is committed to meeting global compliance standards and protecting user privacy. This page outlines our compliance posture and the features that support your regulatory requirements.

GDPR Compliance

Moss provides features to support your GDPR compliance obligations. Moss acts as processor or sub-processor for customer data. Direct data-subject requests to the relevant customer.

Data Subject Rights

Right to Access (Article 15)

Authorized customer operators can fulfill data access requests using:
  • Export chat history via Dashboard
  • Download session recordings
  • Access audit logs for their activity

Right to Erasure (Article 17)

Moss supports deletion of user-linked data: What Gets Deleted:
  • Chat sessions and messages
  • AI-generated instructions and plans
  • Screenshots and recordings in configured storage
  • User records
  • Associated request logs
Deletion Process:
  1. Submit a deletion request via API or contact Moss
  2. Moss validates the request
  3. User records and linked application data are deleted
  4. Deletion results are returned for review
The response covers the selected current application/user records and files in configured session storage. Backups and external processor copies are handled through separate deletion procedures. A failed storage sweep leaves the request incomplete and preserves references for retry. Where queued deletion is enabled, the API first returns a durable request ID and status. Poll that request for completion; acceptance is not proof of deletion. Customer-managed infrastructure and copies held by Moss have separate operating responsibilities. Contractual return, deletion and certification deadlines apply independently of routine retention periods.

Right to Portability (Article 20)

Export user data in standard formats:
  • Chat history (JSON)
  • Session metadata (JSON)
  • Audit logs (CSV)

Lawful Basis

The controller determines the lawful basis for processing:

Data Processing Agreement

Contact sales for a Data Processing Agreement (DPA) that meets your requirements.

SOC 2 Type II

Moss is pursuing a SOC 2 Type II examination.

Trust Service Criteria

Controls

Moss implements controls across:
  • Access Control - Role-based access, MFA, session management
  • Change Management - Code review, deployment approval, rollback capability
  • Incident Response - Detection, escalation, resolution procedures
  • Monitoring - Real-time alerting, audit logging, anomaly detection

Timeline

SOC 2 Type II examination work is in progress. Contact sales for the current status and audit reports.

ISO 27001

Moss is pursuing ISO 27001 certification.

Information Security Management

Key areas covered:
  • Risk Assessment - Regular security risk evaluations
  • Asset Management - Inventory and classification of information assets
  • Access Control - Need-to-know and least privilege principles
  • Cryptography - Encryption standards for data protection
  • Operations Security - Secure development and deployment practices

Timeline

ISO 27001 certification is in progress. Contact sales for updates.

EU AI Act

Moss is preparing for EU AI Act compliance as it applies to AI-powered assistant systems.

Transparency Requirements

Moss supports transparency through:
  • Clear AI Identification - Users know they’re interacting with AI
  • Capability Disclosure - Documentation of AI capabilities and limitations
  • Decision Explanation - AI responses include reasoning when applicable

Human Oversight

  • User Control - Users can dismiss or override AI suggestions
  • Admin Control - Application owners can customize AI behavior
  • Audit Trail - Selected audit events and optional detailed request logs support review

Risk Classification

Applicable requirements depend on the use case and the organization’s role:
  • Transparency obligations
  • User notification
  • Human oversight capabilities

Domain Whitelisting

Restrict where your SDK can operate:

Purpose

  • Prevent unauthorized use of your application ID
  • Control which environments can access Moss
  • Reduce risk of API key exposure

Configuration

Add allowed domains in Dashboard under Settings > Security:

Enforcement

When an allowlist is configured, requests from unlisted domains are rejected during SDK initialization.

Compliance Resources

Documentation

  • Privacy Policy - Available on viamoss.ai
  • Terms of Service - Available on viamoss.ai
  • Security Whitepaper - Contact sales

Agreements

  • Data Processing Agreement (DPA) - Available for enterprise customers

Next Steps

Security Overview

Complete security architecture

Audit Logging

Detailed audit trail documentation