Reviews, feature requests and bug reports
The feedback form is for grown-ups. The grown-up’s name and email, message, optional rating, learning age range and app type are sent to Dihaw contact services and internal notifications for follow-up. Feedback is not automatically published. Do not send child identities or recordings. Contact records are separate from learning profiles; learning-profile export or deletion does not automatically include them. Contact hello@kodingkids.id with your reference to request access to or deletion of a message.
Daily missions, collections and family recaps
Device activity dates, executed block types and counts, daily tasks, chest claims, streaks and freezes, XP, badges and decorations are stored with the private learning profile. The detailed journal retains up to 400 days; earned rewards and XP remain stored. Profile exports include this information. Weekly recap emails require a parent to opt in and use the verified account address; turn them off in Parents at any time. Recaps contain activity counts, without child artwork or recordings. Account closure stops emails; permanent KodingKids deletion covers recap preferences and the private profile. There are no public rankings or automatic publication of creations.
About KodingKids
KodingKids is a coding and creativity learning service for children with adult guidance, operated through the Dihaw ecosystem. This policy covers the website and the KodingKids iOS and Android apps being prepared for distribution. Contact hello@kodingkids.id for data questions, access, correction, or deletion.
Parent accounts
Registration and login process the parent’s email, account identity, verification status, and information provided by Google or Apple sign-in when selected. Authentication uses Firebase and Dihaw account services. Passwords are not stored in child progress data. Use a parent account; children do not need a personal email.
Child profiles, progress, and projects
Nicknames, age groups, avatars, challenge progress, learning coins, settings, drawings, Coding Studio projects, and Pet nicknames, appearance, needs, code rules, and test records are stored in the browser on the web and in application storage on iOS/Android. When signed in, the app attempts to sync profiles and projects through the Dihaw API to private Cloudflare storage. The app’s sync status shows whether cloud saving succeeded; while the service is unavailable or offline, data remains local. Child profiles and projects are not automatically published. Exported files are copies on your device; review them before sharing.
macOS and Windows desktop app
The desktop app stores the sign-in session and a progress copy in its application data folder, separate from the browser. Use parent settings to sign out or delete account data according to the guide. Deleting the installer or installing an update does not automatically erase progress or cloud data. Exported files remain on the computer. The installed app includes the activities from its version; internet is required for sign-in, syncing, payments and online voice services. Desktop Google sign-in opens the browser and returns a credential once through a temporary local connection; the intermediate session stays in memory. This desktop version does not load the website’s Google Analytics script. External links open in the browser after a grown-up confirms.
Microphone, recordings, and voice features
The microphone is optional and requires browser or operating-system permission and parental guidance. In native apps, recording requires the parent gate, lasts up to 15 seconds and does not run in the background. Studio character recordings are saved in projects and included in exports and private profile sync when signed in. Speech recognition may process audio through the browser provider. Ciko’s read-aloud feature uses predefined guidance text through OpenAI when available, or device speech. Ciko’s voice service does not accept microphone recordings or children’s projects as input. Avoid personal information in text or recordings. Revoke microphone permission in browser or device app settings. Native read-aloud uses device voices through the operating system.
Storage and third-party services
The browser or application storage keeps language preferences, login sessions and learning data for the service to work. Server requests may include IP addresses and device information for content delivery and service operation. YouTube videos, Google/Apple sign-in, Firebase, Makeblock links, and WhatsApp follow their providers’ policies. Loading embedded videos or external links may send connection information to those providers. The website loads Google Analytics for visits and page navigation, including page addresses, titles and connection information processed by the provider. Native apps do not load the website Analytics script or a native Analytics SDK. KodingKids does not send child names or project content as analytics parameters. Native apps contain no third-party advertising SDK.
Retention and family controls
Signing out does not delete data. When KodingKids deletion is available, parents can request permanent erasure of profiles, progress, projects, recordings within projects and email preferences from active storage. The app shows pending or completed status; acceptance does not mean completion. Shared Dihaw sign-in and other products remain. A minimal deletion receipt and restricted security and email-delivery audits are retained. Exported files, delivered emails and offline device copies cannot be recalled. Contact hello@kodingkids.id for log and backup retention details relevant to your request.
Mobile version and updates
The iOS and Android apps are being prepared and tested. This policy does not claim public store availability. External links, sharing, recording and native account settings use a parent gate. Distribution status is shown on official store pages; the policy revision date appears here.
Need help?
Contact the KodingKids team at hello@kodingkids.id. Manage local learning data in Parents.
Open Parents