Privacy Policy

1. Scope and controller

This policy applies to the FietzBall apps for iOS, iPadOS and Android, including test versions, and this official website. FietzBall is operated by Matteo Fietta, an individual based in 36027 Rosà, Italy, who is the controller of the personal data described below.

Privacy questions and rights requests can be sent to privacy@fietzball.com.

2. Account and profile information

• On-device state: settings, cached progress and installation identifiers may be stored on the device. Current versions require a permanent account for Home, gameplay and cloud features; they do not create new Guest accounts.
• Email account: Supabase Auth processes the email address, authentication credentials and session information. FietzBall does not receive or store the password itself.
• Sign in with Apple: Supabase Auth receives the Apple identity token and the name or relay email Apple provides. Apple controls the underlying Apple ID and private relay service.
• Sign in with Google: Google authenticates the user and Supabase Auth processes the provider identity, email address and profile information supplied by Google, such as name and profile-image metadata. FietzBall uses the account identity for sign-in, profile and cloud saves; it does not receive the Google password. Google controls the underlying Google account.
• Profile: FietzBall stores the display name, optional avatar key and equipped cosmetic ball associated with the account.

3. Game and cloud-save information

To save and restore play across devices, FietzBall processes best score, stars earned and spent, experience and level, unlocked and equipped cosmetic balls, achievements, run and perfect-run totals, maximum combo, Daily Challenge progress, rewards and streaks, plus revisions and a random installation or device identifier used to reconcile offline progress safely.

The updated app also synchronizes Adventure completions and best times by account, importing existing account-scoped local saves when available. A local safety copy and pending changes support offline play and retry. New Infinite and Adventure game records include mode, world or stage when applicable, results and device-recorded dates; older history may be incomplete. Synchronization does not upload motion-sensor samples.

Use the same FietzBall account on each device. Different Google, Apple or email sign-ins are not automatically merged. Unsynchronized progress remains on the device until it can be uploaded; uninstalling before synchronization can remove that local copy.

4. Leaderboard and public profile data

When a signed-in player submits an eligible score, FietzBall may display the player's display name, equipped cosmetic ball, rank, best score and maximum combo to other signed-in players. Email addresses, authentication tokens and raw account identifiers are not shown on the leaderboard.

Server-issued run tickets and result records are used to validate ranked runs, reduce cheating and keep scores consistent.

5. Operational analytics

FietzBall has no third-party product-analytics SDK. It uses first-party operational statistics derived from its own account and game records, such as active players, new accounts, runs, perfect runs, Daily Challenge activity and leaderboard participation. A short presence heartbeat supports an owner-only view of currently online signed-in players. The owner-only directory includes account creation and last recorded app access, progress, balances, cosmetics and recorded game history. These administrative details are not public leaderboard data.

First-party ad observations may include format, display time, reward status and SDK-reported revenue and currency when available, linked to the signed-in account for restricted operational reporting. Missing data is not reconstructed and reported revenue is not a confirmed payout.

The free Android closed-beta configuration disables advertising, purchases and optional product-insights telemetry. Account, cloud-progress, ranking, presence and first-party game-history processing still operate. Authentication and hosting providers may process IP addresses, request metadata and security logs to operate and protect these services.

The public website is not configured with advertising trackers or an analytics provider. Its hosting and content-delivery infrastructure may still process standard network data such as IP address, request time, path, browser information and security logs to deliver and protect the site.

6. Purchases and advertising

Platform differences: the StoreKit and advertising features below describe the iOS and iPadOS app. The free Android closed beta does not offer in-app purchases or serve advertising; this does not mean it operates without account or gameplay data.

The separate Android Preview 25 APK available from this website enables Google AdMob test ads, not live advertising. The AdMob SDK and consent-related data processing described below also applies to this preview; test ads do not mean the SDK operates without data processing. Google Play purchases remain disabled in this APK.

FietzBall offers optional StoreKit purchases: non-consumable premium cosmetic balls and Remove Ads, plus consumable Continue-token and Star packs. Apple processes the payment, billing account, tax and refund information. FietzBall does not receive or store payment-card or bank-account details.

To verify and restore purchases, credit consumables once, and respond to refunds or revocations, FietzBall processes the product identifier, signed Apple transaction, original and current transaction identifiers, purchase and revocation times, StoreKit environment, and an app-account token linked to the signed-in FietzBall account. The trusted server verifies Apple's signature before recording an entitlement or wallet credit; the app cannot grant paid items from local data alone.

FietzBall uses Google AdMob to show occasional interstitial ads at game over and an optional rewarded ad when a player chooses an advertising-supported Continue. The app requests Google's consent information where required, offers the available privacy-options form in Settings and requests non-personalised ads. It does not request iOS App Tracking Transparency permission for cross-app tracking.

Google and its advertising partners may process device and app information, IP address, coarse location inferred from the IP address, advertising or other device identifiers made available by the operating system, ad impressions and interactions, diagnostics, consent choices and fraud-prevention signals to deliver, measure, secure and limit ads. Availability can vary by region and consent choice. FietzBall sends a pseudonymous account identifier and a random one-run ticket as server-side verification data for a rewarded Continue; Google returns the signed reward event and transaction identifier to FietzBall. The one-run ticket is used to prevent duplicate rewards.

Remove Ads suppresses forced interstitial ads for the signed-in FietzBall account. Optional rewarded ads remain available only when the player deliberately chooses them. FietzBall currently has no subscriptions.

7. Why the data is used

Data is used to authenticate players, provide the requested game and cloud save, restore progress, operate Daily Challenges, award progression, show fair leaderboards, prevent abuse, troubleshoot failures and maintain service security. Depending on the user's location, these purposes may rely on performance of the service contract, legitimate interests in operating and protecting the game, legal obligations, or consent where the law requires it.

8. Service providers and transfers

• Supabase: authentication and the FietzBall database, configured in a European Union region.
• Apple: Sign in with Apple, iOS distribution, StoreKit payments and Apple-controlled account or App Store records.
• Google: Sign in with Google and, when used, Google Play distribution and Google Groups tester enrollment. Google controls its own account, group-membership and store records.
• Google AdMob: advertising delivery, consent management, measurement, security and signed server-side verification of rewarded Continues.
• Website hosting and delivery: the infrastructure used to serve fietzball.com, including its content-delivery and security layer.

These providers process information under their own security, retention and international-transfer arrangements. FietzBall does not sell personal data.

9. Retention and security

Account, cloud-game, Continue-wallet and verified-entitlement data are kept while the account remains active because no shorter product-specific retention period is currently configured. Purchase and rewarded-ad transaction identifiers are retained to prevent duplicate credits and support fraud, refund and revocation handling. Leaderboard, entitlement, wallet and operational records linked to the account are removed from the active FietzBall database when the account is deleted through the in-app flow. Apple and Google keep their own records under their respective terms and retention rules. Provider backups and security logs may remain for their limited backup or legal-retention periods before expiring.

FietzBall uses authenticated database functions, row-level security, encrypted network transport and per-user access controls. No internet service can guarantee absolute security.

10. Deleting data and exercising rights

A permanent account can be deleted from Settings after an explicit confirmation. The request is authenticated on the server and deletes only the signed-in user's Supabase account and associated FietzBall profile, cloud progress, achievements, leaderboard scores, Daily Challenge records, presence and prepared entitlement records. The local session and local player data are removed only after the server confirms deletion.

You can also request account and associated-data deletion on the web, without installing or signing into the app. The page explains what is deleted, the email request steps, ownership verification and the limits relating to backups, security records and independent service providers.

Deleting a FietzBall account does not delete the user's Apple or Google account, erase Apple's transaction history or Google's advertising records, cancel a purchase or request a refund. Unused consumable credits linked only to the deleted account are not restorable. A qualifying non-consumable may be restored later from Apple's records after signing in to a permanent FietzBall account. Apple authorizations can also be managed from the user's Apple ID settings.

Depending on applicable law, users may request access, correction, deletion, restriction, portability or an objection by emailing privacy@fietzball.com. Identity verification may be required before a request is fulfilled.

11. Children and changes

A player must be at least 14 years old to create a FietzBall account independently. A younger player may not create an account unless a parent or legal guardian has lawfully authorised the use and the related processing of personal data. If a parent or guardian believes a child has provided personal data without valid authorisation, contact the privacy address.

The planned Google Play closed beta is limited to adults aged 18 or over in Italy. This beta audience does not change the account rules for other versions of FietzBall.

This policy may be updated when the game or its providers change. Material changes will be reflected on this page with a new date.

Last updated: 27 October 2026.