Skip to content

Trust

How verification works

The Auditor doesn't do vibes. Here's exactly what the verified stamp means, what we store, and when the stamp comes off.

The Auditor, a crow in an accountant visor with a calculator

The rules

What verified means.

  • API-sourced only

    Every number comes from the provider's API through a connection you set up. There's no manual entry anywhere in StatCrow, no CSV upload, no screenshot. If you could type it, it wouldn't be verified.

  • Read-only keys

    We ask for read-only access wherever the provider supports it and warn you when a key can do more. Stripe secret keys and test mode keys get bounced at the door.

  • Encrypted vault

    Keys are encrypted with AES-256-GCM before they're stored, bound to their connection, and decrypted only inside the sync that needs them. They never reach your browser or our logs.

  • Domain checks

    Traffic and search sources must match the project's domain. A GA4 web stream, a Search Console property, a Plausible or Umami site: if the domain doesn't match, the mapping is refused.

  • One account, one project

    A provider account can back only one project. Big sudden jumps and revenue concentrated in a single customer get flagged and kept off the leaderboard until someone takes a look.

  • Self-hosted stays unverified

    Self-hosted Umami, Plausible and PostHog work fine in your dashboard. They never get the stamp, because we can't vouch for a server we don't control.

Freshness

The stamp has an expiry date.

Verified is a state, not a trophy. It's earned on every sync.

healthy.source

Verified

The connection is healthy and synced within the last 48 hours.

Stripe, synced 2h ago

stale.source

Last verified

No healthy sync for over 48 hours. Pages show when it was last verified instead of a live stamp.

Stripe, last verified Oct 24

dropped.source

Stamp removed

Stale for 7 days, or the key was revoked. Badges and embeds stop saying verified until the source syncs again.

Data

What we store, and what we don't.

We keep

  • Daily totals per metric: MRR, revenue, subscriptions, visitors, pageviews, search clicks, downloads and ratings.
  • Which connection produced each number, so every row traces back to its source.
  • Your connection credentials, encrypted.
  • Sync history: when each source last synced and whether it worked.

We don't keep

  • Your customers' names or emails.
  • Individual transactions or raw analytics events.
  • Credentials after you disconnect. Those are deleted on the spot.
  • Anything public that you didn't choose to show.

Visibility

You choose what's public.

Private by default

Projects start private. Nothing shows anywhere until you flip the switch.

Exact, range or hidden

Per metric. Revenue defaults to a range, everything else to hidden, until you say otherwise.

Hidden means hidden

Hidden metrics never leave the server. Not on pages, badges, embeds, stat cards or the leaderboard.

Want the nerdy details? Read the security page.