Integrations & security

Keep the systems you already run. We sit underneath them.

Club-scoped API keys, signed webhooks with delivery logs, and CSV export from every reporting surface. Placeholders are stated as placeholders: no third-party integration is live in this preview build.

The integration surface

Read from Fanpodium
MechanismVersioned public API v1 with club-scoped keys
Typical useFeed the club app, website or BI with content, events and aggregate measurement.
Push from Fanpodium
MechanismSigned webhooks with delivery logs and idempotent references
Typical useTrigger CRM updates, fulfilment or ticketing actions on fan events.
Into Fanpodium
MechanismClearly marked integration placeholders
Typical useTicketing, CRM, commerce, sport data, payments, SMS/OTP, push.
Export
MechanismCSV from every reporting surface
Typical useBoard reporting, sponsor decks, offline analysis.

Integration directions, mechanisms and typical uses
Direction	Mechanism	Typical use
Read from Fanpodium	Versioned public API v1 with club-scoped keys	Feed the club app, website or BI with content, events and aggregate measurement.
Push from Fanpodium	Signed webhooks with delivery logs and idempotent references	Trigger CRM updates, fulfilment or ticketing actions on fan events.
Into Fanpodium	Clearly marked integration placeholders	Ticketing, CRM, commerce, sport data, payments, SMS/OTP, push.
Export	CSV from every reporting surface	Board reporting, sponsor decks, offline analysis.

Read APIs the club can call today

Keys are created in the Partner Console, scoped per key and revocable at any time. Aggregate measurement is suppressed for segments too small to be anonymous.

GET

/api/public/v1/content

Published posts for the club's world, ready to render in the club's own app or website.

GET

/api/public/v1/events

Fixtures and events with venue, city and start time.

GET

/api/public/v1/analytics

Aggregate measurement by country, city, device, channel, date and more — small segments suppressed.

Webhooks the club can subscribe to

Every delivery is signed and logged with an idempotent reference, so a failure is visible rather than silent.

post.published

Push new club content into a CRM, newsletter or app feed.

event.created

Sync a fixture or event into ticketing or a calendar.

reward.redeemed

Trigger fulfilment when a fan redeems a reward.

auction.bid_placed

Track auction momentum in the club's own systems.

donation.recorded

Report cause funding into finance or CSR reporting.

Security and privacy posture

Authentication with required phone number at registration; no anonymous sign-ups.
Row-level security on all tenant data; public read limited to explicitly published content.
Explicit database grants per role; no default open access.
Scoped staff roles held in a dedicated roles table — never on the user profile — checked server-side.
Immutable audit logging of staff actions.
Private storage with signed, time-limited access for uploads.
Consent captured at onboarding, visible and revocable per fan.
Data export and deletion request flows with an audit trail.
Analytics gated on consent, with small-segment suppression in all reporting.
Public API endpoints authenticated with club-scoped keys; webhooks signed and idempotent.
Server-side validation and role re-checks on every write.

Not a compliance claim. This describes how the system is built. Formal data-protection assessment, DPA signing, processor mapping and any regulatory approval sit with the club's own legal function, with our technical documentation as input.

Points that need explicit agreement, not assumption

These are decided in writing with the club's legal function before launch.

Minors

Academy audiences include under-age fans. Age gating, parental consent and what a minor may publish are decided with the club's legal function before an academy world opens.

Moderation policy

The club sets community standards; the platform supplies the queues, the reports and the audit trail.

Data residency and retention

Storage region and retention periods are agreed in the DPA.

Incident handling

Notification path and timelines are agreed in writing before launch.

Exit

Full export on request, plus an agreed deletion window after termination.

Data protection, GDPR roles and where data lives

The club is the controller of its supporter relationship. Fanpodium processes on the club's instruction under a written data processing agreement.

Roles under data-protection law

The club is the controller of its fans' data. Fanpodium acts as processor for the club's tenant and processes only on the club's documented instructions. A processor agreement is signed before launch and lists sub-processors, purposes and retention periods.

Data residency

The club chooses the storage region for its tenant, and the region is written into the agreement. Cross-region transfers are not made without the club's written instruction.

Consent and fan rights

Consent is captured at onboarding, shown to the fan and revocable at any time. Fans can request an export or deletion from inside the product, and every request is logged with who actioned it and when.

Minors and academy audiences

Age gating, parental consent and what a minor may publish are agreed with the club's legal function before an academy world opens. Nothing goes live for an under-age audience without that sign-off.

No compliance claim

We describe how the system is built and supply technical documentation. Formal assessment, processor mapping and regulatory approval sit with the club's own legal function.

Intellectual property

The club keeps its marks, content and creative. Fanpodium keeps the platform. Neither side acquires rights in the other's assets by using the service.

Service levels, support and incident handling

What the club can hold us to during a pilot, written plainly rather than as marketing numbers.

Platform availability target
Commitment99.9% monthly, excluding announced maintenance windows
NoteConfirmed contractually per agreement; measured on the club's own world.
Support response
CommitmentCritical within 1 hour, high within 4 working hours, normal next working day
NoteNamed contacts on both sides, plus a matchday escalation path.
Matchday cover
CommitmentMonitored cover across the club's fixture windows
NoteAgreed against the published fixture list ahead of the season.
Security incident notification
CommitmentNotification to the club's named contact without undue delay
NoteWritten timeline agreed before launch; incidents are logged and reviewed with the club.
Backups and recovery
CommitmentAutomated daily backups with point-in-time recovery
NoteRestore procedures tested; recovery targets stated in the agreement.
Change notice
CommitmentAdvance notice of breaking API or webhook changes, with versions kept in parallel
NoteAPI v1 stays available while a successor version is adopted.

Service levels offered during a club pilot
Measure	Commitment	Note
Platform availability target	99.9% monthly, excluding announced maintenance windows	Confirmed contractually per agreement; measured on the club's own world.
Support response	Critical within 1 hour, high within 4 working hours, normal next working day	Named contacts on both sides, plus a matchday escalation path.
Matchday cover	Monitored cover across the club's fixture windows	Agreed against the published fixture list ahead of the season.
Security incident notification	Notification to the club's named contact without undue delay	Written timeline agreed before launch; incidents are logged and reviewed with the club.
Backups and recovery	Automated daily backups with point-in-time recovery	Restore procedures tested; recovery targets stated in the agreement.
Change notice	Advance notice of breaking API or webhook changes, with versions kept in parallel	API v1 stays available while a successor version is adopted.

How the club leaves — with everything

Exit is a designed feature, not a negotiation. If the club decides to stop, the data goes home and the world goes dark on the club's word.

1. Notice

The club gives notice under the agreement. Nothing is switched off on the day notice is given.

2. Full export

Fans and consent state, content, events, orders, points ledger, tier history, auctions and bids, causes and donations, campaign performance and analytics — all exported to CSV, plus API access for a programmatic pull.

3. Handover window

An agreed read-only period during which the club can re-pull anything it missed and re-point its own app or CRM away from the platform.

4. Verified deletion

After the agreed deletion window, the club's tenant data is deleted from live systems and rolls out of backups on the stated cycle. The club receives written confirmation.

5. What we keep

Only what law requires: invoicing records and the immutable audit trail entries needed to evidence past processing. No fan profiles, no behavioural data, no content.

Straight answers

The questions clubs actually ask

“We already have an app.”: Keep it. Path two runs Fanpodium underneath it and feeds it through APIs and webhooks.
“We already have a CRM.”: Fanpodium does not replace it — it feeds it identified, consented fan activity the CRM cannot capture today.
“Is this GDPR-compliant?”: We make no compliance claim. We describe how the system is built and supply documentation for the club's own legal review and DPA.

Engage. Inspire. Unite. — start with a pilot the club can judge on numbers.

Start a club pilot Pilot plan