Privacy & cookies

Controller and scope

The controller is moonwalkHQ SAS, 10 rue de Penthièvre, 75008 Paris, France. For Draawee privacy questions or rights requests, write to privacy@moonwalkapp.com with “Draawee” in the subject, or send your request to the registered office. This shared privacy contact is published on Moonwalkapp. The identity and scope of any appointed DPO remain to be confirmed; a contact mailbox alone does not establish a DPO appointment.

This website

The code includes no analytics or advertising trackers. Images and the Draawee display font are served locally. The existing Plus Jakarta Sans stylesheet is requested from Google Fonts, so the browser contacts Google’s font servers; this must be included in the production privacy review. Local storage under draawee-motion remembers only the requested animation preference. A rights-request template, where offered, is created locally and not submitted. Hosting logs and any sign-in infrastructure require their own documented purpose, basis, recipients and retention.

App data inventory

The app code checked on 29 October 2026 sends the drawing photo to the server during preparation, before video generation starts. Story requests also send the entered first name, character, mood and language. Starting a video sends the drawing or its reference and the story text. These flows apply during preparation even if no video is ordered. Child profiles and mission records are stored locally. The first name is also used to personalise story and video requests.

The project envisages installation and purchase identifiers for credits; drawings, character names, story inputs and videos for generation; first names for organising child profiles; notification tokens for readiness updates; and technical logs for reliability and security. Each purpose needs a documented legal basis and retention. A contract with a parent does not by itself justify all processing concerning a child.

Providers and transfers

The client defaults to an API on Cloudflare Workers and integrates RevenueCat and Carillon depending on its configuration. Code alone does not establish production configuration, processing locations or the server’s AI providers.

The project mentions a generation server, RevenueCat for credits and purchases, Carillon for notifications, and Apple or Google for store purchases. Their exact roles and data flows must be confirmed. Complete the list of hosting and AI providers, countries, contracts, recipients and any international-transfer safeguards. No EU-only hosting, transfer safeguard or no-training commitment is claimed without verification.

Retention, deletion and security

The current deletion action removes the film from the device and hides the creation, while retaining a mission-history record. This action contains no server-deletion request; it must not be described as erasing all copies or associated data.

Retention periods for source drawings, stories, videos, temporary files, backups, logs, identifiers, support and accounting records remain to be documented, along with deletion criteria and timing. Local profiles, server copies, backups and shared files must be distinguished. Deleting an item or uninstalling must not be presented as complete erasure without verification. Document actual access controls and security measures and evaluate whether a data protection impact assessment is required.

Children and AI

An adult operates the app. Photograph the artwork without unnecessary personal information. Information must be clear and appropriate for the people concerned, including children. Representation rules and, where consent is used, rules concerning minors must be considered. Whether providers use drawings to train AI is not established by the available project documents and must be clarified before collection.

Your rights

Depending on the processing and legal basis, you may have rights of access, rectification, erasure, restriction, portability and objection. Consent can be withdrawn for the future. Responses are generally due within one month, with justified extensions as legally permitted. Identity evidence should be proportionate where reasonable doubt exists, not requested systematically. You may complain to the CNIL. See Personal data & DPO.

Cookies and updates

No consent banner for nonexistent advertising or analytics is added. Any future non-exempt tracker requires the appropriate choice mechanism, including accessible refusal and withdrawal. Production hosting and authentication must be audited. Complete this draft before collecting app data and explain material processing changes at the appropriate time.