Privacy policy

Who operates RTG

eFootball RTG, based in the United Kingdom, operates this service and is responsible for the personal information described in this notice. Contact efootballrtg.support@gmail.com about privacy, your account or the game.

1. The service this notice covers

eFootball RTG is an independent community football quiz and squad-building game. This notice covers its website, guest play, Google sign-in, saved clubs, squad upgrades, ranked matches, public player profiles, community posts and Creator Studio. The game is currently available as a beta. Contract signings and the virtual marketplace have been retired; historical records may remain as explained below.

2. Information used to run your club

• Guest sessions: we create a random browser session and a server-held club so you can return to your progress without registering.
• Google sign-in: Google and Supabase Auth process your selected account identity, email address, name and profile picture under the basic sign-in permissions. RTG validates the Supabase account and stores its identifier linked to your club. The game database does not copy your Google name, email address or profile picture into your club.
• Gameplay: we store your chosen display name, language, squad, cards, upgrades, virtual coins, formations, achievements, questions played, answers, timing, match results and rankings. Monthly ranked results and awards can remain after a phase ends.
• Public profile: we store social links you choose to add, selected badges and gameplay statistics, including average time for correct ranked answers.
• Community posts and reports: we store post text, author, language, timestamps and publication status. A report records the post, reporting account, selected reason, time and review status for abuse review.
• Historical economy records: records from retired contract signings, listings and card swaps may remain for progress preservation, fault investigation and transaction integrity.
• Community cups: we store room details, nicknames, participants, question snapshots, submitted answers, timing, scores and standings.
• Creator Studio: drafts and selected images are saved on your device. Saving to your account or hosting sends the relevant quiz content and images to the service. Uploaded images may retain embedded metadata.
• Support and security: if you email us, we receive the information you send. Hosting and authentication providers process network/request information. The app uses the connecting IP address to limit abusive request volumes.

Google sign-in is used to authenticate you and reconnect your saved club. The app does not receive your Google password or request access to your Gmail messages, Drive files, contacts or YouTube account.

3. Why this information is used

Information necessary to supply the features you request is processed to provide the service under our terms: maintaining your club, validating sign-in, scoring matches, completing squad upgrades, displaying your public gameplay profile and rankings, publishing posts, running rooms and saving your creator content.

We also use information for our legitimate interests in keeping the game secure and fair, preventing repeated rewards or transactions, reviewing abuse reports, investigating faults and answering support requests. We consider the impact on players and limit the information used for those purposes. We process information where necessary to meet a legal obligation, including applicable data-protection requests.

Google sign-in is optional for guest features. The permissions you grant Google and Supabase enable that sign-in; they do not permit unrelated use of your Google information.

4. What other players can see

Public profiles and rankings can be viewed without signing in. They show your chosen display name, public player ID, squad lineup and formation, rating, ranks, gameplay statistics, selected badges and any social links you add. Average ranked response time uses correct answers only. Your Google email, real name and picture are not added to these public views. Social links are optional and can be removed in your profile.

Community posts are public, including to guests, and link to the author's public profile. Avoid posting private information about yourself or others. Reports are held privately for review; the feed does not show the reporter's identity or report reason to other players. Deleting your own post removes it from the public feed, but retains a server record as described below.

In a cup, the host and participants can see nicknames, standings and scores. Questions are shown during the round; explanations, supporting sources and answer images are revealed afterward. People with the room code can join an open lobby. Closing a completed cup preserves results for its existing members and host; people who did not join receive only its finished or closed status. Hosts and participants may show the room on a stream or capture what they see.

Saved creator quizzes are account-restricted, but hosting shares their room snapshot with participants. Avoid uploading personal or confidential material. Remove personal information and unwanted embedded image metadata before uploading.

5. Cookies and storage on your device

• The functional guest-session cookie lasts up to 30 days. Signed-in app sessions last at most one hour, and can expire earlier with the provider session.
• A temporary sign-in cookie links the Google return to the browser that started sign-in; it lasts up to 10 minutes.
• Local storage remembers language and draft navigation. IndexedDB stores creator drafts and selected image bytes so editing can continue after a reload.
• Temporary session storage keeps community post drafts, helps resume a view after sign-in and prevents repeated actions.

Creator drafts have no automatic device expiry and are not erased when you sign out. Community drafts are scoped to the current player in browser session storage; signing out does not erase the stored text. Clearing the site's browser data removes local drafts, preferences and cookies, but does not delete server-held records. It can also remove access to an unsigned guest club.

The current app has no advertising SDK or separate visitor-analytics tracker. The game loads fonts from Google Fonts, so its visitors make requests to Google font servers even when playing as guests. This information website uses system fonts.

6. Service providers and external links

• Cloudflare: hosts the website and game API, stores game data in D1, and supplies network protections. See Cloudflare's privacy policy.
• Supabase: supplies account authentication and stores authentication records. See Supabase's privacy policy.
• Google: supplies Google sign-in, the game's font delivery and the support Gmail mailbox. See Google's privacy policy.

The current Supabase project is configured in Ireland and the game database uses Western Europe placement. Providers can process network requests, support information, logs and backups in other countries. Location settings do not guarantee that all processing remains in the UK or Europe. Contact us for information about the safeguards applicable to a transfer of your information.

Official game references and other external links lead to sites with their own privacy practices. We do not sell Google sign-in information, use it for advertising or provide it for AI model training.

RTG's use and transfer of information received through Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. It is used to supply account sign-in and related security, and shared with service providers only as needed for those purposes or where required by law.

7. Retention and deletion

Expired app sessions and sign-in transactions are cleared by a scheduled cleanup. Successful sign-in consumes its pending transaction. These actions do not delete your saved club or provider account.

We retain account links, clubs and creator content to let you return to them. Match, room, ranked-phase and historical transaction records support shared results, other players' progress, fault investigation and fair play. Community posts and reports support the feed, abuse review and rate limits. Retention depends on whether those purposes still apply, any request to delete information and any legal requirement to retain a limited record.

You can remove optional social links and delete your own community posts. Post deletion hides the post from the feed; its text and related reports remain in the database. It does not erase screenshots or copies others have made. Contact support if you need erasure of retained personal information.

The beta has no general automatic deletion schedule for these records and no in-app account, saved-quiz or image deletion control. Contact support to request deletion. Requests are reviewed manually and require ownership checks. A request involving shared matches, transactions, reports or room content needs individual assessment to protect other players' information. Provider backups and operational logs can remain subject to their applicable retention cycles.

8. Your choices and rights

Contact efootballrtg.support@gmail.com to request access, correction, erasure or restriction of your information, or portability where it applies. These rights depend on the processing involved and can have legal exceptions. We may need to verify ownership before disclosing or changing account information.

You can object to processing based on legitimate interests. Explain your circumstances when contacting us so we can consider your request. Where processing relies on consent, you can withdraw that consent without affecting processing already carried out lawfully.

You can sign out of RTG or revoke its Google connection from your Google Account. Neither action automatically deletes previously saved game records. RTG's “sign out everywhere” control revokes app sessions.

You can complain to the UK's Information Commissioner's Office or another applicable data-protection authority. Please also tell us about your concern so we can try to resolve it.

9. Young players and changes to this notice

The game does not ask for a date of birth. Players must meet the eligibility requirements of any Google account used to sign in. Parents or guardians with a concern about a young person's information can contact support; avoid including unnecessary personal details in the first message.

We will date changes to this notice and explain material changes through the website or game. If new features require additional information or permissions, the relevant notice will be updated before that use begins.