▸ For legal and compliance review

How to read a CreatorScore report before you sign off.

What each output is and is not, how coverage is stated, what every finding carries, which rules the regulated-industry codes consider, and how to verify the exact report you were handed.

“outputs”: 4
Social background check
CreatorScore and risk report
Governance report
Community report
Each states its coveragealways

▸ The four outputs

What you are holding, and what it is not.

Two products share one pipeline. A background check never produces a score; a score never reads a background check.

01 / 04

Social background check

A one-time inspection of a creator's public content history, categorised into brand-safety findings with the post, frame or transcript behind each one. A public-record mode reads press and legal coverage of a public figure and states every matter with its outcome.

What it is not

It produces no score and makes no recommendation. It is not a consumer report and is not FCRA-compliant.

02 / 04

CreatorScore and risk report

A 1 to 100 trust score across a creator's whole footprint, from seven weighted agents, with every flag tied to the post it came from and a two-sentence narrative. Monitoring refreshes it on a schedule.

What it is not

It is not a compliance determination. A high score says the footprint showed no conduct we detect as risk; it does not say a campaign is lawful.

03 / 04

Governance report

A creator checked clause by clause against a code: the FTC Endorsement Guides, a brand-safety baseline, an alcohol baseline, a customer's own code, or one of four regulated-industry codes. Each clause shows a flag with its evidence, a pass over a stated scope, or not assessed.

What it is not

A clause names the rule it considers; it never states that a creator is compliant or in breach of it.

04 / 04

Community report

What a creator's audience says in the comments: sentiment over time, how sponsored posts land, themes, brands the audience names, repeated issues and recurring topics, each with the comments behind it.

What it is not

It is read from stored comments and a model's grouping of them; it is context for a reviewer, not a finding against the creator.

▸ Coverage

Not assessed is never a pass.

Every governance clause carries one of four coverage grades, derived from which detectors are live, never typed by hand.

Full

Every detector behind the clause is live and nothing in the clause's scope is left unexamined. A pass is a pass over the whole clause.

Partial

A verdict is possible, but part of the clause is not examined. The report states the gap under the pass as 'Scope of this pass'.

Advisory

A detector emits findings but cannot ground a pass. A finding is shown; silence is never a pass.

Not assessed

No signal reaches a verdict. The clause says why, and what a reviewer does instead. Not assessed is never a pass.

▸ Every finding

What a finding carries, every time.

A count is never a finding. If we cannot show the proof, we do not apply the penalty.

  • The post, frame, transcript line or comment behind it, with a link and a point-in-time capture where one exists.
  • The category and severity, the detector that produced it, and whether a second-opinion review confirmed it. An unconfirmed visual finding is labelled as such and never moves a score.
  • For any legal, criminal, regulatory or accusatory matter: its outcome, in the words of the record, or 'Unresolved as of' with the date. A matter whose outcome we could not find is not published.
  • Who is speaking: the creator's own words and conduct, or reporting and reaction. Only the creator's own conduct can lower a score; viewpoint and news coverage never do.
  • Whether the account is the creator's: every account in a footprint passes an identity check, and a platform we could not read is listed, not dropped.

▸ Regulated industries

Four codes that name the rule each clause considers.

Each is CreatorScore's plain-language reading of the rules a reviewer in that sector checks a creator against. A clause shows the rule it considers under its requirement and states no legal conclusion. Clauses we have no signal for yet, such as fair balance, licensing and audience age, read not assessed and say what a reviewer does instead.

Pharma and health

FDA 21 CFR 202.1 and the 2025 direct-to-consumer letters, FTC Act section 5 and 16 CFR Part 255, Australia's TGA Code section 24, UK CAP Code 12

Financial services and banking

Securities Act section 17(b), FINRA Rule 2210, SEC Marketing Rule 206(4)-1, FTC Part 255, CFPB UDAAP, UK FSMA section 21

Crypto and digital assets

Securities Act section 17(b), FTC Parts 255 and 465, UK FSMA section 21 as applied to cryptoassets since October 2023

Insurance

state producer-licensing and advertising rules on the NAIC models, CMS Medicare marketing rules at 42 CFR 422.2260, FTC Part 255

▸ Limitations

What a CreatorScore report is not.

  • Not legal advice, and not a determination that any campaign, post or creator complies with any law or regulation.
  • Not a consumer report. CreatorScore is not a consumer reporting agency, and a report must not be used for decisions about an individual's employment, credit, insurance or housing.
  • Not exhaustive. Coverage is stated per clause and per platform; what we did not read is listed, not assumed clean.
  • Not a human review by default. Findings are produced and reviewed by AI models; a human reads a matter when it is contested or when a customer asks.

▸ Provenance, verification and disputes

Verify the exact report you were handed.

  • Every exported report carries a provenance block: the report ID, when the scan completed, when the document was generated and by whom, the code version that produced it, the models recorded on its findings, its coverage, and a fingerprint of its contents.
  • The fingerprint can be checked against our records through the API, so a reviewer can confirm a PDF is the report we generated and has not been altered. A regenerated report has a new fingerprint.
  • Findings are reviewed by AI models, and a creator or a customer can contest any finding. A contested finding is marked pending review; a finding found to be wrong is retired everywhere it appeared.
  • Background-check disputes are acknowledged within two business days and resolved within five, through the dashboard or the API; the general dispute route in the terms allows up to thirty business days.
  • Flagged evidence is stored in private storage and read through short-lived signed links. Scores and findings keep a history with the code version that produced them.

Questions from counsel are welcome.

Write to [email protected] with the report ID and we answer with the record behind it.