Role-based accounts
Players and coaches use separate sign-in routes and permissions. New player and staff onboarding is paused while the club reviews the pilot.
IVYBRIDGE TOWN U16 · SAFEGUARDING & PRIVACY Team websiteThe public team website can remain visible. Private player rollout and new invitations are paused until Ivybridge Town Football Club approves the pilot.
The controls below reduce risk, but they do not replace a formal club decision. Before rollout, the committee should appoint responsibility, involve the Welfare Officer, confirm the lawful basis, complete a safeguarding risk assessment and DPIA, issue clear parent or carer and player privacy information, record any required consent, review suppliers and insurance, and approve a deletion process.
Players and coaches use separate sign-in routes and permissions. New player and staff onboarding is paused while the club reviews the pilot.
The proposed record is limited to account email, player name, team and position, development content, activity type, total time and optional total distance.
There is no coach-to-player inbox or private messaging. Spond remains the official route, with parents or carers included in under-18 communication.
A player sees their own account. Only approved U16 staff see the limited squad information needed for their role, with Welfare Officer oversight agreed by the club.
The proposed schedule is immediate deactivation when a player leaves or consent is withdrawn, followed by deletion within 30 days unless the club documents a lawful need to retain a record.
Only authorised coaches can upload match photographs or short clips. Each upload requires confirmation that current signed permission exists, and it stays private unless deliberately approved for publication.
Speak directly to a parent or carer, the Club Welfare Officer or another trusted adult. Follow the club’s existing safeguarding procedure. If somebody is in immediate danger, contact the emergency services.
The current pilot uses protected account authentication and a managed database. Before rollout, the club will be given the named suppliers, their role, hosting region, access controls, security arrangements and deletion lifecycle for approval. Public visitors cannot see private player records. Existing records will not be expanded or repurposed while review is under way.
Tracker connections remain switched off. If the club later approves them, the integration must request only activity duration and total distance. It must not request, import, display or store GPS routes, live location, start points, end points or health metrics.