Privacy Policy

GalaxyBuilder is a creation platform where children ages 5–13 build games and apps with AI guides, under a parent's account. We designed our data practices for children first: we collect the minimum needed to run the Service, we never sell personal information, and we never use children's information for advertising.

1. Accounts belong to parents

Only a parent or legal guardian may register. Children use the Service through the parent's account; there are no child-held accounts, no child email addresses, and no direct messaging between children or from strangers. Everything in this policy about "your child's information" is information you, the parent, can see, correct, and delete.

2. Information we collect

From you (the parent):

• Email address and account credentials (passwords are stored hashed by our authentication system; we never see or store your password in plain text).
• Subscription and billing status. Payment cards are processed by our payment processor; we receive confirmation and the last four digits only — we never store full card numbers.
• Your parental-control choices and approval decisions (for example, approvals for sharing a creation), which we keep as consent records.
• Messages you send to our support.

From your child, through your account:

• A first name or nickname and an age band (for example, 8–10) that you provide for the child profile. We do not ask for a child's full name, birthdate, address, school, or photo.
• What your child types to the guides (their ideas and instructions), the guides' replies, and the safety-screening results for both.
• Your child's Creations (games, apps, and the art and text inside them) and in-Service activity needed to run the builder — build history, library assets used, and play activity on their own Creations.

Automatically, for operation and security:

• Device, browser, and log data (IP address, timestamps, error and security logs). We use cookies that are strictly necessary to sign you in and run the Service. We do not use advertising cookies, analytics trackers, or any third-party advertising technology.

3. How your child's words and Creations are processed by AI

This section matters, so it is specific.

• Guides and building. To power the guides and the builder, your child's prompts and the build's working text are sent to OpenAI, our AI provider, through its API (chat completions / responses endpoints, with storage disabled — store: false). No account identifiers are included in those payloads. Parent consent checks and all code execution happen on GalaxyBuilder's own infrastructure, not at OpenAI.
• Zero Data Retention status — stated plainly. We have requested OpenAI Zero Data Retention (ZDR) for our API usage and will update this policy when it is granted. Until then, OpenAI processes API data under its standard API terms, which may include retaining inputs for up to 30 days for abuse monitoring. We will not describe ZDR as in place before it is.
• Safety screening. Everything your child types, everything the guides reply, and every finished Creation is screened — first by rules on our own servers, then by an AI safety check through the same OpenAI API — for unsafe content and for personal information. If a child types personal information, the screening is designed to block it and steer the conversation away; flagged content may be retained in our security logs so we can keep the Service safe and show you what happened.
• AI drawing. When the art library has no match for something your child asks for, our system — not your child — writes a short art description (subject, style, colors only; never your child's words, name, or any personal information) and sends that description to OpenAI's image service. The returned image is screened by an automated vision safety check before it can appear in a Creation, and approved images are kept in the library for reuse. If the image service's own safety systems flag a description, OpenAI may retain that system-written description for its review.
• Hosting. The Service runs on DigitalOcean infrastructure, and Creations and library files are stored in DigitalOcean Spaces. These providers process data only to host the Service for us.

We do not use your child's information to train our own models, and our API agreements prohibit OpenAI from training its models on data sent through its API.

4. What we never do

• We never sell personal information — yours or your child's.
• We never advertise to children, and we never build advertising profiles of children.
• We never allow direct contact between children and strangers, and there is no public feed of children's profiles.
• We never make a child's Creation public without your approval, recorded in your parent account.
• We never ask a child for more information than the builder needs.

5. When information is shared

Only in these cases: (a) with the service providers named in Section 3, under contracts limiting them to providing the service to us; (b) if required by law, court order, or to protect a child's safety; (c) in a merger or sale of the company, with notice to you before your information becomes subject to a different privacy policy. There are no other cases. Other families cannot see your child's information or Creations unless you approve sharing a specific Creation, and sharing shows the Creation only — never your child's profile information.

6. Your parental rights (COPPA)

Under the Children's Online Privacy Protection Act (COPPA) and this policy, you may at any time:

• Review your child's information and Creations — they are visible in your parent account at all times.
• Refuse further collection and request deletion of your child's information: email us at [CONTACT: insert privacy email before publication] or use account settings. Deleting the child profile deletes the child's prompts, screening records, and Creations, except: consent and approval records we must keep to prove consent was given, and security logs retained as described below.
• Withdraw consent by deleting the child profile or your account; your child will no longer be able to use the Service, and their information will be deleted as described above.

We verify that deletion and review requests come from the account holder before acting on them.

7. Retention

• Account and child-profile information: kept while the account is active, and deleted within 30 days after account deletion, except consent records (kept to demonstrate consent) and security logs (kept up to 12 months for safety and fraud prevention, then deleted).
• Backups: deleted data is removed from backups within 30 days in the ordinary backup cycle.
• Creations you have approved for sharing remain visible until you withdraw approval or delete them, whichever comes first.

8. Security

We protect information with encryption in transit, access controls that limit data to the systems and people who need it, row-level security in our database restricting each family's data to that family, and the safety screening described above. No system is perfect; if a breach affects your child's information, we will notify you as required by law.

9. Changes to this policy

If we change how children's information is collected, used, or shared in a material way, we will email you first and obtain your fresh consent before the change applies to your child, as COPPA requires. Other updates take effect when posted, with the version number and date at the top of this page updated.

10. Contact

Privacy questions, reviews, and deletion requests: [CONTACT: insert privacy email before publication] [OPERATOR: insert operator legal name and mailing address before publication — COPPA requires the operator's name and contact information to appear in this policy.]

Registration consent (implemented at sign-up)

The Privacy Policy is accepted through the same unchecked-by-default checkbox as the Terms of Service (see the Terms of Service, "Registration acceptance"). Each acceptance is recorded with the account ID, the policy version accepted, the date and time, and the registration-checkbox method, forming the family's COPPA consent record. Adding a child profile inside the account requires the parent to confirm the same consent for that child before the profile is activated.

Terms of Service · Privacy Policy · Contact us · Return to GalaxyBuilder