Skip to main content
Back to home

TallyBaze Privacy Policy

This is the current version of this page. We may update it from time to time; the "Last updated" date below shows when it was last changed.

Last updated:

1. Introduction

TallyBaze (the "App") is a social app where friends record the results of casual games and sports matches, and where an AI "sports journalist" writes a short, humorous post about each confirmed match. This Privacy Policy explains what personal data we collect, why we collect it, who we share it with, how long we keep it, and what rights you have.

We try to collect as little as we need. We do not offer private messages, we do not run analytics tools in the App, and our website does not use cookies. The App can show ads served by Google AdMob, which is described in sections 3, 7 and 10.

This policy applies to the TallyBaze mobile app and the TallyBaze website. Some features described below (push notifications and in-app purchases) are marked "when enabled": they are planned but not yet active, and this policy will apply to them from the day they are switched on. We will not turn them on without making the necessary changes to this policy first.

2. Who is responsible for your data

The controller of your personal data is the TallyBaze team, the operator of TallyBaze. We do not currently present TallyBaze as a registered company or legal entity. Postal address: available on request through the Contact Us screen in the App.

You can reach us through the Contact Us screen in the App (Profile > Settings > Contact Us). For requests about your own data, use Privacy & data in the App Settings (see section 11). You can also email support@tallybaze.com, including if you cannot sign in or have no account (section 18).

We have not appointed a Data Protection Officer. All privacy questions and requests go to us through the channels above.

3. The data we collect

CategoryWhat it includesWhere it comes from
Account and sign-in dataYour email address (or an Apple "Hide My Email" relay address), the unique ID of your account, the sign-in method you used (Google, Apple or Facebook), and session tokensYou, and your sign-in provider
Profile dataUsername, display name, profile picture, short bio, preferred language (Arabic or English)You (some fields may be pre-filled from your sign-in provider and you can change them)
Match and game dataMatches you record or are named in, the game, the score or result details, whether you accepted or rejected a result, tournaments you organise or join, teams assembled for a single match or tournamentYou and other players
AI-generated postsThe news posts the AI writes about your matches and tournaments, in Arabic and English, which mention your display name or usernameGenerated by us from match data
Social dataWho you follow and who follows you, your reactions and comments, reports you submitYou
Virtual-economy dataXP, coin balance, trophies and badges, and a ledger of every XP and coin changeGenerated by the App and by us
Purchase dataWhen in-app purchases are enabled: the store (Apple or Google), product, transaction identifier and verification status. We do not receive your card or payment detailsApple or Google, and the App
NotificationsThe in-app notifications we create for you (for example "a result is waiting for your approval"). When push is enabled: a device push tokenThe App and us
Support dataMessages you send to our support team, their type and status, our replies, and the email address used to send you the replyYou and our staff
Moderation and safety dataReports about content, moderation actions (hidden posts, removed comments, bans), reasons given, and staff audit recordsYou, other users, our staff
Technical dataIP address, device and app version, and request logs processed by our infrastructure providers for security, abuse prevention, rate limiting and fault diagnosisYour device
Advertising dataWhen advertising is switched on, data collected by Google AdMob through its SDK to serve and measure ads. According to Google this can include your advertising ID, IP address, device and app information, ad interactions (impressions and clicks), an approximate location derived from your IP address, and diagnostics. We do not receive this data and do not link it to your account. We also keep, on your device, your choices in the consent promptsYour device, through Google's SDK

We do not ask for your date of birth, phone number, contacts, precise location, or any government ID. We do not intentionally collect "special category" (sensitive) data. Please do not put sensitive information (for example health, religion, political views) in your bio, comments or support messages.

4. What other people can see

TallyBaze is public by design. Accounts are public by default, and there is no private-account mode at this time. Other users can see your username, display name, profile picture, bio, XP, trophies, follower and following counts and lists, your match history, the AI posts about your matches, and your comments and reactions. Your match results appear in leaderboards and in posts seen by you, your opponents and, depending on the feed, your followers and other users.

When a match names you as a participant, the match and its result are visible to the other participants and may appear in their history and posts, even if you later change your display name.

Staff do not see your email address in everyday use. A staff member with the appropriate role can reveal it only through a logged action, and only for support, privacy-request or abuse-handling purposes.

We do not provide private messages between users.

5. Why we use your data and our legal bases

If the GDPR or UK GDPR applies to you, we rely on the following legal bases.

PurposeData usedLegal basis
Create and run your account, sign you inAccount, profileContract (Art. 6(1)(b))
Record matches, collect confirmations, calculate XP, leaderboards, tournaments, trophies and coinsMatch, social, economyContract (Art. 6(1)(b))
Generate AI posts about confirmed matches and tournamentsMatch, profileContract (Art. 6(1)(b)): this is the core feature of the App
Show you notifications about activity that involves youNotifications, profileContract (Art. 6(1)(b))
Push notifications (when enabled)Device push tokenConsent (Art. 6(1)(a)), which you give through the operating-system permission and can withdraw at any time in your device settings
Process in-app purchases and keep purchase and ledger recordsPurchase, economyContract (Art. 6(1)(b)); legal obligation for accounting records (Art. 6(1)(c))
Answer support requests and send replies by emailSupport, accountContract (Art. 6(1)(b)) or legitimate interests in helping users (Art. 6(1)(f))
Moderate content, handle reports, enforce our Terms, ban abusive accountsSocial, moderation, matchLegitimate interests in keeping the community safe and lawful (Art. 6(1)(f))
Protect the service: security, rate limiting, abuse and fraud prevention, fault diagnosisTechnical, accountLegitimate interests (Art. 6(1)(f))
Staff access to an email address through the audited revealAccountLegitimate interests (Art. 6(1)(f))
Handle your privacy requests and keep proof that we didAccount, request recordsLegal obligation (Art. 6(1)(c))
Establish, exercise or defend legal claimsAny relevant dataLegitimate interests (Art. 6(1)(f))
Show advertising through Google AdMob, and require a rewarded ad to create tournaments after your firstAdvertising dataConsent (Art. 6(1)(a)) where the law requires it, for example in the EEA and UK, collected through Google's consent prompt (UMP) and, on iPhone, Apple's tracking prompt; you can change your choice at any time (section 10). Google is an independent controller for its own advertising purposes. Outside those regions we show the choices that your device and local law require

Where we rely on legitimate interests, we have weighed them against your rights and expectations. You can object at any time (see section 11).

We do not use your data for automated decisions that have legal or similarly significant effects on you. Moderation decisions are taken by people. We do not sell your personal data.

6. AI-generated posts and OpenAI

When a match result is confirmed by the participants (or a tournament event occurs), our servers send a prompt to the OpenAI API asking it to write a short humorous post in Arabic and English. The prompt contains the names of the players (display name or username), the game, the result, and a short history of results between the same players (for example winning streaks). It does not contain your email address, your sign-in details or your support messages.

OpenAI acts as our processor. Under OpenAI's API terms, data sent through the API is not used to train its models by default, and may be retained for a limited period for abuse monitoring. We do not control OpenAI's systems, so please choose a display name you are comfortable seeing in a joke post. If you do not want to appear in AI posts, do not take part in recorded matches.

AI posts are created automatically and can be wrong, exaggerated or in poor taste. They are intended as entertainment and not as statements of fact. See the Terms for how to report a post. We review reported posts and can hide or correct them.

7. Who we share data with

We share personal data only as described here.

Other users. As described in section 4.

Service providers (processors). They process data on our instructions under data-processing terms.

ProviderRoleData
SupabaseDatabase hosting and authenticationAccount, profile, match, social, economy, support, moderation data
CloudflareApplication servers (Workers), key-value cache (KV), file storage (R2) for profile pictures and trophy icons, network security and website hostingAll data passing through the API; profile pictures; technical data
OpenAIAI generation of postsPlayer names, game and result details (section 6)
Google, Apple and Facebook (Meta)Sign-in providers, when you choose to sign in with themThe sign-in identifier and email address they pass to us. They are independent controllers of your account with them
Email delivery provider used for support repliesSends our replies to your email addressYour email address and the reply text
Firebase Cloud Messaging by Google (when enabled)Delivery of push notificationsDevice push token, notification content
Google AdMob (when advertising is switched on)AdvertisingData collected directly by Google's SDK on your device (section 10): advertising ID, IP address, device and ad interaction data. Google acts as an independent controller for its own ad purposes, not as our processor. We do not send Google your profile, match or support data
Apple App Store and Google PlayPayment processing and purchase verification for in-app purchases (when enabled)Purchase identifiers. They are independent controllers for your payment data

Authorities and legal reasons. We may disclose data where the law requires it, to respond to valid legal process, or to establish, exercise or defend legal claims, and to protect the rights, safety and property of users and of TallyBaze.

Business transfers. If TallyBaze is merged, acquired or sold, data may be transferred to the successor, which must honour this policy or give you notice and a choice.

We do not sell personal data for money. Advertising through Google AdMob involves Google collecting data from your device for advertising, which is described in section 10 and, for California residents, in section 17.

8. International transfers

Our providers operate globally. Your data may be processed outside the country where you live, including in the United States and the European Union, and the Cloudflare network processes requests at locations close to you.

Where the GDPR or UK GDPR applies and data goes to a country without an adequacy decision, we rely on the European Commission's Standard Contractual Clauses (and the UK Addendum or International Data Transfer Agreement where relevant), on an applicable adequacy framework such as the EU-US Data Privacy Framework where the recipient is certified, and on supplementary measures such as encryption in transit. You may request a copy of the safeguards by contacting us (see section 18).

If you live in a country whose law restricts transfers of personal data abroad, you accept such transfers to the extent they are necessary to provide the App, and we will comply with the transfer requirements that apply to us.

9. How long we keep data

We keep data only as long as needed for the purposes above. The table below shows the longest periods we intend to keep each kind of data. We do not yet run automated deletion for every category. Automated clean-up has been built but is switched off for now, so where it says "we aim to", deletion or anonymization is carried out by our team on a best-effort basis and may happen later than the stated period. We will tighten this wording once the clean-up runs automatically.

DataRetention
Account, profile, sign-in dataWhile your account exists. When you ask us to delete your account, we aim to anonymize your profile and to remove or disable your sign-in record, erasing its email address from our authentication provider, within 30 days (see the Delete Account page)
Accounts that have not been used for 24 monthsWe may anonymize them, using the same procedure as deletion. We aim to do this after 24 months without sign-in; it is not yet automated
Matches, results, tournaments and AI postsKept after your account is deleted in anonymized form, because they are part of other players' history. Your name in AI posts is replaced on a best-effort basis (see the Delete Account page)
Follows, reactionsDeleted when you delete your account (or when you remove them)
CommentsRemoved from view on deletion; the text is replaced by a placeholder
NotificationsWe keep them for at most 90 days and aim to delete them after that
Support tickets and repliesWe keep them for at most 24 months after the ticket is resolved and aim to delete the content after that; on account deletion the text is redacted earlier
XP and coin ledger, trophies, purchase records7 years from the transaction, for accounting and legal obligations. After account deletion they are no longer linked to an identifiable person
Moderation reports, bans, removal recordsWe keep them for at most 24 months after the case is closed and aim to delete or anonymize them after that
Staff audit logs (including email-reveal records)We keep them for at most 24 months and aim to delete or anonymize them after that
Privacy request recordsWe keep them for at most 3 years after completion, to demonstrate compliance, and aim to delete them after that
Technical and security logs at our infrastructure providersShort periods set by those providers, generally days to a few weeks
Advertising data collected by Google AdMobNot held by us. Google keeps it under its own policies as an independent controller (section 10)
BackupsDeleted data may remain in provider backups for up to 30 days, then expire

Where the law requires or allows us to keep data longer, for example because of a dispute or legal claim, we keep it until the matter is resolved.

10. Cookies and tracking

Our website does not use cookies, local-storage trackers, analytics or advertising pixels. Like any website, it is delivered by Cloudflare, which processes technical request data such as your IP address to serve and protect the site (see sections 3 and 7). The App does not use analytics tools. Advertising is described below. The App stores your session token on your device so you stay signed in; this is strictly necessary for the service.

Advertising (Google AdMob)

The App includes the Google Mobile Ads (AdMob) SDK. We switch advertising on and off from our server; while it is switched off the App does not request ads. When it is on:

  • Where you see ads. Banner ads appear between posts in the news feed. Your first tournament is free. To create a further tournament you watch one short rewarded video ad first. If no ad is available (for example no connection or no ad to show), you can create the tournament without it.

  • What AdMob collects. The SDK runs on your device and sends data directly to Google. According to Google, this can include your advertising ID, IP address, device and app information, ad impressions and clicks, an approximate location derived from your IP address, and diagnostics. Google is an independent controller of this data. It decides how it is used for advertising and measurement and how long it is kept, and we cannot see, export or delete it. To learn more, see Google's page "How Google uses information from sites or apps that use our services" (https://policies.google.com/technologies/partner-sites) and manage your Google ad settings at https://adssettings.google.com.

  • Consent. If you are in the EEA or the UK (or anywhere else the law requires it), Google's consent form (UMP) asks for your choice before ads are requested. On iPhone, Apple's tracking prompt asks whether the App may use your advertising identifier. If you decline, the App keeps working and you may still see ads, but they are not personalised using your advertising ID.

  • Changing your choice. In the App: Profile > Settings > Privacy & data. On iPhone: Settings > Privacy & Security > Tracking. On Android: Settings > Privacy > Ads, where you can delete or reset your advertising ID (the exact path depends on your device).

  • Children. TallyBaze is for people aged 13 and over (section 12). We do not direct ads at children, and we limit ad content to the "PG" level offered by AdMob.

We do not sell your data to Google and we do not pass your name, email, matches or other profile data to AdMob.

11. Your rights

Regardless of where you live, we offer you the following rights, in line with the GDPR and, where applicable, other privacy laws:

  • Access the personal data we hold about you and receive a copy.

  • Portability: receive your data in a structured, commonly used, machine-readable format. Our team prepares a JSON file on request (Privacy & data > Request a copy of my data in the App) and delivers it to you; there is no self-service download in the App. The file also includes moderation records about you and AI posts that mention you, but not other users' personal data.

  • Rectification: correct inaccurate data. You can edit most profile fields yourself in the App.

  • Erasure: delete your account and data. See the Delete Account page for exactly what is deleted, anonymized and kept.

  • Restriction and objection: ask us to limit processing, or object to processing based on legitimate interests.

  • Withdraw consent at any time, where processing is based on consent, without affecting earlier processing.

  • Not to be subject to solely automated decisions with significant effects. We do not make any.

How to exercise them. In the App, open Profile > Settings > Privacy & data. There you can ask for a copy of your data ("Request a copy of my data") or ask us to delete your account ("Delete my account"). Both requests go to our team, which handles them manually; nothing happens automatically. If you cannot sign in or have no account, email support@tallybaze.com with the same request. For any other request, use Contact Us in the App (Profile > Settings > Contact Us) or the same email address. A request made in the App is tied to your signed-in account, and our staff also verify your identity manually before acting. We will not ask for more information than needed, and we may refuse a request if we cannot verify that it comes from the account owner. We respond within 30 days. For complex or numerous requests the law allows an extension of up to two further months, and we will tell you why. Requests are free of charge unless they are clearly unfounded or excessive.

We may refuse or limit a request where the law allows, for example to protect another person's rights (we will not disclose other users' personal data in an export) or because we must keep data to comply with the law.

12. Children

TallyBaze is intended for people aged 13 and over and is not directed at children under 13. We do not ask for your date of birth, we do not verify your age, and we do not knowingly collect personal data from children under 13.

The Terms require users to meet the minimum age and, where the digital age of consent in their country is higher than 13, to have the permission of a parent or legal guardian if local law requires it. We do not collect or check that permission.

If we learn that a child under 13 has an account, we will delete the account and its associated data. Advertising in the App is not directed to children. Parents or guardians who believe a child has an account, and anyone who knows that a user is under 13, can tell us through the in-app support screen (Profile > Settings > Contact Us; see section 18) so that we can act.

13. Security

We use measures that are appropriate to the risk, including:

  • encryption of data in transit (TLS) between the App, our servers and our providers;

  • encryption at rest provided by our infrastructure providers for their databases and storage;

  • access to production systems and personal data limited to staff who need it for their role, with different roles for moderators, support and administrators;

  • audit logging of sensitive staff actions, including each reveal of an email address;

  • request rate limiting and network protection provided by Cloudflare;

  • verification of sign-in tokens on every request, and server-side validation of inputs.

No online service is completely secure, and we cannot guarantee absolute security. Please keep your sign-in method secure, and tell us immediately if you suspect unauthorized access.

14. Data breaches

If a personal data breach occurs, we will investigate and contain it, assess the risk to individuals, and, where the law requires, notify the competent supervisory authority within 72 hours of becoming aware of it. If the breach is likely to result in a high risk to you, we will tell you without undue delay, using in-app notices and, where we hold a usable email address, email. We keep a record of all breaches.

15. Changes to this policy

We may update this policy as the App or the law changes. For material changes we will give notice in the App, on this page or, where appropriate, by email, and where consent is required we will ask for it again. The "Last updated" date at the top shows the latest version. If you do not agree with a change, you can delete your account.

16. Complaints

Please contact us first (see section 18), and we will try to resolve your concern. You also have the right to complain to a data protection authority, in particular in the country where you live, work or where you believe an infringement occurred. In the EU/EEA you can find your authority on the website of the European Data Protection Board; in the UK it is the Information Commissioner's Office. Residents of other countries can contact their national data protection authority.

17. California residents

This section applies to California residents to the extent the California Consumer Privacy Act, as amended by the CPRA (CCPA), applies to us.

  • What we collect. In the last 12 months we collected the categories described in section 3: identifiers (username, email, account ID, IP address), internet or app activity within the App, user-generated content, and commercial information (virtual purchases and in-app purchase records). We collect them for the purposes in section 5.

  • Sale and sharing. We do not sell personal information for money. When advertising is switched on, Google AdMob collects identifiers and ad interaction data from your device through its SDK, and under California law this can count as a "sale" or as "sharing" for cross-context behavioural advertising. You can opt out by declining the tracking prompt or turning off tracking for the App in your iPhone settings, by deleting or resetting your Android advertising ID, and through the ad choices in Profile > Settings > Privacy & data (section 10). We do not knowingly sell or share the personal information of children under 13.

  • Sensitive personal information. We do not intentionally collect sensitive personal information as defined by the CCPA.

  • Your rights. You may request to know, access, correct and delete your personal information, and not to be discriminated against for using these rights. Use the methods in section 11. We respond within 45 days, and may extend by a further 45 days with notice.

  • Authorized agents. You can use an authorized agent; we may ask for proof of authority and verify your identity directly.

  • Retention. See section 9.

18. Contact

For any question about this policy or your data:

  • In the App: Profile > Settings > Contact Us. For requests about your own data: Profile > Settings > Privacy & data.

  • Email: support@tallybaze.com. Use it if you do not have an account or cannot sign in, and for any privacy request.

  • Operator: the TallyBaze team. Postal address: available on request through the Contact Us screen in the App.