Last updated: 17 October 2026
Football Playbook is a football planning app for creating and organizing plays, preparing game plans, studying plays, and exporting materials. The developer and data controller is Omari Sopromadze, based in Spain. For privacy questions or requests, contact [email protected].
Plays, drawings, playbook and player names, position assignments, imported images, game plans, study progress, and editor drafts are stored on your device. The current app does not provide an account or app-managed cloud synchronization, and does not upload this content to our servers, RevenueCat, or PostHog.
When you import an image, the app reads the image you select through the system picker. It creates a local image copy without retaining the source image’s EXIF or GPS metadata. It does not request access to your entire photo library.
If you export a PDF, image, or backup, you choose where it is saved or shared. Files saved through iCloud Drive or another provider, and device backups enabled through Apple, are subject to those providers’ policies. Recipients can access content you choose to share. We do not receive those exported files unless you send them to us, such as when requesting support.
We use PostHog to understand app use and improve the product. Events describe app launches and updates, screens visited, onboarding progress, and completed actions such as creating a play, importing an image, saving a game plan, studying plays, and exporting a PDF or backup.
Events may include timestamps, counts, bounded options such as an export format or formation template, app and operating-system versions, device characteristics, language or locale, and an app-generated identifier. Our providers also receive network information such as your IP address and may derive approximate location from it. The app does not request your precise location.
We do not include play, team, or player names, drawings, imported images, search text, or other user-entered playbook content in analytics events. Session replay and automatic capture of taps and text entry are disabled.
These identifiers are pseudonymous: the app does not ask you to register with a name or email, but events can still be associated with the same app installation.
Apple processes App Store payments. We use RevenueCat to validate purchases, provide subscription access, restore purchases, and support subscription management. RevenueCat receives an app-generated customer identifier, purchase and transaction information, product identifiers, subscription status, and technical information needed to deliver these services. We do not receive your full payment card details.
We connect the PostHog identifier with RevenueCat and use RevenueCat’s PostHog integration to understand subscription outcomes alongside product use.
The app enables Apple AdServices attribution through RevenueCat. Where Apple makes attribution available, this helps us understand whether an installation or subscription came from an Apple Ads campaign. This can include an attribution token and campaign-related identifiers or results. The app does not collect Apple’s advertising identifier (IDFA).
If you contact us, we receive information you provide, such as your email address, message, and any attachments or diagnostics you choose to send. Avoid sending unnecessary personal information or sensitive playbook content.