Footy Ready is built to collect as little as possible. There is no account, no server of the developer's, and no analytics in the App Store release. It also offers an optional iCloud backup, off unless you turn it on. See "iCloud backup" below for what that changes. Here is exactly what all of this means.
Everything Footy Ready remembers is stored locally on your device using Apple's SwiftData framework: your training profile (birth year and month, equipment, goals, session length, any injuries you have flagged), your season dates, your daily readiness check-ins, and every session you log. By default, none of it leaves your device on its own. If you turn on the optional iCloud backup feature, that changes. See the next section.
Footy Ready has an optional backup feature, off by default, that you turn on yourself in Settings. Once it's on, your training profile, your season dates, every daily check-in, and every session you log are copied to your own iCloud account, using Apple's CloudKit and your own private database, so they come back if you lose your phone or get a new one. Footy Ready has no server and never sees your training, backed up or not.
Your assessment answers, including any injuries you have flagged, and your daily check-ins are encrypted before they leave your device, with a key only your own devices hold. Apple cannot read them, and neither can the developer.
Apple's iCloud servers are not located in Australia, so turning this feature on does mean your data leaves the country. To be precise about what that does and does not mean: your data goes to your own Apple Account, under Apple's terms, and the developer has no access to it at all, in any country. No third party of any kind receives it from the developer, because the developer never holds a copy to send.
Turning the feature off in the app keeps the copy already on your phone and does not delete what is already in iCloud. You can remove that copy yourself at any time: on your iPhone, go to Settings, then your name, then iCloud, then Manage Account Storage, and remove Footy Ready's data there.
Footy Ready asks for a birth year and month, not a full date of birth, and uses it only on-device to apply age-appropriate content rules, for example keeping the training load conservative and never showing a weight-loss goal to an athlete under 18. It is never sent to the developer or to any third party. If you turn on iCloud backup, it forms part of your training profile and is copied to your own iCloud account with the rest of it, encrypted before it leaves your phone.
Settings in Footy Ready includes a "Prepare your data export" button that builds your profile, season dates, every check-in and every logged session into a single JSON file on your phone, which you can then share yourself, by email for example, if something looks wrong and you want to send it to the developer. This is entirely manual and opt-in: nothing is built or sent unless you tap that button yourself, and nothing happens automatically.
Footy Ready does not include any crash-reporting SDK. If you have opted in to iOS's own "Share With App Developers" setting (Settings → Privacy & Security → Analytics & Improvements), Apple may send the developer anonymised crash diagnostics through Xcode. This is Apple's own, user-consented mechanism, not something Footy Ready adds.
Footy Ready's subscription is processed entirely by Apple through StoreKit. The developer never receives or has access to your payment details. That relationship is between you and Apple.
Footy Ready gives general fitness guidance, not medical advice, and is not physiotherapy or rehabilitation. While an area is flagged as sore, the app leaves its work out of your plan rather than training around it. See a health professional about anything more than that.
Footy Ready carries a 13+ age rating and is not directed at children under 13. It does not knowingly collect any information from anyone under 13.
If this policy ever changes, for example if a future version of the app adds a feature that shares data differently, this page will be updated and the date above will change.
Questions about this policy: mattsappdevelopment@gmail.com
