What this means for clubs
- A club normally decides why its workspace data is collected and how it is used for club operations.
- MySportsHive provides the platform, support, security, and technical processing needed to run those club workflows.
- Public club profile pages should only use club-approved public data; private member, finance, child/player, message, and permission records must stay behind signed-in areas.
- A paid onboarding order form or DPA should confirm the formal controller/processor position, retention, deletion, subprocessors, and breach notice process.
Working data responsibility model
The working model is that a club controls the workspace data it adds, invites, manages, publishes, or uses for club operations. MySportsHive provides the platform and acts as processor for that club-controlled workspace data where the club determines the purpose.
MySportsHive controls data it collects for its own business, public website, support, security, public demo/contact leads, administration, paid onboarding, and platform protection.
Club-controlled workspace data
- Club members, staff, officials, coaches, volunteers, parents, guardians, players, and under-16 profile relationships.
- Programme/team membership, attendance, availability, session records, progress or performance records, messages, announcements, and club dashboard records.
- Club finance records such as billing profiles, invoices, payment records, manual payment notes, e-wallet settings, receipts, bank details where configured, and signed invoice link metadata.
- Public club profile content that a club chooses to publish, such as activities, venues, media, sponsors, news, and contact details.
MySportsHive-controlled data
- Public contact, support, pricing interest, demo booking, and optional demo tailoring details.
- Support correspondence sent directly to MySportsHive.
- Public portfolio analytics where configured and consented.
- Commercial onboarding records, admin assignment notes, lead follow-up records, security logs, abuse-prevention records, and operational diagnostics.
What a final DPA should cover
- Subject matter, duration, nature, purpose, data categories, data subjects, and processing instructions.
- Confidentiality, security, subprocessor approval, assistance with rights requests, breach notification, deletion or return of data, audits, and international transfer safeguards.
- Special care for youth sport data, parent/guardian links, private profile information, medical/profile data, invoices, payment records, and public/private profile boundaries.
Requests, export, deletion, and offboarding
Some requests should start with the club because the club controls the workspace record. MySportsHive can help route platform, access, support, privacy, and technical requests where appropriate.
Final deletion, export, retention, and offboarding commitments should be confirmed in the signed club agreement or DPA before they are treated as a public promise.
Sensitive public form boundary
Public demo, contact, and support forms should not be used for passwords, full card details, unnecessary medical information, or unnecessary sensitive child details.
Safeguarding, medical, match-day, welfare, and club policy issues should use the club route or emergency route where appropriate. MySportsHive support helps with platform access, account links, privacy, accessibility, security, invoice download, and technical issues.
Need help with a legal or account question?
Use the public contact form for support, privacy, account, package, or product questions. For club-specific records, contact the club administrator as well.