Your family’s data in Wonderwild

JuniorCodes uses parent or guardian accounts. We store the adult’s name, email, protected password credentials and sessions, plus child nicknames, age groups, selected avatars and learning work. We do not ask for a child’s email or exact birth date.

Learning and recovery

When you choose Google sign-in, Google shares your basic profile and email so we can identify your parent account. We do not request access to Gmail messages, contacts or Drive files. After a successful sign-in, a browser cookie remembers only the sign-in method (Google or email) for up to 30 days. It contains no email address or password. Use “Forget this hint” on the sign-in page to remove it; it is specific to this browser.

Completed activities, code drafts, experiments and learning preferences are stored with the selected explorer. Pending changes can also be kept on this device for recovery. Sign out on shared devices. Voice selection and pace are device preferences; a device’s speech service may use its own online processing.

Payments and public achievements

Razorpay handles payment collection. Wonderwild stores payment references, amounts and access records, not full card details. Badges and certificates are private unless a parent chooses to publish them. Published pages show the explorer nickname, achievement and issue date and can be made private again. A WhatsApp share card is also created only when a parent chooses “Share on WhatsApp”: it stores and shows the explorer nickname and achievement (never an email or surname), uses an unguessable link and stops working when the parent chooses “Stop sharing”.

Invitations

Each verified parent has a personal invite link. When another family registers with it, we record which account invited which, the join, verification and reward dates, and add the extra month to both accounts. JuniorCodes staff can see these records; the families do not see each other’s details, only a count of families who joined.

Your controls

Family settings provide account export, session revocation, explorer removal and account deletion. Removing an explorer removes their learning records and public achievements. Account deletion removes credentials and learning data. Transaction references and audit records remain for payment reconciliation with parent profile details removed; payment-provider identifiers may still link to provider records. Copies in backups follow the configured backup retention schedule.

Support and launch policy

Support requests are stored with the parent account for staff follow-up. Do not send passwords, card details or unnecessary child information. Region-specific consent, business contact and retention terms must be finalized before public enrollment opens.