Security model

Read-only Stripe access, no account changes.

Proofround is designed to make a founder revenue packet credible without expanding access beyond what is needed to verify Stripe-backed metrics.

What we access

  • Read-only Stripe permissions
  • Revenue, customer, and subscription records
  • No write access or payment initiation

What we never store

  • Raw Stripe objects in their original form
  • Card or bank details
  • Founder passwords or account credentials

Founder controls

  • Revocable packet links
  • Expiry windows for shared access
  • Visibility settings for public profiles

Investor view

  • Read-only packet experience
  • No investor account required
  • Only aggregated, time-stamped metrics

What this means in practice

Access

We only request read-only Stripe permissions needed to compute verification metrics and generate packets.

Storage

Raw Stripe data is not stored as a user-facing asset. Packets present aggregated metrics and founder-controlled access links.

Sharing

Packet links can expire or be revoked, giving founders control over who can view their information.

Investors

Investors see the packet in a read-only view with no account creation required.