Terms & privacy pages for your branded pool: what to include
By Dirk Menkveld on Thursday, April 9, 2026
Terms and privacy pages for your branded pool: what to include
If you run a branded pool, clear legal pages matter.
They help people trust your game.
They also help you set fair rules.
And they can cut down on support issues later.
On GoKoppa, Fantasy Football (is Prediction Game in English) means a game where people predict match results. They do not select players. That point should be clear on your site and in your rules.
This guide shows what to include in your terms, privacy policy, and legal pages for a prediction pool.
Why these pages matter
A fun game still needs clear rules.
Your pages should help people know:
- who runs the pool
- who can join
- how scoring works
- what data you collect
- how you use that data
- how people can ask for help
- what happens if there is a dispute
If you explain these points well, your pool feels safer and easier to join.
Start with a simple terms page
Your terms page is your rule book.
Keep it short. Use plain English. Add headings.
Include these key parts:
1. Who you are
State:
- your brand name
- your website address
- a contact email
- your country or region, if needed
This tells users who runs the pool.
2. What the game is
Explain the format in one clear line.
For example:
This pool is a football prediction game. Players score points by predicting match outcomes and scores.
Also say that users do not build a squad or trade players.
3. Who can join
Set basic entry rules, such as:
- minimum age
- country limits, if any
- one account per person
- no fake names, if that matters for prizes
4. How scoring works
This part should be very clear.
List:
- how many points each correct prediction earns
- what counts as a valid entry
- when picks lock
- how tie-breaks work
- how leaderboards update
If prizes exist, explain:
- what the prizes are
- when winners are confirmed
- how prizes are sent
- when a prize may be withheld
5. Fair play rules
Add rules to protect the game.
Examples:
- no cheating
- no duplicate accounts
- no abuse of bugs
- no harmful or rude content in names or messages
Say that you may remove users who break the rules.
6. Changes and errors
Sometimes fixtures change. Tech issues happen too.
Say that you may:
- correct obvious scoring errors
- change deadlines if match times move
- suspend or close the pool if needed
Keep this fair and transparent.
Build a privacy page people can understand
A privacy page should not feel scary.
Use short sections and simple words.
1. What data you collect
Tell users what you collect, such as:
- name or username
- email address
- login details
- prediction entries
- IP address or device data
- cookie data
Only list what you really use.
2. Why you collect it
Explain the reason for each type of data.
Common reasons are:
- to create accounts
- to run the pool
- to show leaderboards
- to send game updates
- to prevent fraud
- to answer support requests
3. Your legal basis
If your users are in places with privacy rules, explain the legal basis in simple terms.
This may include:
- consent
- contract
- legal duty
- legitimate interests
For a helpful example of clear privacy guidance, see the ICO guide to privacy notices.
4. How long you keep data
Tell users:
- what data you keep
- how long you keep it
- when you delete it
Example:
- active account data: while the account stays open
- support emails: up to 12 months
- marketing consent records: until consent is withdrawn
5. Who you share data with
Be honest here.
You may share data with:
- email service tools
- analytics providers
- hosting providers
- prize fulfilment partners
State that you only share what is needed.
6. User rights
Tell people what they can ask for.
These rights may include:
- access to their data
- correction of wrong data
- deletion of data
- limits on some uses
- withdrawal of consent
Also explain how they can contact you.
Do not forget your cookie note
If you use cookies or tracking tools, say so.
A short cookie page or banner should cover:
- essential cookies