See where your website actually stands—no email, no URL crawl, score in two minutes. Run the free System Review →
Client-owned web systems
Plan my system

SITEBORNE SIGNAL MODULE

ProofVault — secure document and deliverable portal

Provides controlled access to approved resources through short-lived authorization and retention controls.

Try the demonstrationAdd to a project brief

BUSINESS OUTCOME

What this capability changes.

  • Controlled delivery
  • Revocable access
  • Documented retention

Best for

Agencies, Professional firms, Client-service businesses

AI: noneProduction pattern: available

From $3,000

Module-only monitoring: from $250/monthA narrow add-on scoped to this module alone—checking its allowance, fallback, and failure state. It is separate from and smaller than a full Care plan, which covers the whole website.

Launch allowance statusAvailable

PLAIN LANGUAGE, TECHNICAL PROOF

What ProofVault does.

A controlled place to deliver approved documents for a limited time instead of attaching them to a long email chain.

Why it is valuable

Access can expire or be revoked, and the business can document who was allowed to retrieve a deliverable.

Example workflow

A client receives a 48-hour link to an approved launch report; access expires automatically and can be revoked sooner.

FOR TECHNICAL READERS

How the control model works

Production delivery uses private object storage, short-lived signed authorization, D1 audit records, explicit retention, and a verified recipient channel. This public demo never accepts files.

Failure path: Manual delivery through a verified client-owned channel.

INTERACTIVE WALKTHROUGH

Use ProofVault before discussing it.

Choose a deliverable and access window to preview the controls that would wrap a real client-owned file.

The interaction uses your input and identifies whether it runs locally, checks this live site, or previews a production control. It does not disguise seeded output as intelligence.

Interactive demonstrationYour input stays in this browser unless the control says “live.”

System view

Required

Cloudflare R2, Cloudflare D1, Cloudflare Workers, Resend

Optional

None

Fallback

Manual delivery through a verified client-owned channel.

Provider dependencies

Cloudflare R2, Cloudflare D1, Cloudflare Workers, Resend

Last verified

2026-08-02

Provider limits, terms, model availability, and pricing may change. Production accounts remain client-owned.

Data classification

  • Approved documents
  • Access audit events
  • Verified email

LAUNCH ALLOWANCE

Object storage

Storage for approved media, resources, screenshots, and deliverables.

Current limit
10 GB-month, 1M Class A operations, 10M Class B operations monthly; no R2 internet-egress charge; excludes Infrequent Access.
Expected light use
Approved downloads, monitoring screenshots, and a limited library of client-owned media.
What consumes it
Standard-storage GB-months plus Class A mutation and Class B read operations.
Fallback
Disable optional uploads and preserve local/documented delivery path.
Paid successor
Cloudflare R2 paid usage or approved storage adapter
Commercial use
Commercial use permitted.
Data warning
Private buckets by default; signed access and retention controls required.
Last verified
2026-08-02
View all referenced allowances
  • Object storage: 10 GB-month, 1M Class A operations, 10M Class B operations monthly; no R2 internet-egress charge; excludes Infrequent Access.
  • Transactional email: 3,000 emails/month, 100/day, one custom domain, one webhook endpoint, 30-day retention.

Upgrade triggers

  • storage — 75%. Archive or expand storage.
  • sensitive classification — any. Require separate security review.
Conventional fallback: Manual delivery through a verified client-owned channel.
View implementation proof

Decision rationale

The implementation favors semantic HTML, static rendering, typed content, and isolated on-demand routes. Optional AI never controls pricing, eligibility, or emergency routing.

Controls

  • WCAG 2.2 AA target
  • Provider-neutral adapters
  • Usage caps and kill switches
  • Client-owned production accounts
  • Conventional fallbacks

Verified evidence

  • The browser demonstration runs from a clean clone without a paid credential.
  • Kill switch and allowance states are typed configuration.
  • Primary navigation and contact paths remain independent of this module.

Known limitation

External provider allowances and production behavior require owner accounts and deployment-time verification.