Security at VidSeen

This page describes how VidSeen protects your recordings and account data. It is written for the person on your IT or security team who has to approve us — contact us for anything it does not answer.

Architecture

VidSeen runs entirely on Microsoft Azure in the United States (East US). Recordings are stored in Azure Blob Storage, metadata in Azure SQL Database, and video is delivered through Azure Front Door. Each organization’s data is isolated by organization ID at the application layer; share pages on customer domains resolve to exactly one organization.

Identity and access

Sign-in is handled by Microsoft Entra External ID — we never see or store passwords. Organizations on the Enterprise plan can connect their own identity provider so their IT controls access and offboarding. Inside VidSeen, roles (Owner, Admin, Member) limit who can manage the team, billing, and domains.

Encryption

All traffic uses TLS 1.2 or later. Data is encrypted at rest by Azure Storage and Azure SQL (AES-256). Application secrets live in Azure Key Vault with role-based access, not in code or configuration files.

Backups and resilience

The database has continuous point-in-time backup, and restores are rehearsed, not assumed. Deleted recordings are recoverable by us for 14 days before permanent deletion. Availability is monitored from multiple regions around the clock, and the team is alerted automatically when checks fail.

Subprocessors

Microsoft Azure (hosting, identity, storage, telemetry), Stripe (payments — card details never touch our servers), Azure AI Speech (transcripts), and Anthropic (written summaries). Providers process content only to deliver their service to us and do not train models on it.

Reporting a vulnerability

Email security@vidseen.com and we will respond within two business days. Please give us reasonable time to fix an issue before disclosing it.

Data processing

Our data processing addendum covers GDPR and similar requirements for customers who need one.