What Roll On does with your team's information

At a glance

Roll On is a football team-management app for grassroots coaches in the UK. This policy is written for coaches using the app, and for parents or guardians of players whose details a coach has added. The app is distributed in the UK only and is intended for adult coaches and team managers — children do not use it themselves.

The same app runs on iPhone and on iPad, and this policy covers both. There is no separate iPad version and no separate iPad storage: an iPad reads and writes the same teams in the same iCloud account, which is what makes a squad entered on one appear on the other.

It covers the Apple Watch app too. The watch keeps no teams of its own: it shows what the paired iPhone sends it for the match being played — the clock, the score, the opponent's name, and the squad list when you are choosing a scorer — and sends your taps back. That exchange is between your own two devices, and nothing about it reaches the developer.

And it covers Siri. Asking Siri one of Roll On's questions is answered on the phone, out of the same teams already stored there. No player's name is added to the device-wide Spotlight index, nothing is sent to the developer, and Apple's own handling of what you say to Siri is covered by Apple's privacy policy rather than this one.

What information the app keeps

When a coach uses Roll On to manage a team, the app keeps the following in that team's private iCloud storage, rather than sending it to the developer. Where this information is stored sets out the one exception:

• Player details: name, squad number, preferred position, activity status, and match history — minutes played, goals, assists, player-of-the-week, and availability for fixtures. Because a squad is made up of children, Roll On has no way to add a photograph of a player: their avatar is their initials. Earlier versions did allow one, and any photo added then is deleted from your iCloud the first time this version opens.
• Coach and manager details: your name or display name, and your role on each team you're part of. If you use an invite code to ask to join someone else's team, the app also asks for the email address you sign in to iCloud with, so that team's manager can confirm it's really you before granting access. That address is kept with your coach record on the team, so it is visible to the manager and to the other coaches on that same team — it is not shown to anyone outside it.
• Team details: team name, colour, an optional club badge or logo, and squad size.
• Fixtures and events: opponents, dates, locations, formations, line-ups, substitutions, and any notes you add.
• Session plans you attach: a training session can carry a file — a club's drill PDF, or a photo of a whiteboard from your library. The app keeps the file you chose, with that session, and nothing else: it is not read, scanned, or looked at for what's in it. It is as sensitive as whatever you attached, so a photo of people is worth thinking about before you add it. Swiping the file away in the session's Session plan list deletes it.
• A match recording's address: if you paste the web address of a recording — a Veo page, usually — against a match, the app keeps that address with the fixture so you can open it again. It keeps the address only: no video, no still frame, and nothing about whether anyone watched it. Match recordings covers what happens when you open one.

Roll On does not ask for or store financial information, home addresses, health or medical records, or precise location data. It contains no advertising, and uses no analytics or tracking SDKs.

One thing the app has no say in: if you have left "Share With App Developers" switched on in your iPhone's or iPad's Settings → Privacy & Security → Analytics & Improvements, Apple gives the developer anonymous, aggregate figures — how many devices have the app, how often it's opened, and crash reports. That comes from Apple, is not tied to you or your team, and switching it off stops it.

Where this information is stored

All of the information above is stored in a private database in your own iCloud account, using Apple's CloudKit service. This is how the app keeps your data in sync across your own devices — an iPhone and an iPad see the same teams — and lets it survive a new phone.

• By default, this data sits in your private CloudKit database. Apple encrypts it in transit and at rest, and neither Apple nor the developer of Roll On can read its contents for their own purposes.
• If you use team sharing to invite another coach or manager to a team, the records for that team — including player names and details — become visible to that person too, through Apple's sharing mechanism. Only people you explicitly invite, and who accept, gain access.
• Inviting a coach or asking to join a team briefly uses a lookup area of Roll On's iCloud storage that isn't private to you and isn't limited to people you've invited — it's what lets an invite code or a join request be found by someone else's device. It holds nothing about players, and it is the only part of Roll On the developer is able to read.
• An invite code published there carries the team's name and the intended coach's name. It is deleted as soon as it's used or cancelled, and when the team it belongs to is deleted. A code that's simply left alone stops working after 7 days, and the device that created it deletes it the next time you open the app.
• A request to join published there carries your display name and the email address you sign in to iCloud with. Only the device that sent it can delete it — the manager can't, whichever way they decide — so your own copy of Roll On does it for you: as soon as the team syncs to your device, or, if the request is turned down or simply never answered, once it has lapsed at 14 days. Either way it happens the next time you open the app.
• A small "next event" summary is also stored locally on each device you use, so the home-screen widget can draw itself without opening the app. It holds every team's name, colour and a resized crest, and the next couple of events for each — their dates, and their titles, which for a match is the opponent and any score you've entered, and for training or anything else is whatever you called it. No player is named in it, and it never leaves your device.
• The developer of Roll On does not operate a server and cannot access what's stored in your iCloud account. Apart from the lookup area described above, no copy of your data reaches them.

Who can see a player's information

• The coach or manager who added the player.
• Any other coach or manager who has been invited to that specific team and accepted the invite.
• Nobody else. Roll On does not publish, sell, or share player or coach data with any third party, advertiser, or analytics provider.

Match recordings

A match can carry a link to its recording — a Veo page, usually. This is the one place the app will take you somewhere that isn't ours, so it's worth setting out plainly.

• Roll On stores the address you paste and nothing else, alongside the rest of that fixture in your private iCloud. It's entered in the match's Match Details sheet, under Video, and coaches you've invited to the team see it as they see the rest of the match.
• The Watch row on the match screen opens that page inside Roll On, in Safari's viewer — Apple's in-app browser. The page is the recording provider's, drawn by Safari, and deliberately keeps its own appearance rather than the team's, so it's clear you're not on a screen Roll On drew.
• Because it is Safari's viewer, it shares Safari's cookies and sign-in for that site: a coach already signed in to Veo in Safari is signed in here, and is not asked again. That also means the site can recognise you as it would in Safari, and the visit is subject to that site's own privacy policy, not this one.
• Roll On cannot see inside that page. It hands Safari an address and gets nothing back — not what you watched, not how long for, not who you're signed in as. Nothing about your team is sent to the recording provider by the app.
• Whether the recording itself shows players, and who at your club can reach it, is decided by the service holding it and by whoever set that up — Roll On neither uploads footage nor controls access to it.
• Clearing the link removes it: open Match Details, empty the Video field, and there is nothing left in Roll On pointing at the recording.

Your rights and how to exercise them

Because this data lives in your own iCloud account, you're in direct control of it at all times.

• View or correct a player's details at any time from their profile in the Squad screen.
• Delete an individual player from Player Details → Delete Player. This permanently removes their profile and match history from your device and your iCloud account.
• Delete an entire team, including every player, fixture and match history, from that team's Manage Team screen → Danger Zone → Delete Team. You can also selectively clear just the squad, the fixtures, or the events from the same screen.
• Remove a coach's access to a team from Manage Team, which stops them seeing that team's data going forward.
• Clear a match recording's link from that match's Match Details sheet, by emptying the Video field.
• Delete an attached session plan by swiping it away in that session's Session plan list.
• Leave a team you were invited to, if you're not its manager, from the team's ••• menu → Leave Team. That team's squad and fixtures stop reaching your device and go from it once iCloud catches up. Nothing is deleted for the manager or the other coaches, and you can be invited back.
• Stop sharing entirely by turning off iCloud for Roll On in your device's Settings app, or by signing out of iCloud — though this also stops your data syncing across your own devices.

Step-by-step instructions are on the support page.

If you're a parent or guardian and have a question about how a club or coach is using Roll On to store your child's details, the data controller is the coach or club who entered that information, not the Roll On developer — they're best placed to action a correction or deletion request. If you need help reaching them, or have a question about the app itself, get in touch at the address below.

Data retention

Information stays in your iCloud account for as long as you keep it in the app. There's no separate backend copy — deleting a player or team in the app deletes it from iCloud too, on your next sync.

The shared lookup area works differently, and it's worth being exact, because nothing there expires on its own — each entry is deleted by the device that put it there. An invite code goes when it's used, cancelled, or its team is deleted, and a code that's generated and then forgotten goes once it lapses at 7 days. A join request goes when the join completes, and one that's turned down or never answered goes once it lapses at 14 days — and only the device that sent it can do that, which is why it's your copy of the app that does. In every case the deletion happens the next time that person opens Roll On.

Children's information

Roll On is used by adult coaches to record details of youth players for team-management purposes — line-ups, substitutions, and playing time. We recommend that clubs and coaches using the app for youth teams do so under their existing safeguarding and parental-consent arrangements, for example an FA-affiliated club's standard registration consent, and enter only the minimum information needed to run training and matches.

This website

Everything above is about the app. The website is a separate thing, and worth being precise about: these pages are plain files. They set no cookies, run no analytics, and load nothing from anyone else's servers, so there is nothing here to consent to.

They are served by Cloudflare, though, and that part is not nothing. Like any host, Cloudflare handles every request and keeps its own logs, which include your IP address, to deliver the pages and to block attacks on them. It also adds two small scripts of its own to every page: one that spots automated traffic, and one that restores the address behind the contact links above, which is kept out of the page so that it cannot be collected and sold. Neither is analytics and neither is used to build a picture of you, but they are Cloudflare's rather than ours, and what Cloudflare does with request data is covered by its own privacy policy.

None of that tells us who you are. Nothing here is logged by us, and there is no account to tie a visit to; what we can see is Cloudflare's count of how many people came, not which people.

Changes and contact

If this policy changes, the "last updated" date at the top will change with it. Material changes will be reflected here before they take effect.

Questions about this policy, or a request to correct or delete something: send an email. Requests about a specific child's details are better directed at the coach or club who entered them, as described above.