Privacy Policy — PronoGo

Last updated: August 29, 2026 Version: 1.4

1. Introduction

This privacy policy (“Policy”) explains how PronoGo (“we”, “our application”) collects, uses, and protects your personal data when you use the PronoGo mobile application (“the Application”).

PronoGo is published by Mehdi Bouhaouala, a sole proprietor (auto-entrepreneur) registered in France, whose contact details are available at the end of this Policy.

PronoGo is a mobile sports prediction game based on virtual currencies (tokens, pronocoins). No real money is wagered, no monetary winnings are paid out. The Application is free to use and is funded through optional in-app purchases (via Google Play and the App Store) and advertising (Google AdMob). See our Terms of Service for more details.

By using the Application, you acknowledge having read and accepted this Policy.

2. Data we collect

2.1 Data provided upon account creation

You can create your account in three ways:

Email + password: the email address serves as account identifier and for transactional communications (including the email address verification message). The password is stored as a secure hash by Firebase Authentication (never in clear text).
Sign in with Google: we receive from Google your email address, display name and, where applicable, your profile picture. We never receive your Google password.
Sign in with Apple: we receive from Apple your email address (or a private relay address if you choose “Hide My Email”) and your display name. We never receive your Apple password.

In all cases:

Display name: shown publicly in leaderboards, private leagues, and the friend system.

2.2 Data generated by your activity

Predictions made: matches, bet types, virtual token stakes, results.
Owned cards: collection, levels, evolutions, bonuses.
Deck lineups: weekly compositions.
Scores and rankings: weekly, monthly, season, lifetime.
XP level, completed missions, mini-games, mythic cards.
Private league memberships and friend list.
League chat messages: the text you post, your display name, and the date of posting. They are visible to the other members of the relevant league (see Terms of Service, section 5.3).
Reports: when you report a message or a player’s profile, we record a moderation file containing your identifier as the reporter AND that of the reported person, the league and message concerned, the reason you enter, and — for a profile report — the public display name of the reported person at the time of the report. A report file therefore holds data about two people.
Your list of blocked players: for each blocked player, their identifier and the display name they had at the time you blocked them (50 maximum). This list is visible only to you.
Referral (friend code): if you enter a referrer’s code (or someone enters yours), the referrer/referee link is recorded and your display name is visible to your referrer (and vice versa) in their referral tracking. No other personal data is shared through the referral system.
Card image you publish: when you share a card, the image generated by the Application (it is not a photo from your device) is stored on our servers at a public address, built from your technical identifier and the card’s. Anyone who receives the link — and the link-preview bots of WhatsApp, X or Facebook — can display it without being signed in. The folder cannot be browsed: an image can only be reached by knowing its exact address. The image is overwritten on each new share, deleted automatically after 30 days, and removed together with your account.
Support request: when you write to us from the Application, we record your message (1,000 characters at most) together with the technical context filled in automatically — Application version, platform, language and your identifier — so that we can reply.

2.3 Technical data

Firebase unique identifier (UID).
FCM token (Firebase Cloud Messaging) to send you push notifications.
IP address: collected by Firebase for security (anti-abuse) and country geolocation (store compliance).
Device type, OS, app version.
Crash reports (Firebase Crashlytics): in the event of a crash, a technical report is sent (device model, OS and app version, application state at the time of the crash, technical traces). These reports are used solely to fix bugs.
Performance traces (Firebase Performance): how long the Application takes to start and how long network calls take, without any of the content exchanged. They are used solely to spot slowdowns.
Advertising identifier (Android Advertising ID / Apple IDFA): used by Google AdMob for ad serving, subject to your consent (see section 4).

2.4 Transaction data (in-app purchases)

If you make an in-app purchase (virtual currency, card pack, welcome bundle), the transaction is entirely processed by Google Play or the App Store. We never see and never store your card number or payment details.

We receive and keep only: the identifier of the purchased product, a transaction token/identifier provided by the platform (to verify the purchase and credit your account), the date, and the transaction state.

2.5 Data we do NOT collect

Card number, bank details, payment information (handled exclusively by Google Play / App Store).
Phone number, postal address, full civil identity.
Precise GPS location.
Phone contacts.
Photos, microphone, calendar.

3. How we use your data

Your data is used exclusively to:

Provide the service: login, save your progression, calculate scores, resolve predictions via the api-football.com API.
Personalize the experience: rankings, recommendations, match and result notifications.
Social system: display your nickname in leagues, manage friend list, friend rankings, and referrals.
Process your in-app purchases: verify transactions with Google Play / App Store, credit purchased items, prevent fraud, and meet our accounting and tax obligations.
Secure the service: abuse detection, anti-cheat, rate limiting.
Improve the application: audience measurement (Firebase Analytics), crash reports (Crashlytics) and performance traces (Performance Monitoring). These three measurements are tied to your account identifier — so we do not present them as anonymous. Crash reports carry only a prefix of that identifier: enough to piece an incident back together, not enough to identify you.
Advertising monetization: display ads via Google AdMob (native ads and optional rewarded videos). See section 4 regarding consent.

We ask for your agreement first, and you can take it back. These three measurement tools start switched off and send nothing until you have accepted. You can withdraw that agreement at any time: Settings → “Analytics and diagnostics”. The withdrawal takes effect immediately on the device and applies to every subsequent launch; it requires neither writing to us nor deleting your account.

We never sell your data to third parties. Ads served via AdMob are filtered: we block sensitive categories (real-money competitor gambling, adult content, dating, politics, religion, etc.).

The Application displays ads via Google AdMob: native ads integrated into the interface, and “rewarded” videos that you voluntarily choose to watch in exchange for virtual rewards.

Consent (EEA / United Kingdom / Switzerland): before any personalized advertising, a Google UMP consent form (User Messaging Platform) is presented to you. You may accept or refuse personalized advertising; if you refuse, non-personalized (contextual) ads are served instead. You can change your choice at any time from the Application Settings.

If you consent, AdMob may use your advertising identifier (Android Advertising ID / Apple IDFA) to personalize ads. You can also reset this identifier or disable personalization from your device Settings → Privacy → Ads.

Rewarded videos: when you watch a video in exchange for a reward, your account identifier is passed to Google’s advertising network, which sends it back to us signed. It serves one purpose only: to verify server-side that the reward goes to the right person, and to prevent it from being claimed twice. It is not used for ad targeting.

Approximate location: we request no location permission, and the Application contains no geolocation component. Google’s advertising module nevertheless estimates a region from your IP address in order to choose ads. This is the only form of location involved, and it is why our privacy labels declare it.

On iPhone and iPad — tracking permission: Apple requires a permission separate from ours (App Tracking Transparency). If you grant it, your device’s advertising identifier (IDFA) may be used to track you from one app or site to another, including those of other companies. If you refuse it, it is not. This choice can be changed at any time in iOS Settings → Privacy & Security → Tracking. This permission is what explains the “Data Used to Track You” mention on our App Store listing.

The Application currently offers no subscription: all in-app purchases are one-time purchases.

5.1 Technical subcontractors

Google Firebase (Authentication, Firestore, Cloud Functions, Cloud Messaging, App Check, Analytics, Crashlytics) — EU hosting (region europe-west9), GDPR compliant.
Google Play / Apple App Store — processing of in-app purchases. These platforms process your payment data under their own privacy policies (Google, Apple).
Google AdMob — serves ads in the Application. Receives, subject to your consent, your advertising identifier and technical data (IP, device type, language) for ad targeting, as well as a region estimated from your IP address. It also receives your account identifier when you watch a rewarded video, solely to verify that reward (see section 4). Neither your email address nor your name is transmitted to it.
Brevo (company established in the European Union) — delivery of our emails: address verification, welcome message, replies to your support requests, internal moderation alerts. Receives your email address and the content of the message sent. EU hosting, encrypted transport.
api-football.com — provides match data (team lineups, scores, results, statistics). No personal data is transmitted to it.

We do not share any data with:

Social networks.
Data brokers.
Online gambling sites.
Competitor advertisers (FR bookmakers explicitly blocked in AdMob).

6. Retention period

Data	Duration
User account (users, user_scores, cards, predictions, lineups)	As long as the account is active
Notifications inbox	7 days (automatic TTL)
Daily claims logs	15 days (automatic TTL)
XP logs (xp_log)	30 days (automatic TTL)
Technical and security logs (server)	Up to 90 days
In-app purchase records (IAP transactions)	Legally required duration (accounting, tax and anti-fraud obligations), including after account deletion
League chat messages	30 days at most, and only the last 200 messages of each league are kept (automatic daily purge)
Your list of blocked players	As long as your account exists, or until you lift the block
Report files	90 days, by automatic purge. This duration is not arbitrary: the file acts as a lock against repeated reports, and the message it targets lives at most 30 days — three times that duration leaves room for review without keeping a trace that has become unverifiable. A file you submitted is also deleted when you delete your account, and a report targeting your profile is deleted when you delete yours
Card image you publish	Overwritten on each new share, purged automatically after 30 days, and deleted together with your account
Support requests	Kept for as long as needed to handle the request and to retain a record in case of dispute

Upon account deletion (via Settings → Delete my account), your personal data is irreversibly erased on the Firebase side, in compliance with Article 17 of the GDPR: account, cards, predictions, line-ups, friends, private messages, progress and history.

Six exceptions, and we would rather tell you about them:

What remains	Why	For how long
Purchase records	Accounting and tax obligation — Article 17.3(b) of the GDPR expressly covers this case	Statutory retention period
Messages you already posted in a league that carries on without you	Erasing them would leave holes in other members’ conversation	Automatically purged after 30 days
Your standings row in a league still in progress	Removing it would distort the result for the other participants. It is anonymized as “Deleted account”	Until that league ends
Your place in a finished season’s hall of fame	It is the shared history of the game; rewriting it would change other players’ standings. Only already public information appears there (display name, height reached, tier)	Kept
Aggregated, anonymized statistics	They are no longer linkable to you	Kept
Report files concerning a message you had posted	They document the handling of a report filed by another player. The message itself is already gone (30-day purge); only the moderation record remains	Kept as a moderation record

Everything else goes. See our dedicated page: Account Deletion.

In accordance with Regulation (EU) 2016/679, you have the following rights:

Right of access: see the data we have about you.
Right of rectification: modify your nickname, email, etc.
Right to erasure (“right to be forgotten”): exercise via Settings → Delete my account. Deletion is irreversible; the six exceptions are listed in section 6 (detailed instructions).
Right to portability: request an export of your data by email to pronogo.dev@gmail.com.
Right to object: refuse certain processing (e.g., push notifications, can be disabled in Settings).
Right to withdraw consent: at any time, and by the same gesture that gave it. For audience measurement, crash reports and performance traces: Settings → “Analytics and diagnostics”. For personalized advertising: Settings → “Ad privacy preferences” (a row present wherever European regulation requires it), or your device Settings. On iPhone and iPad, the tracking permission is withdrawn in iOS Settings → Privacy & Security → Tracking.
Right to lodge a complaint with your data protection authority (e.g., CNIL in France: www.cnil.fr).

To exercise these rights, contact us at pronogo.dev@gmail.com.

8. Security

Your data is protected by:

Encryption in transit: all communications with our servers use HTTPS/TLS.
Encryption at rest: Firebase Firestore and Authentication encrypt stored data.
Access control: strict Firestore rules preventing one user from accessing another’s data.
App Check: server-side abuse protection.
Strong authentication: Firebase Authentication, with email address verification.
Server-side purchase verification: every in-app purchase is validated with Google Play / App Store before being credited.

No system is infallible; we cannot guarantee absolute security, but we implement industry best practices.

9. Minors

PronoGo is intended for persons at least 16 years old. This restriction applies worldwide (GDPR Europe: article 8; in the United States and the United Kingdom: COPPA and UK-GDPR compliance through alignment).

Upon account creation, you explicitly declare being at least 16 years old by validating the consent checkbox.

If you become aware that a minor under 16 is using PronoGo, contact us at pronogo.dev@gmail.com — we will delete the account without delay.

10. Cookies / local storage

PronoGo stores locally on your device:

Firebase Authentication session token.
Offline cache of user data (Firestore persistence).
Preferences (language, theme, notifications opt-in, advertising consent choice).
Daily streak and advertising counters (SharedPreferences).
Your choice regarding audience measurement and diagnostics. It is stored on the device, not on your account: the tools concerned have only one switch per installation, and switching accounts on the same phone does not turn them back on.

The Google Mobile Ads SDK (AdMob) may use technical identifiers for ad targeting, subject to your consent (see section 4). You can reset your advertising identifier or disable personalization from your device Settings → Privacy → Ads.

11. Changes to this Policy

We reserve the right to modify this Policy. The “Last updated” date will be updated at the top of the document.

In case of substantial changes, we will inform you via in-app notification or email before the changes take effect.

12. Contact

For any questions or requests:

Email: pronogo.dev@gmail.com
Address: Mehdi Bouhaouala, Courbevoie, France

PronoGo is published by Mehdi Bouhaouala, sole proprietor (auto-entrepreneur), resident in Courbevoie, France. The application is free to use, with optional in-app purchases (virtual currencies and game bundles via Google Play / App Store, all consumable — no subscription) and advertising (Google AdMob — native ads and optional rewarded videos). This Policy will be updated if the publisher status evolves (company) or if new paid features are introduced.