Oddwalk: privacy

Oddwalk privacy
Updated 6 November 2026

Oddwalk is a creature fashion game for children aged 6 to 11. Moola operates the game. A grown-up manages accounts, purchases, links, sharing and account deletion behind a parental gate. The child never creates an account. A parental gate does not by itself establish legally required parental consent.

The preview and gameplay use original catalogue artwork. We do not ask children for names, birthdays, photos, voice recordings, location, contacts or messages. We do not include advertising or third-party analytics. We do not sell personal information or use it for targeted advertising. Outfits, the preview's completion, generated courses, maker drafts and undo, kept courses, discovered tricks and game checkpoints are stored on the device so play can resume. Checkpoint coordinates describe the game world, not the device's location. Original music and effects play from bundled files. Anonymous music and sound switches are device preferences, separate from account backup, and may remain after account deletion.

A parent may sign in using Apple on iOS or a phone number through Firebase Authentication. Apple may provide the parent's name and real or relay email to Firebase. Phone numbers are sent to and stored by Google for spam and abuse prevention across Google services, including Firebase. We show that disclosure before phone verification. Apple and Google process account information according to their own terms and privacy notices. The parent must provide accurate adult account information. We do not offer Google Sign-In or email/password login in this child-directed app.

Firebase App Check and platform attestation help protect account services. These services process technical information needed to validate the app and device. Parent services use the Moola Firebase project and the named moola Firestore database in europe-west4. Other authentication, security and provider infrastructure may process data in other locations according to provider terms. Security SDKs are not used to measure the child's play.

A verified purchase is linked to the parent Firebase account. Apple or Google Play handles payment details; Oddwalk does not receive payment-card numbers. Our server retains purchase references, an opaque account mapping and access status to verify rights, handle refunds and recover purchases. A protected device cache permits offline play only until its original server-authorized deadline. Test rights do not become production rights.

The parent can choose to back up the game. A backup contains catalogue outfit choices, look identifiers, bounded course seeds and part IDs, maker drafts and undo, kept courses, discoveries and game checkpoints under the parent's app account. It does not contain a child's name or photo. Backups are private to that app account. Conflicting saves are refused instead of silently overwriting another device. The parent can export the existing game record without paying.

Sharing requires a fresh parental gate and the operating system's share sheet. A poster contains the original creature art and optional catalogue prompt or a bounded code that reproduces a course. A course-code entry accepts only versioned catalogue choices, not arbitrary messages, and is not uploaded as text. It excludes account details, phone numbers, photos, location and contact information. We do not upload contacts, auto-post, measure recipients or reward sharing. The receiving service handles anything the parent elects to share under its own policy.

Parents can initiate deletion in the grown-up corner after confirming identity, or request help through the public Moola support route. Deletion removes the app's saved account records, access mappings and local account cache. Apple authorization is revoked when applicable. Other Moola app memberships are preserved. A queued deletion is shown as requested until the worker confirms completion. Detached store dispute references may remain for up to 90 days after deletion; operational retry records expire after 7 days and completed deletion markers after 30 days, with expiry processing asynchronous. Firestore point-in-time backups follow the project's configured 7-day recovery period and must not restore deleted records into active use. Support correspondence is kept for 12 months after closure.

Device-only game records that have not been backed up may be lost on app removal. Public policies and support remain available without installing or paying for the game. Parents can request access, correction, deletion or an explanation of the data practices through the Moola support route. We do not require disclosure of more child data to use the game.