Checklist
Eight privacy checks for a betting app
Check eight things about your data before you use a betting app: the App Privacy or Data safety section, the operator's privacy policy, tracking, marketing consent, how long data is kept, your right to a copy, how to withdraw consent and how to complain to the Data Protection Commission (DPC). Device permissions are covered separately.
Editorial team · checked
The eight checks
| # | Check | Where to look | Fail if |
|---|---|---|---|
| 1 | Store data section | App Privacy (App Store) or Data safety (Google Play) | It is empty, or it lists data the app does not need to run a bet |
| 2 | Privacy policy | The operator's own site and the app's settings | No policy, or it does not name who is responsible for your data |
| 3 | Tracking | The app's settings and the store data section | It tracks you and offers no choice |
| 4 | Marketing consent | Sign-up screens and account settings | Marketing is switched on for you with no clear choice |
| 5 | How long data is kept | The privacy policy | No retention period is stated |
| 6 | Right to your data | The privacy policy's rights section | It does not say how to ask for a copy |
| 7 | Withdrawing consent | The policy and account settings | You cannot find how to withdraw |
| 8 | Complaint route | The policy's contact section | It does not mention the right to complain to the DPC |
In short: eight checks, each answered by a store page, a policy or a setting.
The rules behind the checks
- GDPR and the Data Protection Act 2018 apply. The Data Protection Commission (DPC) supervises them.
- On a website, cookies that are not strictly necessary need your consent (reg 5 of the ePrivacy Regulations, S.I. 336/2011). Strictly necessary cookies do not. The DPC publishes guidance on cookies.
- The store sections are declarations by the developer. They are not an audit.
- Retention periods and rights wording in each operator's policy: Not checked.
In short: GDPR sets the duties; the DPC supervises; store labels are declarations.
Reading the store sections
- Read the ten listing checks first.
- Compare the data types listed with what a betting app needs: account details, payment and age check data.
- Device permissions such as location or camera are separate: see what the app asks the phone for.
- Notification and marketing settings: switching off notifications.
In short: read the labels against what a betting app plausibly needs.
If a check fails
- Check 1 or 2 fails. Do not install until the section or policy exists.
- Check 3 or 4 fails. Switch the choice off in the app. If there is none, do not sign up.
- Check 5 to 7 fails. Ask the operator in writing. Keep the reply.
- Check 8 fails. You can still complain to the DPC.
- The operator does not answer. Follow the order in complaints.
For your own login security, see securing your account.
In short: ask in writing; the DPC is the route if the operator does not answer.
How we checked
- Law: GDPR, the Data Protection Act 2018 and the ePrivacy rule on cookies, as recorded in our country notes.
- Still to capture: App Privacy and Data safety labels for three apps (snapshot D2); the privacy policies of three operators, for retention periods and rights wording.
- This site's own policy is on the privacy page. We did not install any app.
In short: the law is sourced; operator policies and labels are not checked.
What changed
- 7 November 2026: first version of this page.
In short: no earlier versions exist.
Keep going