Your conversations never train a model. Tenant-isolated, encrypted, yours.

Read our security posture

ArcGlass Listen — AI Notetaker with Enterprise-Grade Security.

Download

Get an executive review of your company conversations before you commit.

See a sample
Security & compliance

Data security

Updated on Sep 7, 2026 · 1 minute read

This page describes the controls that protect customer data in ArcGlass.

Encryption

All data is encrypted in transit using TLS. Data at rest is encrypted using industry-standard algorithms. Secrets and tokens are stored encrypted and are never exposed in URLs or logs.

Tenant isolation

Every organization's data is logically isolated. org_id is a first-class scoping field applied on every query, and access is checked against the caller's membership in the organization before any data is read.

Access control

Access is governed by role-based permissions with one capability map for the whole product. Identity is derived from the verified session, never from caller-supplied fields. Destructive operations require an explicit delete capability. See Members & Roles.

Application security

  • Inbound webhooks are signature-verified before processing.
  • Server-side fetches of user-supplied URLs go through an SSRF-safe path.
  • OAuth popup callbacks target a specific origin, never a wildcard.
  • Independent penetration testing has been performed; results are available under NDA.

Infrastructure

ArcGlass runs on reputable cloud infrastructure with access restricted to the systems and personnel that require it. See Subprocessors for the vendors involved.

NextData privacy & retention →