This is an early provider overview, not a final subprocessor register. It explains the provider categories and current direction so clubs can see what must be confirmed in a signed agreement or final register.
How to read this page
- A provider direction means MySportsHive intends to use that provider or category, but the final register should confirm exact service names, regions, and legal role.
- A provider may apply only to some features, environments, clubs, or payment routes.
- Do not treat a provider as UK-only, certified, active for every feature, or covered by a specific contractual safeguard unless the final register or order form says so.
- Paid clubs should receive clear notice of provider categories before live club/member/player/parent data is handled at scale.
Provider categories
- Category
- Backend and application hosting
- Purpose
- Run backend APIs, server-side application services, queues, cache, and related production infrastructure.
- Status
- Laravel Cloud is the current backend hosting direction. Production region and managed service details should be named in the final register.
- Category
- Frontend hosting
- Purpose
- Host the public portfolio and related frontend applications.
- Status
- Netlify is the current frontend hosting direction. Deployed app and domain coverage should be named in the final register.
- Category
- Database, queue, and cache services
- Purpose
- Store application data and support jobs, cache, queue processing, and operational reliability.
- Status
- Production database, queue, and cache services should be listed with region, retention, and security details before final publication.
- Category
- File and media storage
- Purpose
- Store uploaded media, public club profile assets, generated files, invoice/receipt files, and operational attachments where configured.
- Status
- The active storage provider and region should be confirmed before public launch claims are made.
- Category
- Email delivery
- Purpose
- Send account, support, demo, invoice, and service emails.
- Status
- The production email provider, sender domains, and retention position should be confirmed in the final register.
- Category
- Payment provider
- Purpose
- Enable Stripe payment routes, connected account flows, payouts, refunds, disputes, and reconciliation where enabled.
- Status
- Stripe is the intended payment provider direction. Package payment flow, Connect scope, fees, refunds, disputes, merchant model, and rollout status should be confirmed before paid onboarding.
- Category
- SMS or messaging provider
- Purpose
- Send SMS or communication messages where enabled.
- Status
- SMS or messaging use should be listed only when a production use case is enabled.
- Category
- Error monitoring and security logging
- Purpose
- Diagnose incidents, bugs, abuse, and platform reliability issues.
- Status
- Production monitoring providers should be listed with retention and data minimisation details before final publication.
- Category
- Analytics
- Purpose
- Measure public portfolio usage only when configured and consented.
- Status
- Google Analytics 4 support is implemented for the public portfolio, but remains inactive unless the deployment is configured and the visitor accepts optional analytics. GA4 property ownership and launch timing should be confirmed before production analytics is enabled.
- Category
- AI-assisted features
- Purpose
- Support AI-assisted performance, feedback, or support tooling where enabled.
- Status
- AI provider terms, customer data use, retention, training, and opt-out boundaries should be confirmed before paid-club commitments are made.
| Category | Purpose | Status |
|---|---|---|
| Backend and application hosting | Run backend APIs, server-side application services, queues, cache, and related production infrastructure. | Laravel Cloud is the current backend hosting direction. Production region and managed service details should be named in the final register. |
| Frontend hosting | Host the public portfolio and related frontend applications. | Netlify is the current frontend hosting direction. Deployed app and domain coverage should be named in the final register. |
| Database, queue, and cache services | Store application data and support jobs, cache, queue processing, and operational reliability. | Production database, queue, and cache services should be listed with region, retention, and security details before final publication. |
| File and media storage | Store uploaded media, public club profile assets, generated files, invoice/receipt files, and operational attachments where configured. | The active storage provider and region should be confirmed before public launch claims are made. |
| Email delivery | Send account, support, demo, invoice, and service emails. | The production email provider, sender domains, and retention position should be confirmed in the final register. |
| Payment provider | Enable Stripe payment routes, connected account flows, payouts, refunds, disputes, and reconciliation where enabled. | Stripe is the intended payment provider direction. Package payment flow, Connect scope, fees, refunds, disputes, merchant model, and rollout status should be confirmed before paid onboarding. |
| SMS or messaging provider | Send SMS or communication messages where enabled. | SMS or messaging use should be listed only when a production use case is enabled. |
| Error monitoring and security logging | Diagnose incidents, bugs, abuse, and platform reliability issues. | Production monitoring providers should be listed with retention and data minimisation details before final publication. |
| Analytics | Measure public portfolio usage only when configured and consented. | Google Analytics 4 support is implemented for the public portfolio, but remains inactive unless the deployment is configured and the visitor accepts optional analytics. GA4 property ownership and launch timing should be confirmed before production analytics is enabled. |
| AI-assisted features | Support AI-assisted performance, feedback, or support tooling where enabled. | AI provider terms, customer data use, retention, training, and opt-out boundaries should be confirmed before paid-club commitments are made. |
Payment provider boundary
Stripe is the intended payment provider direction, but online payment routes are not automatically available to every club. They depend on provider setup, account readiness, provider terms, and product configuration.
Stripe or another payment provider may apply its own verification, fee, payout, refund, and dispute rules. Public copy should stay cautious until final commercial, technical, and legal review is complete.
Analytics boundary
The public portfolio includes consent-aware analytics wiring and optional attribution storage. These remain disabled unless a measurement ID is configured, analytics is explicitly enabled, and the visitor accepts optional analytics.
Token-bearing auth URLs and sensitive query parameters are scrubbed before page view tracking or lead attribution storage.
Before this becomes a final register
- Confirm each production provider name and legal role.
- Confirm processing region, transfer safeguards, retention, and security commitments.
- Confirm whether clubs receive notice or approval rights for new subprocessors.
- Confirm how provider changes are communicated to paid clubs.
- Confirm how clubs can ask questions about a provider before signing an order form.
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.