Allscreenshots Docs

Compliance and auditing

Create time-stamped proof of web content for regulatory and audit requirements

Capture verifiable, time-stamped screenshots of web content for compliance documentation, regulatory audits, and organizational records.

The problem

Many industries require proof of what was displayed on websites at specific points in time:

  • Financial services — Document disclosures, terms, and pricing as shown to customers
  • Healthcare — Archive patient-facing content for HIPAA compliance
  • E-commerce — Preserve records of pricing, promotions, and product descriptions
  • Legal — Capture terms of service, privacy policies, and consent forms

Manual screenshots aren't reliable. They lack timestamps, can be edited, and don't scale across hundreds of pages.

How Allscreenshots helps

Automatically capture time-stamped screenshots that serve as reliable evidence of web content at specific moments in time.

  • Metadata capture — Timestamps, URLs, and capture parameters recorded
  • Scheduled archiving — Automate compliance captures on a regular basis
  • Full page capture — Document entire pages including below-the-fold content
  • Bulk processing — Archive hundreds of pages in a single operation

Store screenshots in your own S3-compatible storage for complete control over retention and chain of custody.

Quick example

Capture a terms of service page with full metadata:

curl -X POST https://api.allscreenshots.com/v1/screenshots \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://yoursite.com/terms-of-service",
    "fullPage": true,
    "format": "png",
    "waitUntil": "networkidle",
    "metadata": {
      "purpose": "compliance-archive",
      "documentType": "terms-of-service",
      "version": "2.1"
    }
  }'

The response includes capture timestamp and all parameters used:

{
  "url": "https://yoursite.com/terms-of-service",
  "capturedAt": "2024-01-15T14:30:00Z",
  "imageUrl": "https://...",
  "metadata": {
    "purpose": "compliance-archive",
    "documentType": "terms-of-service",
    "version": "2.1"
  }
}

Key features for this use case

Next steps

On this page