Skip to content
BallerBase

BallerBase · Website & Android

Privacy Policy

Your football. Clear information about your data.

How BallerBase handles information on its website and native Android app, and the choices available to you.

Effective date
Last updated

This policy describes the current implementation. It is not a certification of legal compliance. Some provider settings and retention practices require further operator verification; no universal deletion deadline is promised.

1. Introduction and scope

BallerBase is operated by Yassine Ben Romdhane. This policy covers theballerbase.com and the native Android application with package name com.ballerbase.app. It distinguishes website services from Android features; browser storage and Android app storage are different systems.

You can browse public football information without creating an account. Website accounts and some connected features are optional. The current native Android app does not provide account registration or sign-in. This policy does not replace the privacy notices of external services you choose to use.

2. Information handled

Website device data can include favorites, saved lineups, searches and recent items, language and theme choices, dashboard arrangement, game scores, learning progress, match filters and notification preferences. An optional activity recap records timestamped activity only when enabled; its local history is capped at approximately 5,000 events.

Optional website accounts can hold a username, display name, password and recovery-code hashes, creation information, saved preferences and lineups, prediction-group memberships, predictions and votes. Registration does not currently require an email address. A privacy request sent by email contains the information you choose to include.

The Android app saves favorites, settings, game boards, lineups and learning progress in its own local storage, and caches public responses for offline use. It does not currently request Advertising ID, precise-location, contacts, camera or microphone access.

Online requests can expose connection information such as IP address, request time and technical browser or app information to hosting and service providers. Some backend features use hashed IP-derived rate-limit or quota identifiers. Actual platform log fields, retention and backup settings have not all been verified.

Private friend games handle a guest display name, room code, participants, game choices, scores, private roles and temporary connection offers. Offers may contain private or masked local-network addresses. The room service uses guest-token and IP-derived hashes for access and rate limits. No public room directory or random matchmaking is provided.

3. How information reaches us

Information is handled when you use a feature, enter account details, save a preference, send a privacy email, request tutor help, enable browser notifications or permit optional analytics. Essential cookies and local device storage support the features described below.

Public football-data requests usually retrieve information about teams, players and fixtures through BallerBase's server integrations. Loading an external image, opening a news source or playing embedded media can also create a connection to that external provider.

4. Why information is used

Information is used to provide and remember requested features, authenticate optional website accounts, synchronize supported account saves, deliver opted-in browser alerts, process votes and predictions, answer tutor questions, respond to requests and help protect the service from abuse.

With website analytics consent, usage and performance events help us understand navigation and technical performance. We do not describe optional analytics as necessary for browsing football information. We do not use the native app's local game progress as an advertising profile in the current implementation.

5. Local storage and cookies

On the website, browser local storage, session storage and cookies retain preferences and temporary state. Local saves generally remain until you clear them, reset the feature or clear site data; there is no single automatic expiry for every preference. Clearing browser data can remove unsynchronized saves.

The website language cookie can last up to one year. Authenticated account-session cookies expire after seven days, and guest voting-session cookies after 30 days. Account and guest session cookies use Secure, HttpOnly and SameSite protections. Expiry does not guarantee immediate removal of every server-side record.

The Android app uses local DataStore settings and an app database/cache, not the website's browser cookies. Cloud backup and device transfer are excluded by the audited app configuration. To remove Android-local saves and cached data, use Android Settings, open BallerBase's app-storage controls and clear its storage; uninstalling also removes app-local data. This does not itself delete a separate website account.

Use the website's Privacy preferences control on main-page footers to change analytics consent. You can also manage cookies and site data in your browser. The optional recap provides a Clear activity control. Shared lineup or comparison links may reveal encoded selections or names to anyone with the link; do not put confidential information in shared titles.

Private friend games use an HttpOnly, SameSite guest-session cookie for up to seven days; the published HTTPS service also sets Secure. Room membership and local-connection verification are separate from knowing a room code. Browser-local game preferences and optional personal result records can be cleared with site data.

6. Analytics, advertising and diagnostics

The website's Google Analytics loader is gated on analytics opt-in. Essential only keeps that optional loader disabled. Consent withdrawal disables future analytics events from the site, but does not undo data already sent or automatically erase every provider cookie. Browser cookie controls can be used separately.

AdSense requests are currently paused in the reviewed website implementation. Publisher-account verification metadata and ads.txt may remain. These verification entries do not mean that ads are currently being requested. If advertising is enabled later, appropriate disclosures and consent arrangements must be in place; analytics consent is not a substitute for an advertising consent platform.

The reviewed Android build has no enabled AdMob, analytics, Firebase Messaging or dedicated third-party crash-reporting SDK. Android, Google Play and hosting providers may produce their own operational diagnostics under their respective services. Future SDK changes must be reflected in this policy and the app's store declarations.

7. Services, football data, tutor and notifications

Netlify provides website hosting and backend functions; connected features use Netlify Blobs for server records. API-Football/API-Sports and other cited football sources provide football information. Provider coverage, schedules and attribution differ. API credentials remain server-side; a football-data source is not automatically an analytics service installed on your device.

When you tap Ask in the tutor, your question, language, answer style and lesson context are sent to BallerBase. The website may also include a previous question and learning level. When the online AI provider is enabled, relevant content is sent to Google's Gemini service. The backend requests store:false, but that flag is not a guarantee of zero provider retention. The reviewed tutor handler does not intentionally store a conversation history; it keeps quota counters and rotating daily hashed-IP identifiers. Do not send personal or sensitive information in tutor questions.

Website translation features can use stored dictionaries and, when configured, a server-side Gemini service for missing public site text or published news. The reviewed translation endpoint restricts this to allowed public text, not private custom lineup names or user questions. This Privacy Policy's language versions are supplied as static pages and do not require that translation endpoint.

Browser match alerts require an explicit permission/subscription action. Stored notification records can include a random device ID, subscription endpoint and encryption material, token hash, selected fixtures, event types, spoiler preferences and timestamps. Delivery uses browser push services, which may be operated by Google, Mozilla, Apple or Microsoft. This is not evidence of a Firebase SDK in the native app. Native Android push registration is not currently enabled.

Supabase hosts private friend-room state and connection coordination in the configured EU Central region. The service is used to exchange room and game data; the local-connection check uses direct WebRTC data channels without configured STUN or TURN servers. This checks private-network reachability, not a Wi-Fi network name or GPS location. It is not a guarantee of physical co-location.

8. Sharing and disclosure

Information may be handled by hosting, storage, AI, analytics or browser-push providers as needed for the feature you request or the consent you give. External destinations receive the requests made to them. Provider roles and contractual terms can differ; the Google Play Data Safety definition of sharing is not identical to every disclosure described in this policy.

Members of a website prediction group may see member display names and leaderboard results. Voting views generally expose aggregate totals and your own selection, rather than a public list of named voters. Content you explicitly share, including an exported lineup image or a shared link, is disclosed to the recipients or service you select.

Information may also be disclosed where required by applicable law, a valid legal process or a necessary investigation of security or misuse. We do not claim that use of the service means your information can never reach another organization.

9. Retention and deletion

Retention depends on the record and feature. Local preferences generally persist until cleared. Website account records do not currently have a general automatic expiry; they remain until deleted or otherwise removed. Session and rate-limit records have technical expiry/maintenance rules, but cleanup runs in bounded passes, not as a guaranteed deletion deadline.

For a website account, open the account controls to use Export my data or Delete account. Deletion requires the account password and the requested confirmation. The implemented process removes the account, its sessions and supported related group, prediction and player-of-the-match vote records, with retry handling. Browser-local saves remain unless you clear them separately.

Complete removal of every vote or poll record is not guaranteed by the current automated account-deletion flow: some newer poll and guest-vote records are outside that cleanup. Browser-push device records and tutor quota counters also have no verified universal deletion schedule. Disabling browser alerts clears the stored subscription but can leave a device record. Contact the privacy address for a review of an outstanding record or request.

Hosting logs, provider records and backups can have separate retention settings. Those settings and processing regions have not all been confirmed, so this policy does not invent fixed retention periods or promise immediate deletion from every system. Applicable legal and security requirements may affect what can be removed. Do not email your account password or recovery code.

Friend rooms expire after 24 hours. Expired rooms and rate-limit records are normally removed by hourly database maintenance while the service is running. Connection offers are removed on successful verification or with the room; failed pending requests become unusable after their short deadline. Hosting logs and backups have their own provider retention. Closing a game does not promise immediate deletion of all room records.

10. Security

The public service uses HTTPS. The native app disallows cleartext network traffic in its configuration. Account passwords and recovery codes are stored as hashes, rather than deliberately retained as plaintext by the reviewed account handler. Session protections and rate limits help protect connected features.

Security measures reduce risk but cannot guarantee that every device, transmission or service will be completely secure. Protect your credentials and recovery code, use device security controls, and avoid placing private information in public names, group content, shared links or tutor questions.

11. Choices, rights and requests

Depending on the law that applies to you, you may request information about our handling of your personal information, access or correction, withdrawal of consent for optional processing, deletion where applicable, or a review of a privacy concern. Consent withdrawal may prevent a feature from working; it does not automatically reverse past processing.

Email the public privacy contact with enough context to identify the account or issue. We may need proportionate verification before disclosing or changing account information. Do not send passwords, recovery codes or identity documents in an initial email. We will consider requests under applicable requirements; this policy does not promise an invented response deadline or an unconditional right to erase every record.

Canadian privacy requirements may include federal or provincial laws depending on the circumstances. You can also seek guidance or raise concerns with the relevant privacy regulator, including the Office of the Privacy Commissioner of Canada where applicable.

12. Children and consent

Age and parental-consent requirements vary by jurisdiction and by a person's ability to understand the processing. There is no single worldwide age threshold asserted by this policy. The Canadian privacy regulator generally expects parental or guardian consent for children under 13, while capacity and maturity also matter.

The current service does not have a verified age-assurance or parental-consent system for every feature. Children should use the service with a parent or guardian and should not submit personal or sensitive information through optional accounts, group names or tutor questions without appropriate consent. If you believe a child has provided personal information without necessary consent, contact us for review. The operator must keep the intended audience and store declarations consistent with the features actually offered.

13. International processing

BallerBase and its providers may handle information outside Canada, in places with different privacy laws. The location of every log, backup and provider operation has not been confirmed; no Canadian-only storage claim is made. Information processed abroad can be subject to lawful access in that jurisdiction.

We remain responsible for considering appropriate arrangements for providers processing information on our behalf. Contact us for questions about relevant service providers or cross-border handling; contractual and account-specific provider settings require operator review.

14. External sites and media

News reports, creator profiles, social channels and other references can link to external websites. Website entertainment features may load YouTube thumbnails and an embedded YouTube player when played. Some other images are served by third parties. These connections can transmit normal request information and may involve the provider's cookies or signed-in account.

The Android entertainment section opens YouTube or a browser for external videos; it does not bundle those videos as native content. Selected training or GOAT clips stream from the BallerBase host. Once you open an external service, its own terms, privacy practices and settings apply. A source link or an image credit does not transfer all underlying content rights.

15. Policy updates

This policy may change when BallerBase's features, providers or data practices change. The effective and last-updated dates appear on this page. Material changes may require an additional notice or a new consent choice where applicable. English is the default version; French, Spanish, Arabic and German versions are provided with the same intended meaning.

16. Contact

Privacy contact: BallerBase — Yassine Ben Romdhane. Public business contact: ybenromdhane3@gmail.com. Use this address for privacy questions, access/correction requests, deletion concerns or complaints. Do not send passwords, recovery codes or confidential identity documents.

17. Effective and updated dates

Effective date: 20 November 2026. Last updated: 20 November 2026. This policy covers both the BallerBase website and the native Android application com.ballerbase.app as described above.