Makie Privacy Notice
Updated 9 October 2026
Makie is operated by Askie Kids AI Limited. This notice covers Makie and supplements the Askie privacy policy for families who use both products.
Information Makie uses
Makie uses the adult's authenticated account, child profiles, optional child sign-in emails and invite status, maker usernames, game prompts, project source and revisions, generated assets, Make Credit and subscription records, Stripe billing identifiers, game data and scores, positive reactions, play counts, reports, and security logs needed to provide and protect the service.
Publishing and public data
Games are private until a maker chooses to publish. Anyone with a published link can play that fixed version. A maker may also list the version in Explore and choose whether signed-in Makie users can make a private copy. A copy includes the published code and assets with attribution, but not the original app's saved data or scores. Like counts, play counts, and Makie usernames may appear publicly. Askie profile names and child emails are not shown. Makers can stop sharing or remove an app from Explore at any time.
AI services and voice input
Makie uses third-party AI services to build, repair, illustrate, and safety-check games. When a maker asks Makie to build, change, or fix a game, Makie sends the request, the child's age, and the game's source code, error messages, and screenshots to Google Gemini on Google Cloud. If Google is temporarily unavailable, OpenAI may process the same data as a backup. Google Gemini also draws game art and cover images, checks photos a maker attaches to a request, and, before an app is listed in Explore, reviews its name, player-visible text, and source code for critical scams and inappropriate content. When a game has a talking character, what a player types to it is sent to Google Gemini (or OpenAI as a backup) to write the reply. TypeSafe checks game names and Makie usernames, with the child's age, to make sure they are suitable to show publicly. These providers process the data only on our instructions and only to provide these features, under agreements that require the same or equal protection as this notice; Google and OpenAI do not use it to train their models. The Makie iOS app asks a grown-up for permission before anything a child types, including messages to a game's AI characters, is first sent to these providers, and Makie's servers refuse these AI features in the app until that permission is given. Optional dictation uses the device's or browser's speech recognition service; Makie receives the transcript, while the device or browser provider handles the audio under its own terms.
Cookies and measurement
Makie uses essential storage for authentication, language, security, and service operation. Makie follows Askie's existing analytics cookie choice and opt-out behavior through the shared banner. Unless analytics have been declined, Makie sends the approved action names, broad counts, stable game project identifiers, and context such as template, category, source, plan, and visibility described above.
Advertising measurement
Makie measures which of its ads bring in new families. This concerns only the grown-up's account, never a child's games, prompts, or messages. When a grown-up creates a Makie account, and again when they add their first maker, Makie's servers send a sign-up event to Meta (the company behind Facebook and Instagram) through the Meta Conversions API. Each event contains the grown-up's email address and Makie account ID, both scrambled (hashed) before they leave our servers, plus the IP address and browser or device details (user agent) of that request, and, on the website, Meta's ad click identifiers when the grown-up came from a Meta ad. Meta uses this to match the sign-up to an ad and to report how our ads perform. The Makie iOS app includes the AppsFlyer SDK, which records when the app is installed and opened so we can see which ad campaign led to the install. AppsFlyer receives the IP address, device details such as model, operating system, and language, an app-specific device identifier, an AppsFlyer install ID, and, while a grown-up is signed in, their Makie account ID. The app does not ask to track you and does not collect the device's advertising identifier (IDFA). For App Store purchases, RevenueCat receives a copy of the purchase with the AppsFlyer install ID, so the purchase can be credited to the right campaign. Makie's website uses Google Ads to measure which ads lead to sign-ups and first subscription payments, using Google's ad click identifier rather than an email address. Makie never sends a child's name, age, games, or anything a child types to Meta, AppsFlyer, RevenueCat, or Google Ads.
Other service providers
Makie also relies on these providers, and each receives only what its job needs. Auth0 runs sign-in and holds the grown-up's email address and login details. Stripe processes payments on the website and receives the payment details, billing address, and an email address for receipts. Apple processes App Store purchases and sends Makie a signed record of each one so the plan can be unlocked. PostHog records how Makie is used, such as which features are opened and the size and cost of each AI request together with the child's age, linked to the grown-up's account ID; it does not receive email addresses or the words of prompts and messages. PostHog also keeps our server logs, with email addresses and names removed. Sentry receives crash and error reports without names or email addresses. Resend delivers Makie emails, such as a child's sign-in invitation. Railway, MongoDB Atlas, and Cloudflare run Makie's servers, database, and game file storage.
Retention and deletion
Projects remain until they are deleted or the Makie account is deleted. Deleting Makie permanently removes Makie projects, drafts, scores, public links, reactions submitted by that Makie account, creator notifications, assets, and maker usernames without deleting the Askie account. A private copy made by another maker remains that maker's separate project with its attribution record. Limited billing, security, legal, or backup records may be retained when required.
Family choices
A parent or guardian can review Makie projects, add or remove a child's optional sign-in email, stop sharing, remove an app from Explore, stop future copying, change maker usernames, delete games, or permanently delete Makie from settings. Stopping future copying does not delete private copies already made by other makers. Applicable privacy rights can also be exercised through the contact below.
Contact
A grown-up can contact Askie Kids AI Limited about Makie at askie@kidsai.app.