Security

Secure Sharing for Authenticated App Snapshots

SnapState is built for private app context, so security copy must be specific, conservative, and easy to understand.

Intentional capture

SnapState captures a page when a user chooses to capture it. That is different from hidden background recording. The intentional model makes the privacy story easier for teams to evaluate.

The reporter should always know that a snapshot is being created and should be able to preview what will be shared.

  • User-initiated capture.
  • Redaction before sharing.
  • Workspace-aware links and revocation.

Data minimization

SnapState captures what is needed for collaboration: UI state, route, viewport, metadata, comments, and optional diagnostics. Teams can avoid richer diagnostics when they do not need them.

That framing helps security reviewers understand the product's boundaries.

Future trust center

SnapState does not use compliance badges, SOC 2 claims, or enterprise guarantees before they exist. The current controls are described honestly, and enterprise features belong on the roadmap only when appropriate.

This security model pairs naturally with redaction, authenticated app screenshot guidance, and pricing because buyers need to understand both workflow and control.