DogDoku Privacy Policy
This Privacy Policy applies to DogDoku on iOS and Android. Some features and third-party services are available only on a particular platform or when you choose to use them. This Policy describes the combined practices of both versions so that one policy URL can be used for both App Store and Google Play listings.
Controller/operator: The DogDoku publisher identified on the applicable App Store or Google Play listing.
Privacy contact: wangziwei9401@gmail.com
1. Data We Process
Game data and settings
We store game progress, unfinished game state, virtual resources, unlocked content, gameplay statistics, and settings such as language, sound, haptics, and display preferences. This data is primarily stored locally on your device.
Analytics and diagnostics
DogDoku uses Firebase Analytics and Firebase Crashlytics. These services may process an app-installation identifier, device and system information, app version, screen views, feature interactions, gameplay events, crash logs, and diagnostic information. We use this information to understand feature usage, improve the app, maintain security, and diagnose stability problems.
Advertising
DogDoku uses Google AdMob for ads on iOS and may use app-open, banner, interstitial, and rewarded ads on Android. On iOS, Google User Messaging Platform (UMP) manages advertising privacy choices where required. In the European Economic Area, the United Kingdom, Switzerland, and other applicable regions, UMP may show a Google-provided privacy message describing advertising partners, data purposes, device storage, and choices related to personalized advertising. The user's choice may be stored locally and used by the Google Mobile Ads SDK to determine how later ad requests are handled.
Users may consent, decline, or manage applicable advertising purposes. Declining does not restrict normal gameplay, levels, Battle, purchases, or purchased features. Limited ads may be available after a decline, or no ad may be available because of privacy status, connectivity, or inventory. Where required by UMP, iOS users can change or withdraw their choice through Settings → Ad Privacy Choices. Changing a choice causes ads preloaded under the earlier choice to be discarded. Withdrawal does not affect processing based on consent before withdrawal.
On supported iOS versions, DogDoku requests App Tracking Transparency (ATT) permission after the advertising privacy choice is resolved. If you allow it, AdMob may access the iOS advertising identifier (IDFA) and use it for advertising across apps or websites, measurement, and invalid-traffic prevention. If you decline or tracking is restricted by the system, normal gameplay remains available and ads may be limited or non-personalized. AdMob may also process coarse region inferred from IP address, app- or developer-scoped device identifiers, device and network information, app interactions, ad impressions or clicks, and diagnostic data. Rewarded ads grant an in-game reward only after the advertising provider confirms eligibility.
Sign-in, cloud saves, and leaderboards
On Android, if you choose Google Sign-In for cloud saves, the app obtains a Google ID token and passes it to Firebase Authentication to authenticate your account. Depending on the account information returned by Google, Firebase Authentication may process your Google account identifier, email address, display name, profile photo, sign-in provider information, and the Firebase user ID assigned to your account. The app uses your signed-in display name in its cloud-save interface.
Firebase Firestore stores a game-save snapshot linked to your Firebase user ID. The snapshot includes game progress, virtual resources, unlock state, and settings, together with a save-format version and update time. After you choose to sign in, the app reads and merges an existing cloud save and uploads the resulting snapshot; later changes are synchronized while the app is running with the signed-in account. This allows the app to restore progress and keep supported devices using the same account in sync. Choosing not to use this optional sign-in feature leaves its save data on your device.
If you use Google Play Games leaderboards, Google Play Games may process your player profile, authentication status, and submitted completed-level score. This is separate from the Google sign-in used for Firestore cloud saves.
On iOS, if iCloud is enabled and you allow DogDoku to use CloudKit, a game-progress snapshot may be stored in your private iCloud database so it can be restored across devices using the same Apple account. If you use Game Center or multiplayer features, Apple Game Center and the services supporting those features may process authentication status, player name, avatar, leaderboard scores, match state, and related records necessary to provide those features.
Nicknames, avatars, and Battle on iOS and Android
On iOS and Android, you may enter a new nickname of up to ten visible characters through the home-screen avatar entry or profile settings. New text is sent to our Firebase Cloud Functions for format and profanity checks. An approved nickname is saved on your device for later battles; these checks do not create a permanent server-side nickname profile or rename history. The app can use an anonymous Firebase identity for validation without a separate Game Center, Google Play Games, or Google cloud-save sign-in. Existing preset names remain compatible. A nickname need not be unique or your real name, does not change your Game Center or Google Play Games name, and is not an account-recovery credential. Please do not enter contact details or sensitive information. Word checks run within our Firebase service without an additional external content-moderation service; automated filtering may make mistakes and is not individual manual review.
Friend Battle on iOS and Android uses private invitation rooms accessed by room code. World Battle is an iOS feature that lets authenticated players choose from a public waiting-room list; it does not provide automatic random matching or chat. Players in the same match can see each other's nickname, avatar, and necessary live game state. The iOS public waiting-room list shows the host's nickname, avatar, difficulty, aggregate battle statistics, and occupancy. Firebase temporarily stores the display name in the current room and, where applicable, the public waiting-room listing. These copies follow room and listing cleanup. Firebase also processes player identifiers, room and match state, progress, lives, hints, results, and aggregate battle statistics to operate the available features.
On both platforms, you can select bundled avatars and avatar frames, represented by style identifiers without uploading a personal photo. On iOS, if no bundled animal avatar is selected, the app may use your Game Center avatar or the default avatar. A retrieved Game Center image is compressed and uploaded to Firebase Storage; its download URL is used to display it to match participants and authenticated iOS lobby viewers. Images may be cached on devices. The profile feature does not let you upload another image.
You can edit your locally saved nickname or reset it to the default; resetting works offline. Uninstalling the app, clearing app data, or changing devices may prevent recovery of the locally saved name. Renaming does not automatically change a match already in progress or other players’ local caches. Completed World Battle records retain results and player identifiers with generic player labels rather than personal nickname snapshots. New text requires online validation; failed validation leaves the previous name unchanged. These nickname-storage rules do not delete or change the retention of Firebase authentication records, optional cloud saves, leaderboard records, or other data described in this Policy. To notify us of an inappropriate name or request correction or deletion of identifiable Battle data, email the privacy contact with relevant room, match-time, or player-identifier details where available. Never send passwords or authentication tokens.
Purchases
Purchases, restores, refunds, billing, and transaction verification are handled by Apple App Store / StoreKit on iOS and Google Play Billing on Android. We do not receive complete payment-card information. We may store entitlement status locally and record product identifiers and purchase-flow events for support, analytics, and entitlement restoration.
Images, sharing, and feedback
The iOS version may let you choose a puzzle image or use the camera for its solver. The selected image is processed primarily on the device and is not intentionally uploaded by us. On either platform, when you choose to share, the app may create a share image locally and pass it to the app you select through the system share sheet. If you contact us by email, we receive the email address, message content, and any information you include.
We do not access contacts, microphone, precise location, or your photo library or camera except when you actively use a feature that requires the relevant iOS permission.
2. How We Use Data
We use the data described above to provide and improve gameplay; save, restore, and synchronize progress; provide purchases, leaderboards, and multiplayer features; deliver and measure advertising; diagnose errors; prevent abuse and invalid traffic; and respond to support requests.
Depending on the activity and applicable law, processing may be based on performance of a contract or requested service, consent, legitimate interests in security and service improvement balanced against user rights, or compliance with legal obligations.
Use of Google account information
Google account information is used to authenticate your account, identify its cloud save, display your signed-in identity, and provide the optional features described above. The Android app also sends the Firebase account creation time to Firebase Analytics as a user property for app-usage analysis. The installation identifiers, gameplay events, advertising data, and diagnostics processed by other SDKs are described separately in this Policy.
The cloud-save sign-in feature does not request access to the contents of your Gmail, Google Drive, Google Photos, contacts, or calendar. DogDoku does not use Google account information or cloud saves to train AI models or generate images. Our use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
3. Sharing and Third-Party Services
Google sign-in and cloud-save data: Google and Firebase process authentication and cloud-save information to provide those services. We do not sell your Google account information or provide your Google account email, display name, profile photo, ID token, or cloud-save snapshot to advertising partners for personalized advertising. Our app's use of advertising SDKs and analytics is described separately above. A leaderboard profile or submitted score may be visible to other players according to Google Play Games settings; the Firestore cloud-save snapshot is not a public leaderboard.
We do not sell personal information. We share data only as needed to operate the features described in this Policy, including with Google AdMob, UMP, advertising technology providers identified in the applicable UMP message, Firebase, Google Play, Google Play Games, Apple App Store, StoreKit, iCloud, CloudKit, Game Center, and system sharing services. In multiplayer features available on the relevant platform, the other participant may see the display name, avatar, and match state needed to play. Third-party services process data under their own terms and privacy policies and are expected to provide protections consistent with applicable law and this Policy.
Useful links:
4. Retention and Deletion
Google sign-in and cloud saves: Firebase account records and the linked Firestore save are retained to provide authentication and restore your progress; the app does not apply a fixed automatic expiry period to these records. Uninstalling DogDoku, clearing local app data, or revoking Google sign-in access does not automatically delete a Firebase account or an existing Firestore save. You may review or remove the app's Google account connection through Google Account connections. Removing the connection may require you to authorize again if you later choose Google sign-in.
To request deletion of your identifiable Firebase account and cloud-save data, email wangziwei9401@gmail.com with the subject “DogDoku cloud data deletion request” and identify the Google account used for the app. We may ask for information sufficient to verify your ownership and locate the records. Do not send a password, ID token, or access token. Google Play Games leaderboard records, purchase records, and other data held by Google or Apple are managed separately under the relevant service's settings and policies.
Local game data remains on your device until you delete the app, clear app data, clear progress where that option is available, or the operating system removes it. Cloud-save, leaderboard, purchase, advertising, analytics, crash, and multiplayer data are retained by the applicable service provider for the period required to provide its service, ensure security, meet legal obligations, or comply with its policies.
Deleting the app stops that installation from sending new data but does not automatically delete data already held by a third-party service. You can manage Google, Apple, Game Center, iCloud, and Google Play Games settings through your account or device settings. To request access, correction, deletion, restriction, portability, objection, or consent withdrawal concerning information provided by email, a Firebase anonymous identity, Battle rooms, World Battle records, or other reasonably identifiable Firebase data, contact us at the address above. We may need information sufficient to verify the requester and locate data associated with an anonymous identifier.
The iOS app can currently clear local game progress but does not yet provide an in-app button that automatically deletes a Firebase anonymous account and all related cloud Battle data. A cloud-deletion request can currently be initiated through the privacy contact above.
5. Your Choices
You may choose not to use cloud saves, leaderboards, multiplayer, rewarded ads, sharing, the iOS solver, or optional sign-in. On iOS, where UMP requires a privacy-options entry point, use Settings → Ad Privacy Choices to view, change, or withdraw advertising choices. Declining or withdrawing advertising consent does not affect normal gameplay, but personalized advertising, some measurement, or rewarded ads may become unavailable. You may also manage privacy and account settings through your device and the relevant Google or Apple services. Network-dependent features may be unavailable while offline.
6. Regional Rights and International Processing
Subject to applicable law, users may have rights of access, correction, deletion, restriction, portability, objection, consent withdrawal, and complaint to the competent data-protection authority. Withdrawal does not affect processing based on consent before withdrawal.
Apple, Google AdMob, UMP, Firebase, advertising partners, and their service providers may process information outside the user's country or region. Where regulated, transfers will rely as applicable on an adequacy decision, standard contractual clauses, contractual arrangements, or another valid transfer mechanism.
7. Children
DogDoku is not directed to children under 13 for the purpose of collecting personal information. Minors should use the app with parent or guardian consent and guidance. Where local law sets a digital-consent age higher than 13, a user below that local threshold should use the app only with consent given or authorized by a parent or guardian. If a guardian believes a minor provided personal information directly to us, please contact us.
8. Changes to This Policy
We may update this Policy when our features, data practices, third-party services, or legal obligations change. We will update the effective date when we do so. If a material change legally requires renewed consent, we will request it before the relevant processing begins.
iOS 与 Android 昵称、头像及对战补充说明
iOS 与 Android 用户可通过首页头像入口或个人资料设置填写最多10个可见字符的新昵称。新昵称会发送至我们的 Firebase 云函数进行格式和敏感词检查，通过后保存在本机，供之后的对战复用；检查过程不建立长期云端昵称档案或改名历史。应用可通过 Firebase 匿名身份验证昵称，无需另外登录 Game Center、Google Play Games 或用于云存档的 Google 账号。旧预设昵称继续兼容。昵称不要求真实姓名、不保证唯一，也不改变 Game Center 或 Google Play Games 名称或用于找回账号。请勿填写联系方式或敏感信息。自动检查在 Firebase 内执行，不会发送至额外的第三方内容审核服务，可能存在误判或遗漏，并不代表逐条人工审核。
iOS 与 Android 的好友对战通过房间码邀请加入。世界对战是 iOS 功能，提供由玩家自行选择的公开等待房间列表，不提供自动随机匹配或聊天。对手可见你的昵称、头像和必要局内状态；在 iOS 世界对战中，已认证玩家可在公开列表看到房主昵称、头像、难度、汇总战绩及人数。Firebase 会在当前房间及适用的公开等待列表中临时保存展示昵称，并随房间及列表清理；也会处理运行对应对战功能所需的玩家标识、房间及对局状态、进度、生命、提示、结果及汇总战绩。
两个平台的内置头像及头像框均以样式标识展示，无需上传个人照片。在 iOS 上，未选内置动物头像时，可使用 Game Center 头像或默认头像；Game Center 头像经压缩后上传至 Firebase Storage，以下载链接向对局参与者及 iOS 公开列表的已认证玩家展示，并可能在设备上缓存。个人资料功能不允许上传其他图片。
你可以修改本机保存的昵称或恢复默认，恢复默认无需联网。卸载应用、清除应用数据或更换设备后，本机昵称可能无法恢复。改名不会自动改写已开始的对局或他人的本地缓存。世界对战的云端历史记录保留结果及玩家标识，使用通用玩家标签，不保存个人昵称快照。新填写的昵称需要联网验证，失败时原昵称不变。上述昵称保存方式不等于删除 Firebase 身份认证记录、可选云存档、排行榜记录或本政策所述其他数据，这些数据仍按各自规则保存。遇到不当昵称，或需更正、删除可识别的对战数据，可联系上述邮箱并尽可能提供房间码、对局时间或玩家标识；不要发送密码或登录令牌。