Fish Flow Privacy Policy

This policy applies to the current Fish Flow game service distributed as a WeChat Mini Game and to the official website at fishflow.airstrike.cn. This page is also used as the privacy-policy URL for TapTap game ID 902641.

The public developer display name on TapTap is 萌小鱼, and XGame (independent developer + AI collaboration team) is the brand and production credit. Neither display name is asserted here as the legal developer or operator name. The legal entity or individual name for the final store and policy disclosures remains pending confirmation by the account owner. Store placeholders for Android, iOS, or web do not mean those editions are published.

This English page is a complete translation provided for convenience. The Simplified Chinese version remains the reference text if interpretations differ.

Local game data includes the current level, move history, star records, best time, tool use, AI-assistance state, Gold Pearl balance, tool inventory, sign-in or event state, collection discoveries and rewards, preferred home background, language, music, sound, and vibration settings. It is used only to restore gameplay and preferences. Current game code does not upload this data to an XGame user database.

When you tap Copy Prompt, the game locally creates text describing the level, branches, fish order, mechanisms, rules, and stable fingerprint, then asks to write that text to the clipboard. The prompt is not designed to contain a name, account, or contact details. The game never reads the clipboard automatically. You paste an external AI answer into the game yourself, and strict JSON is validated and simulated locally before execution.

If you send a prompt to an AI product you selected, that provider handles it under its own privacy terms. XGame does not currently embed a general-purpose model SDK or automatically transmit your board to an external AI service.

The WeChat edition uses window size, safe-area, and menu-button position for portrait layout, and may request short vibration feedback if enabled. These values are used locally and not to create a persistent device profile.

The static website requires no sign-in or form submission and sets no marketing or profiling cookie. Its Nginx server records standard access logs such as IP address, time, path, status, referrer, and browser User-Agent for HTTPS delivery, security, and fault diagnosis. Logs currently rotate daily with 14 history files.

If you email support, we process the sender address, message content, attachments you choose to provide, and delivery metadata to investigate and reply, protect the service, and retain necessary support records. Do not send passwords, verification codes, identity documents, or unrelated sensitive information.

Clipboard write is requested only when you tap Copy Prompt. Network access is used to open the website and guides or download required remote game resources. Short vibration provides optional feedback. Window and safe-area information supports screen, WeChat capsule, and Game Club layout.

Current public-version business code does not request or use the camera, microphone, location, contacts, photo-library reading, or clipboard-reading capability. It does not call WeChat login, profile, or phone-number APIs. The unreleased Google Play Android build declares the Android advertising ID for Google Mobile Ads; UMP obtains any required regional consent before ads are initialized. If a future feature needs another capability, we will explain its purpose, scope, and the effect of refusing before requesting authorization.

The WeChat Mini Game runtime (Tencent) provides execution, local storage, clipboard-write authorization, vibration, window adaptation, and the Game Club entry. The game does not call WeChat login, profile, or phone-number APIs.

WeChat advertising components (Tencent) may show rewarded video when a player voluntarily requests an eligible tool and may show an interstitial at product-defined completion points in the published WeChat edition. Ad delivery and related processing are handled by WeChat’s advertising platform.

Alibaba Cloud Object Storage (Alibaba Cloud Computing Co., Ltd.) hosts remote gameplay resources for the WeChat edition. The game downloads files by URL without embedding the OSS client SDK and does not upload local progress. Network delivery may still process IP address, request time, resource URL, and necessary request headers.

The channel-isolated TapTap Android preparation source set includes TapSDK and TapADN and is kept separate from Google Mobile Ads and UMP. That source-level preparation does not by itself establish the final TapTap release’s data flows. The final dependencies, merged manifest, console configuration, device traffic, login or analytics capabilities, and disclosures must be verified before release rather than inferred from the SDK names.

Tencent Privacy Protection · Tencent Advertising Privacy · Alibaba Cloud Privacy Policy

A Fish Flow record exists in Google Play Console, but it has not obtained production access because the required closed-test gate remains incomplete, and the Android edition is not publicly released. The isolated Google Android preparation source set now integrates legacy Google Mobile Ads 25.4.0 and UMP 4.0.0 for direct rewarded and interstitial ads, with no MAX or other mediation. All Google Play and TapTap Android builds, including Debug, retain the same package com.xgame.fishflow.sort; channel isolation is implemented through flavours, dependencies, and resources rather than package-name changes.

The formal Fish Flow Android app and its rewarded and interstitial units have been verified read-only in AdMob without placing their identifiers on this page. The AdMob app is not yet linked to a public store listing and remains awaiting review. Google Debug contains the real AdMob app ID only to address the correct consent configuration and uses Google’s public test ad units; production ad-unit values are limited to ignored local Release configuration.

The Google Play target audience is 18+. The prepared release manifest sets allowBackup to false and declares Android AD_ID for Google Mobile Ads. The Google build requests UMP consent information on launch and initializes ads only when UMP permits ad requests. These safeguards do not replace final manifest, dependency, Data safety, and device-network review.

A published Fish Flow UMP message covers the Android and iOS apps. The startup gate can request current consent information and show the applicable form or privacy-options entry when required by the user's region and stored choices. The Android edition remains unpublished; final Release behaviour and Google Play Data safety answers will still be verified against the production artifact.

• Android advertising choice: use the consent or privacy-options entry when the final UMP configuration requires it.
• Identifier baseline: the Google release declares Android AD_ID for Google Mobile Ads; the final merged manifest and device traffic will be checked against the Google Play Data safety disclosure.
• Optional rewarded ads: do not open a rewarded-ad entry if you do not want to request that ad; core play that does not require the reward remains available.
• The final Google Play Data safety disclosure must match the verified production build and its actual network behaviour.

Google Mobile Ads Android data disclosure · Google UMP for Android · Google Privacy Policy

As of this policy date, no Fish Flow iOS edition is publicly available on the App Store. Development code contains a direct rewarded-ad bridge for Google Mobile Ads and a User Messaging Platform (UMP) consent path. The final Xcode project, SDK versions, production app and ad-unit IDs, UMP messages, ATT request flow, device behaviour, privacy manifests and report, and App Store privacy label have not all been finalised and verified. The following is therefore conditional and does not describe current website or WeChat processing.

If the released iOS build retains Google Mobile Ads, Google’s current iOS disclosure says the SDK may process IP address for approximate location, crash logs and performance diagnostics, device identifiers such as IDFA where permitted or app/developer-bounded identifiers, advertising data such as ads viewed, and product or ad interactions such as app launches, taps, and video views. Depending on the final consent and account configuration, those signals may support ad delivery, measurement, diagnostics, fraud prevention, analytics, or personalisation. The prepared bridge does not explicitly attach local level progress, clipboard contents, or AI prompts to an ad request.

The planned UMP path requests updated consent information, presents any required privacy form, exposes a privacy-options entry when required, and checks whether ads may be requested before starting Google Mobile Ads. ATT is a separate iOS system permission governing tracking and access to IDFA. If the final build requests ATT, it will first explain the purpose and use Apple’s system prompt. Google states that when ATT is denied, Google Mobile Ads does not send IDFA in its ad request, although an ad may still be requested in a mode allowed by the user’s other choices and the applicable configuration.

No third-party mediation adapter or additional advertising network is currently confirmed for the iOS release. If mediation, analytics, optional Google features, or another advertising SDK is added, this policy will be updated before release with the actual SDK name and version, provider, data categories and purposes, sharing, retention and deletion controls, and the results of the final dependency, privacy-report, and network checks.

• ATT choice: manage tracking permission in iOS Settings. Refusing tracking must not be treated as consent to use IDFA.
• Advertising privacy choice: where UMP requires a privacy-options entry, use it to revisit the choices made in the consent form.
• Optional rewarded ads: do not open a rewarded-ad entry if you do not want to request that ad; core play that does not require the reward remains available.
• Provider-held advertising or consent data follows the relevant provider’s controls and retention rules; the final App Store disclosure must match the verified production build.

Google Mobile Ads iOS data disclosure · Google UMP for iOS · Apple user privacy and data use · Google Privacy Policy

Local progress and settings remain until you clear Mini Game or site data, uninstall the relevant client, or the platform clears storage. The AI recovery checkpoint exists only in runtime memory and expires through normal game flow. Clipboard contents are managed by the operating system or platform. Website logs are currently retained for about 14 days on the mainland China website server. Support emails and related records are retained only as long as reasonably needed to handle the request, protect the service, meet legal obligations, or resolve disputes, then deleted or anonymised where applicable.

We do not sell personal information. Information is processed by the providers above only where necessary for a capability you use, ad delivery, resource download, website access, or a lawful request from an authority. Current game-side code does not share local progress with advertising platforms for personalised profiling.

The website uses HTTPS, access controls, log rotation, a minimal static-service scope, and atomic releases. No internet service can guarantee absolute security; we will take legally required remedial, reporting, or notification steps if an incident may affect your rights.

Subject to applicable law, you may request access, a copy, correction, supplementation, deletion, withdrawal of consent, or an explanation of processing. To protect information, we may reasonably verify that a request relates to the relevant device or platform, but we will not ask you to post identity documents publicly.

• Delete local data through the platform’s clear-data controls or by uninstalling the relevant client.
• Avoid clipboard writing by not tapping Copy Prompt, or manage authorization in WeChat or system settings.
• Turn vibration off in game settings.
• Decline optional rewarded advertising by not opening an eligible reward entry; core play that does not require that reward remains available.
• If the iOS edition is later released, manage ATT in iOS Settings and use the in-app advertising privacy options when the consent system requires that entry.
• If the Android edition is released with the prepared advertising path, use the in-app privacy-options entry when an effective UMP message requires it; final device and store disclosures will describe any additional system controls that actually apply.
• Do not use AI assistance if you prefer. Review the chosen AI provider’s privacy terms and do not add sensitive personal information to a prompt.

Minors should use the service and read this policy with a parent or guardian. Where processing information about a child under 14 requires consent under applicable Chinese law, the guardian should make that decision. The current game creates no XGame user account and does not actively collect a name, national ID number, phone number, or face data.

Guardians should help minors manage play time and avoid posting names, contact details, school, home address, identity documents, or similar information in Game Club, TapTap communities, or prompts submitted to an external AI. WeChat handles any real-name, minor-protection, or anti-addiction functions under its own rules; current game code does not receive that real-name data.

Google Play target audience is 18+ and the application is not directed at minors. Before any Android or iOS release, the final target-audience selection, SDK versions, consent flow, production behaviour, and advertising settings must still be checked. This policy does not claim that an unverified mobile advertising configuration is already active.

When distribution channels, features, SDKs, third-party services, or processing practices change, we will update this page and show the new version, publication date, and effective date. Material changes will receive a more prominent notice through the website, game, or distribution platform where available.

For questions about this policy, information processing, or a rights request, use an enabled official channel below. 萌小鱼 is a public TapTap developer display name and XGame is a brand and production credit; neither replaces the legal developer or operator name that remains pending confirmation by the account owner:

• WeChat Mini Game: open Game Club from the Fish Flow home screen and submit the issue through the official community entry.
• TapTap: use the developer contact or feedback entry on the page for game ID 902641.
• Website: use the public support email or the Support page linked below.

Label the request “Privacy Request” and include the platform, device type, and a short description. Do not post an identity number, phone number, complete clipboard text, or other sensitive information publicly.

Public support email： bugyellow2021@gmail.com · Open the Support page