Privacy
Privacy & Consent
How PlayerSignal separates public DBU-derived football data from player-owned profile fields, private uploads and consent-sensitive information.
Public match data
PlayerSignal indexes public DBU match pages, lineups and match events. These public stats remain source-locked and are shown with source context so clubs, scouts and players can verify them.
Player-owned fields
Profile fields such as position, Instagram, external profile link, legal/agent contact and media / clip links are controlled from the signed-in profile workspace. Public visibility is explicit per field where the workspace supports it.
Minors and representatives
Youth players may involve a parent, guardian or representative. PlayerSignal treats contact and ownership information as account-controlled data, not as public DBU match data.
Private uploads
Scouting files and uploaded profile material are private by default. They require an upload-rights confirmation and are not exposed in public pages, public APIs, CSV exports or AI-agent discovery surfaces. Public media / clip links should only be added when the owner has the right to share them.
Access control
Admin, claim, upload and profile-owner APIs require sign-in and origin protection. Public exports intentionally contain DBU-derived football rows only, not private workspace data.
Correction and removal
If a public profile is wrong, the right fix is normally source correction, identity merge/split review or removal of player-owned fields. For private account or profile-owner data, contact PlayerSignal support.