Public sources only

How We Collect Data

Where creator information comes from, what we deliberately do not touch, and the legal basis for it.

Last updated: 29 July 2026

Summary

We build our creator directory from information creators publish themselves, preferring official platform APIs wherever they exist. We do not read private messages, private analytics, or anything behind a login. Every sponsorship we record stores the evidence it was based on, and any creator can see, correct, or remove their record.

What We Collect, and From Where

Public profile information

For creator discovery we collect information creators have made public on their own profiles: display name, handle, channel or profile description, subscriber and follower counts, view counts, post counts, country, profile image, and the links they publish in their own bios and link-in-bio pages.

Public sponsorship signals

We record publicly visible indications that a piece of content was sponsored — disclosure hashtags such as #ad or "paid partnership", brand mentions, discount codes, and affiliate links — together with the text we saw and where we saw it.

Official platform APIs first

Where a platform provides an official API, we use it in preference to anything else. YouTube data is collected through the YouTube Data API. This is both more accurate and less intrusive than reading rendered pages.

Data you give us directly

If you create an account, claim a profile, or connect an account by OAuth, we collect what you provide and what you authorise. This is separate from public discovery data and is treated as yours.

What We Never Collect

Private messages

We do not collect direct messages, comments in private groups, or any content that is not publicly visible.

Private analytics

We do not access creator-only analytics dashboards. We only see private metrics if a creator explicitly connects their account and grants us permission, and only for as long as that permission stands.

Credentials

We never ask for, store, or use platform passwords. Account connections are made through the platform’s own OAuth flow.

Content behind a login wall

We do not create accounts to reach material a logged-out visitor cannot see.

Every Claim Carries Its Evidence

Nothing is asserted without a source

When we record that a creator worked with a brand, we store the text we saw, where we saw it, when, how it was detected, and a confidence score. If a creator disputes an entry, we can show exactly what it was based on rather than pointing at a number.

Estimates are labelled as estimates

Figures we infer rather than observe — such as an estimated rate — are recorded as estimates with their basis, and are never presented as reported results.

Linked accounts require proof

Accounts on different platforms are only attached to one identity when there is proof of control, such as an OAuth connection or a verification token. Anything weaker is reviewed by a person before it is treated as the same creator.

Your Rights as a Creator

Access and correction

You can request everything we hold about you, and ask us to correct anything inaccurate. Claiming your profile shows you the record directly.

Objection and erasure

You can object to our processing or ask us to remove your profile from discovery. We will do so unless we have an overriding legal obligation to retain something, and we will tell you if that is the case.

How to reach us

Email [email protected]. We aim to respond within 30 days, as required under UK and EU data protection law.

How We Behave Technically

Rate limits and politeness

Our collection runs at a deliberately conservative pace with per-domain rate limiting. We are not trying to extract as much as fast as possible.

Refresh, not hoarding

Public metrics are refreshed on a schedule so records stay current, and profiles that stop changing are checked less often rather than more.

Storage and access

Data is held in an encrypted database inside a private network. Access is restricted and administrative actions on creator identities are recorded in an audit trail.

Questions?

Contact our team if you need clarification on this policy.

[email protected]