Flipward Privacy Policy

Last updated: October 22, 2026

Request data deletion

LiteFeel develops Flipward (Android package: com.litefeel.flipward). This policy describes the current age-screening and Play Games update, including test builds. Availability depends on the installed build, Google account, region and release channel; publishing this policy does not mean the update is available on Google Play. The full local game can be played without sharing age information, enabling diagnostics, or signing in. The current update has no advertising, in-app purchases, player chat, cloud saves, or revives.

Earlier builds retain their own behavior until updated. The earlier 0.3.1 release candidate used a manually changeable under-18 / adult / unknown age choice and one combined diagnostics choice, and did not set a Firebase player user ID. Earlier 0.3.0 test builds offered optional diagnostics and feedback without an age screen. The age-screening, separate permissions and player-ID association below apply to builds containing those features.

ON-DEVICE GAME DATA

Flipward saves route unlocks, star ratings, a no-revive endless high score, sound preferences, practice completion, local achievements, separate diagnostic choices, and an age-screening record on your device. The age record contains a screening version, source, age category, confirmation state, and applicable restrictions; it does not contain your birthday. LiteFeel cannot remotely access your game save. Clearing app storage removes these local records and resets progress and choices. Device backup services may handle app data under the platform provider's policies.

AGE INFORMATION

On Android the game first requests age information using Google Play Age Signals. Google may ask you or your parent whether to share an age range. Google returns a range, its source, and applicable parental approval status; it does not provide an exact birthday. The game uses these signals only for age-appropriate access and compliance, not advertising, profiling, or analytics, and does not forward them to Firebase, Tally, or other third parties. It does not retain the API's installation identifier.

If Google does not share an age range or the service is unavailable, and there is no known mandatory platform restriction or previously confirmed age, you may enter a date of birth in empty fields or skip. The date is processed in memory on the device to calculate an age category, is not saved or uploaded, and is cleared when leaving the page. Skipping leaves age unknown, with local play available and the option to provide age information for the first time later. Once age is confirmed, the game offers no manual age changes. Google's newer signals can update the effective category automatically.

While a Google query is pending, SKIP on the waiting screen opens optional birthday entry if age has never been confirmed and no mandatory restriction is known. The query continues in the background. A manually confirmed category does not enable online features until the query resolves; current platform verification and parental restrictions still take priority. SKIP on the birthday page leaves age unconfirmed and allows local play.

When Google returns NOT_SHARED, the game offers optional birthday entry to users who have never confirmed their age and have no known mandatory restriction. Skipping keeps age unknown. An existing valid manually confirmed category is retained; it cannot be manually edited. Required Play verification or parental restrictions cannot be bypassed by typing a date. Platform results take priority over an earlier manual record. Saved platform age alone does not authorize SDK startup in a new process. The game refreshes platform age after startup and relevant returns from the background. Older age-button selections are invalidated on update; diagnostic choices and pending online submissions are cleared while local gameplay progress is preserved.

OPTIONAL GOOGLE PLAY GAMES

The game's current product rules permit Play Games for age categories 13–17 and 18+, subject to Google account eligibility, parental controls, platform approval, and applicable regional requirements. These product thresholds are not universal legal age limits. Children below that category and users with unknown age keep local play without Play Games initialization. Eligible players may encounter Google's sign-in or profile screen and can cancel. Signing in does not grant diagnostic permission.

The game offers nine active local achievements and one active online no-revive endless leaderboard. Google processes authentication, player identifiers, gamer names and avatars, achievements, banked scores, and technical information under its policies. Play Games also collects its own SDK analytics and diagnostics for service stability and improvement, independently of the game's Firebase choices. Google's UI may display your profile and scores according to your Google profile visibility settings. The game uses the player ID for authentication and account-bound submissions; it does not copy your gamer name or avatar into Firebase. Flipward does not create a separate LiteFeel account. Google manages the account and any Play Games profile setup.

Eligible players' builds may automatically attempt Play Games authentication after the age check. You can cancel Google's screen or turn off Play Games in PRIVACY. The device stores account-bound pending scores and achievement claims and retries for the same authenticated account; it does not transfer claims across accounts or upload scores earned without authentication. Removed legacy leaderboards and the former revive achievement receive no new submissions from this build, although Google's native UI may still display backend historical entries. Uninstalling does not delete information already held by Google. You can delete Flipward's Play Games data or your Play Games profile through Google's controls: https://support.google.com/googleplay/answer/9130646. Deleting Google-held game data does not by itself delete LiteFeel's diagnostic or feedback records.

OPTIONAL ANDROID DIAGNOSTICS

The analytics and crash-report choices initially have no selection. Eligible adults must explicitly select ALLOW or DECLINE for each before continuing; declining both allows the full local game. No collection is enabled by leaving a choice untouched. Restricted or unknown-age users continue locally with these options unavailable. Saved explicit choices are restored on later visits and can be changed independently. Diagnostics are off by default. They are available only when the resolved age category is 18+ and the player separately allows each option in PRIVACY. Firebase automatic startup initialization is removed. After an eligible adult age result and the first game frame, the game initializes Analytics and Crashlytics with Analytics collection and automatic crash upload off unless the player has separately allowed the corresponding option. Initialization and SDK dependencies may still perform local processing or make network requests. Crashlytics may store crash information locally while upload is off; the game clears pending SDK reports before enabling crash upload. Game analytics events from before consent are discarded. Game events cover route starts and outcomes, retries, practice results, gate and parcel interactions, and skipped deliveries. Associated information includes game version, mode, route, attempt, distance, elapsed time, score, cargo, and flip count. Reports may include stack traces, application state, logs, device and operating-system information, and SDK-generated installation identifiers. Analytics can derive approximate location from a masked network address; the game does not request precise device location. Firebase and its dependencies may also process technical information such as network addresses when providing services.

For eligible adults signed in to Google Play Games, the game sends their Play Games player ID as the Analytics user ID only when analytics is allowed, and as the Crashlytics user ID only when crash reporting is allowed. This links permitted gameplay activity and errors to the same player. Each choice is independent; signing in alone does not enable either use. The game clears the corresponding current identifier when permission is withdrawn, age eligibility is suspended or lost, sign-in is being refreshed, authentication fails, an account change is detected, the player disconnects, or the game session ends. Events recorded before sign-in are not retroactively assigned a player ID, and queued events keep their original account association. Clearing an identifier does not delete uploaded records or rewrite reports already recorded by the SDK.

The game does not send Play Games profile names, account email addresses, tokens, feedback text, screenshots, or contact email to Firebase. It disables advertising ID collection and advertising personalization signals and removes advertising ID and Android advertising-service permissions from its Android build. Diagnostics are not enabled in the Windows version.

You can turn diagnostics off in PRIVACY at any time. Doing so stops the game's diagnostic event recording, disables Analytics collection and automatic Crashlytics upload, clears queued game events, requests deletion of pending SDK crash reports, cancels background diagnostic upload jobs, and resets local Analytics data. SDKs may retain local session information and already started requests may finish. It does not delete information already uploaded. An already initialized SDK may still do local processing during that process. Starting another age query pauses the affected collection and submissions without itself revoking saved choices or closing the game. If a newer platform result removes eligibility after SDK initialization, the game revokes the affected choices and pending submissions and may close after saving restrictions to stop SDK work in that process. Reopen the game to apply the startup gates. Old combined diagnostic consent and legacy age-button selections do not grant new diagnostic permission.

OPTIONAL PLAYER FEEDBACK

The Tally feedback form is available only when the resolved age category is 18+. FEEDBACK explains the information sent before opening https://tally.so/r/yPK0lB in your browser. Opening the form sends the game version, route, mode, run status, device model, operating-system version, and language in the link. This occurs independently of the Firebase diagnostics choice. Tally may also process browser and network information under its own privacy policy. Under-18 players and players who do not provide an age group cannot open the form from the game.

The form asks for a category and description. Control and feature questions, an image attachment, and a reply email are optional. LiteFeel uses submitted feedback to investigate issues and improve the game, and may reply using a supplied email. No Tally account is required. Avoid including names, locations, school information, or other unnecessary personal details in text or screenshots.

CHILDREN

Flipward's intended audience includes children aged six and older. Restricted and unknown-age users can play the full local game. Firebase diagnostics and Tally feedback are unavailable to minors and users with unknown age; Play Games has the separate restrictions described above. A manually entered birthday or self-declared platform age is not verified parental consent or identity verification. Parents and guardians can contact flipward@litefeel.com separately without unnecessary personal details about a child.

GOOGLE PLAY UPDATE CHECK

The Android game checks Google Play once after startup to learn whether a newer version is available to the current store account. This check is independent of diagnostics and is also used when age is unknown or under 18. It uses Google's Play In-App Update library and the Play Store service, which may process app, version, account and device information under Google's terms. The game does not send gameplay, feedback or its local age group in this check. An update notice can appear before play. If a slow response arrives during a game, the notice waits until that run finishes, fails or is left for the home screen; it does not interrupt active play, practice or a paused run. Once a newer version is confirmed and the notice is shown, the game requires an update before you can continue playing. Returning from the store without updating leaves the notice in place. A failed or unavailable check does not prevent offline play. Choosing Open Google Play opens the store, or its web page if the store is unavailable.

SERVICE PROVIDERS AND SECURITY

Google Play supplies age signals and game services, Google Firebase processes diagnostics, and Tally hosts the feedback form. Their services and subprocessors handle information under their respective terms and privacy policies. LiteFeel has configured permitted Analytics events to be exported to Google BigQuery in Singapore and archived on LiteFeel's access-restricted server, including private database copies and CSV/database backups, for gameplay analysis and troubleshooting. Exported records may contain event parameters, device and installation identifiers and, when supplied under the permissions above, the Play Games player ID. These copies are not public and do not create new collection from players who declined analytics. LiteFeel does not sell feedback or diagnostic information or use it to personalize advertising. The game uses HTTPS destinations for diagnostics and feedback. Providers may process information outside your country.

Provider information: https://policies.google.com/privacy, https://firebase.google.com/support/privacy and https://tally.so/help/privacy-policy.

RETENTION AND PRIVACY REQUESTS

Local game records remain until removed through app storage settings or by the device. Uploaded diagnostics are subject to Firebase product retention and deletion controls; turning the option off does not erase server records. The current BigQuery sandbox expires its daily tables after 60 days, but LiteFeel's exported database, private viewing copies and backups are retained separately and currently have no automatic expiry. Expiry or deletion in Google services does not automatically remove those copies. Feedback and support messages are retained for investigation and replies, subject to the provider's operation and applicable requirements.

DATA DELETION REQUESTS

To request deletion of identifiable diagnostic, exported analytics, feedback or support records held by LiteFeel, email flipward@litefeel.com with the subject "Flipward data deletion". Describe the records and provide only information needed to locate them, such as the approximate date, feedback email, or Play Games player ID if available. You do not need to reinstall the game. We will explain any additional information needed to identify your records and any applicable retention limits. A request concerning exported analytics also covers identifiable copies in LiteFeel's private database, viewing copies and backups; disabling diagnostics alone does not initiate this request. Google's own account and Play Games data can be managed using the Google controls described above.

For a privacy question or a request concerning diagnostic, feedback, or support records, contact flipward@litefeel.com. Include only enough information to identify the record. Do not send identity documents or a child's personal details. Permitted diagnostic records may be associated with a Play Games player ID; we do not receive your Google account email through this feature, so an email address alone may not identify those records. Older or signed-out records may have no player ID.

DEVICE ACCESS AND PLATFORM SERVICES

The game uses touch input, graphics, and audio and includes internet access for optional services. It does not request precise location, contacts, camera, microphone, or advertising ID permissions. If you attach an image in the browser's feedback form, the browser or device handles file selection under its own permissions. Google Play, your browser, and your operating-system provider independently process information under their policies.

CHANGES AND CONTACT

LiteFeel will update this policy when data practices change. Developer: LiteFeel. App: Flipward. Support and privacy email: flipward@litefeel.com.