Understanding a FigureCert proof

A number you can inspect.
A record you can share.

A Screen-verified certificate records a number and its reporting context read from a guided browser recording. It tells you who submitted the report, what FigureCert checked and when the certificate was issued.

From report to certificate

  1. The submitter chooses a report

    They choose the metric and dates, provide the report link and sign in to FigureCert with LinkedIn. The LinkedIn name identifies the submitter; it does not establish ownership of the report account.

  2. FigureCert guides the recording

    The submitter shares a prepared tab. FigureCert opens the chosen report in that tab and records the visible page through its capture process. The capture is bound to the verification session and checked before review.

  3. The number and context are checked

    Image-reading models read the value, unit, account and reporting dates. Server-side rules compare those readings with the request and check supported consistency rules. Missing or conflicting required information prevents a successful certificate for that metric. This is automated review, not a human audit.

  4. FigureCert issues a signed record

    The certificate states the confirmed value and context. FigureCert signs the issued facts digitally so changes can be detected. The signature establishes the issuer and integrity of the record; it is not a signature from Stripe, HubSpot or Salesforce.

What you can conclude

The certificate documents the result of FigureCert’s screen check. Read the number together with its dates, filters and any submitter-provided metric description. A reporting date is different from the date the certificate was issued.

FigureCert checked what was visible on screen. It did not confirm the underlying records with the provider. A screen check cannot rule out all browser manipulation or establish that a company’s reported revenue is economically accurate.

Your report stays private until you share

Recordings are used for verification and deleted under the capture retention policy; they are not included in a public certificate. The full report URL and source account identity are not automatically published. Before publishing, the submitter reviews the exact public certificate, including any potentially sensitive labels or filters.

The public link shows the signed certificate while sharing remains active. The owner can revoke that link. Revocation cannot remove copies or PDFs someone has already saved.

Inspect a certificate

Check the value, reporting period, submitter and verification method. Use the original public link for the current sharing status. “Technical details” provides the signed document and verification key for independent signature verification.

Research source checks use a different method: an authenticated provider response. Their certificates are labelled Source-verified. A Screen-verified certificate never claims that method.