Privacy Architecture

Technical overview: local-first design, one external API (license validation only).

1. Local Storage Model

  • Sessions stored locally
  • Screenshots stored locally
  • Exports generated locally
  • PRO autosave ZIP written locally

Session data is stored locally (e.g., Chrome storage). PRO autosave writes ZIP files locally via Chrome downloads.

2. External Communication

Only one outbound request: PRO license validation API (status only). License validation confirms entitlement only.

Data that may be transmitted for license validation (minimal):

  • License key or purchase email
  • Extension version
  • Anonymous device identifier generated locally

Data that is never transmitted during license validation:

  • Captured screenshots
  • Captured steps or session data
  • Documentation content or notes
  • Exports (RTF, PDF, DOCX, ZIP)
  • Browsing history

3. What We Do NOT Collect

  • No usage analytics
  • No behavioral tracking
  • No telemetry
  • No background monitoring

Privacy Policy — Home