Waddle Wars: Penguin Panic

Mobile privacy policy

Local adventures, with optional accounts in supported iOS builds. Clear information about what leaves your device.

Which version this covers

This document covers Waddle Wars: Penguin Panic for iOS and Android. iOS builds with Sign In, starting with build 41, offer optional accounts, cloud progress, and score submission. Builds with the Leaderboard setting also support automatic guest score posting on iOS and Android. Older builds without this setting keep their existing sign-in and score-posting behavior. No account is required to play. These mobile editions have no in-app purchases; fish and cosmetic unlocks are earned through play.

The browser game is a separate version, with its own account configuration. This mobile policy does not cover browser-game payment services. Publishing this policy does not mean a particular build is already available in a store or TestFlight.

Progress stored on your device

The game stores progress, earned cosmetics, best results, runner missions, settings, and time-trial ghosts in local app storage. Core gameplay and local progress work without an internet connection.

Without signing in on a supported iOS build, the game does not upload your progress to a game account. The Android launch configuration disables automatic Android app-data backup. On iOS, device backup and restore behavior depends on your operating-system settings and policies; a device backup is separate from game-account cloud sync.

When you choose a sharing action, the mobile game hands the selected result or challenge text and game link to your device's share options where available, or copies it to the clipboard. The game does not automatically publish that text; you choose whether and where to send or paste it.

When you use the Leaderboard

Opening or using the Leaderboard requests public results over HTTPS from our Cloudflare-hosted service. Selecting a board, retrying a failed request, or rotating the screen can request results again. Public board requests send the selected mode, course, and result limit. In builds with the Leaderboard setting, participation starts enabled: while online, Waddle Run best scores post automatically, including scores from guests. Daily Trail results do not post to this board. The signed-in iOS features are described below.

Cloudflare handles requests and may process IP addresses, traffic-routing data, system-configuration information, and network/security records to deliver and protect the service. Its privacy policy describes this processing. Provider retention depends on purposes and legal obligations, not a fixed Waddle Wars deletion deadline.

Workers Logs and Workers Traces were disabled for our game and leaderboard production services in the October 2, 2026 hosting review. The browser-game host later enabled Workers Logs for operational monitoring; the native game's leaderboard service is separate. This dated observation does not mean Cloudflare processes no data. Provider logs, security records, and retention follow its practices.

Our Workers logging settings do not give us control over every provider-held record. We do not promise a fixed retention period or immediate deletion for those records.

You can avoid these game-service requests by playing offline, staying signed out, and not opening the Leaderboard or sending Feedback.

Automatic guest leaderboards

Builds with the Leaderboard setting give guests a randomly generated public name and a persistent guest identifier when posting a Waddle Run best. The generated name, score, game mode and rank can appear publicly without account sign-in. The private posting credential stays in app storage and is sent only to our leaderboard service over HTTPS; it is not a public name or part of your cloud save. We do not publish your device identifier, credential, email or social-login name.

You can turn Leaderboard off in Settings before playing to stop automatic posting. Turning it off stops future posts; it does not remove scores already received. Offline progress remains on the device, and a saved best may be posted when participation is enabled and a later connection succeeds. Guest identity is separate for production and testing boards. It is separate from the usage analytics identifier.

Guest records and best scores are retained while the leaderboard entry exists. Contact support with your generated guest name and whether you used a test or production build to request removal; do not send your private posting credential. Clearing app storage loses that credential and does not automatically remove a server entry. Our Cloudflare-hosted service processes network information for security and limits repeated registrations and score requests; raw network addresses are not added to the leaderboard database.

Usage analytics by app version

Version 1.2.1 introduces required first-party usage analytics with no analytics selector. The game measures opening/loading, sessions, tutorials, run starts and ends, replays, run duration and end reason, distance, score, fish, shop interactions where available, and fixed error categories, together with platform, build and random event/session identifiers.

The updated game stores a random installation identifier and includes it with events to measure new, active and returning installations. We do not join it to your account or link it across devices. This is required product measurement under the updated policy, not a record that you opted in. Upgrading replaces earlier Off and Basic settings; those preferences are not treated as consent. Deleting app data removes the local identifier; opening the updated game creates another. Earlier app versions retain their optional analytics settings and existing behavior. Contact support@waddlewars.io for privacy questions or applicable access, deletion or objection requests.

These events are processed by Cloudflare. They contain no account identifier, name, email, authentication token, save file, receipt body, raw URL or free-text error. Our endpoint uses IP addresses for abuse limits without writing them into the analytics database. Event removal is scheduled after 35 days; installation summaries are scheduled for removal after 90 days without activity. When purchases are enabled, verified purchase/refund totals contain store, product, currency, amount and a transaction digest for deduplication, without a player identifier, and are scheduled for removal after 400 days. Provider hosting, security and backup records follow provider practices.

Optional iOS sign-in and saved progress

Sign In opens a secure system authentication window using our production Clerk service at clerk.waddlewars.io. Clerk and the sign-in provider you choose process the account details needed for authentication, such as an account identifier, email address, and, when supplied by that provider, a name and profile picture. Their browser cookies and network/security information follow their own practices. See Clerk's privacy information and your chosen provider's privacy policy.

The game uses an account identifier and short-lived authentication credentials to connect your account to our Cloudflare-hosted game service. Credentials are held in app memory, not included in cloud progress or feedback. This does not clear cookies held by the system authentication window or records held by Clerk.

After you sign in, the game synchronizes earned fish, unlocked and equipped cosmetics, achievements, mission and run progress, best results, and related gameplay statistics. Existing progress on the device may be included. The game keeps an online copy associated with your account so that supported signed-in devices can recover progress. Settings and time-trial ghost files remain local. Signing out stops authenticated synchronization; it does not delete the existing online copy or local progress.

Completed signed-in runs can submit scores and course or mode information to the leaderboard. A separate Post Local Best action can submit a result already on the device. Public results show your chosen leaderboard name, or Penguin by default. Your social-login name and email are not automatically published as your leaderboard name. You can change your leaderboard name from Account.

We use this account and gameplay information for sign-in, saves, leaderboards, account support, and protection against unauthorized or repeated requests. Account and cloud records are kept while the account is active, subject to the deletion process below. The game service and authentication providers also process network and security information; we do not promise that all provider records have the same retention period.

Deleting an iOS account

In a supported iOS build, open Account → Privacy & Data → Delete Account. Review and confirm the request. After server confirmation, your game profile, leaderboard scores, cloud save, and native game-session records are removed or invalidated, and deletion of the Clerk identity is requested. Check status distinguishes game-data removal from identity deletion; a network error does not mean the request was cancelled.

We retain a minimal account-retirement marker, a hashed deletion recovery receipt, and deletion-status records to prevent an old session or delayed save from recreating deleted data and to let you check the request. Identity-provider cleanup can remain pending. Provider security records and backups may persist under their practices. The current status does not certify that every retained record has been erased, and we do not promise a fixed deletion deadline for those records. Contact support for questions about retained information.

Account deletion keeps earned offline progress on this device. To remove that local progress too, delete the app or clear its app storage; device backups may keep a separate copy. A separate browser-game account is not automatically deleted. See data deletion instructions.

When you visit these information pages

These support and privacy pages are also hosted by Cloudflare. Our game website uses Cloudflare Web Analytics. If its Cloudflare Web Analytics beacon is loaded when you visit these information pages, it sends page-performance measurements and website-visit information to Cloudflare. Available reports include page paths, referring sites, browser, operating system, device type, and country. See Cloudflare's collection documentation and reported dimensions.

This website measurement and browser-game analytics are separate from native game play: they run in a browser, not inside the mobile game. Provider retention and privacy practices apply. External links open other websites with their own policies.

If you contact support

If you email us, we receive the information you choose to send, such as your email address, device details, description of a problem, and attached screenshots. We use this information to respond and troubleshoot. Do not send passwords, payment credentials, account tokens, or unrelated personal information.

The optional in-game Feedback form sends your chosen category, message, optional reply email, game version, and platform to support@waddlewars.io only when you press Send Feedback. It does not attach your save, screenshots, account token, or purchase history. Cloudflare processes the request and limits repeated submissions using the client IP address; Amazon Simple Email Service sends the message. You can use the form without providing an email address, although we cannot reply without one.

The owner of Ninja Consulting LLC personally handles Waddle Wars support and privacy requests. Cloudflare Email Routing forwards messages sent to support@waddlewars.io to the publisher's Gmail inbox. Cloudflare and Gmail/Google process email under their respective privacy policies.

We retain routine support correspondence while an issue is open and delete it from the publisher's active mailbox within 90 days after resolution. We retain specific records longer only when required by legal obligations or necessary for fraud or security handling, limited to what those purposes require.

Email-provider backup copies may persist under the provider's practices. We do not promise a fixed deletion deadline for those copies.

Handling and sharing information

Game-service requests use HTTPS. Support information is used to handle your request, not posted to a public leaderboard. Publisher access is limited to the person handling support; Cloudflare, Clerk, your chosen sign-in provider, Amazon Simple Email Service, and Google process information needed for the services described above. Information may also be disclosed when required by law or necessary to address fraud or security incidents.

We do not sell personal information. No internet service or email system is completely secure, so send only information needed for your request. Provider processing can involve countries other than your own, as described in their policies.

Your choices and requests

You can play offline, stay signed out, avoid online leaderboards, and choose what to include in a support message. To ask about access, correction, or deletion of information sent to support or an online service, contact the privacy address shown above. Applicable rights depend on your location and the information involved; we may need sufficient details to locate and verify your request.

For Cloudflare processing, start a privacy request with Ninja Consulting LLC. Cloudflare's published policy directs users of customer applications to that customer. Requests may require identity verification and enough details to locate information. Its published data-processing terms describe assistance to the extent it is able and in line with applicable law. We cannot promise that every provider record can be located or erased.

A parent or guardian can contact us about information a child has sent to support. Do not include a child's personal details in a public message.

Deleting the app or clearing its storage can permanently erase local progress. Device backups may retain a separate copy. Removing mobile app data does not delete an online account or its records. Use the account deletion flow for a supported iOS account; identify a separate browser-game account separately in a support request.

Policy updates

Updates will show their effective date on this page. If a later mobile version changes its account features or adds purchases, analytics, or other data-handling features, we will update this policy and the relevant store disclosures before enabling those features.