Version 1.0 — March 2026

Privacy Policy

1. What data we collect

Parent accounts:

  • Name, email address, and password (hashed)
  • Language preference
  • Consent records (timestamps, versions)

Child profiles:

  • Display name (chosen by parent)
  • Date of birth (used to determine age tier)
  • Avatar selection
  • Voice recordings during game creation sessions (processed in real-time, not permanently stored)
  • Game and app content created on the platform

2. How we use your data

  • To provide and operate the Buildaloo platform
  • To personalize the experience based on age tier
  • To send account-related emails (verification, password reset)
  • To send tips and offers by email, if you opted in. You can unsubscribe at any time from any of these emails or from parent settings.
  • To moderate content for child safety
  • To improve our service and fix issues
  • To analyze usage patterns and improve the platform (see section 4 for details on analytics)

We do notsell your data or your children's data to third parties. We do notuse children's data for advertising or profiling purposes.

3. Children's data (COPPA compliance)

Buildaloo is designed for children ages 5–12 and complies with the Children's Online Privacy Protection Act (COPPA). We collect only the minimum data necessary to provide the service.

  • Parental consent required: A parent must create the account and consent before any child profile is created.
  • No direct collection from children: Children interact through voice; we do not ask children for personal information.
  • Parental access:Parents can review, modify, or delete their child's data at any time through the parent dashboard.
  • Voice data: Voice recordings are processed in real-time for speech-to-text conversion and are not permanently stored.
  • No tracking on children's pages: We do not use cookies, analytics scripts, or any third-party trackers on pages where children interact with Buildaloo. Server-side analytics collect only aggregated, anonymized metrics (e.g., total games created per day) that cannot identify individual children.

4. Third-party services

We use the following third-party services to operate Buildaloo:

  • PostHog — product analytics. On parent-facing pages (login, registration, parent dashboard), PostHog collects anonymized page views, session data, and feature usage to help us improve the platform. PostHog is never loaded on children's pages — no cookies, scripts, or tracking of any kind runs while a child is using Buildaloo. Server-side analytics about game-creation steps and build outcomes are sent using a one-way hashed identifier so an individual child cannot be re-identified from the analytics data. PostHog is hosted in the EU. See PostHog's privacy policy.

    On marketing, waitlist and registration pages we store two first-party attribution cookies (30-day lifetime): buildaloo-utm-firsttouch (the first campaign or landing we saw) and buildaloo-utm-lasttouch (the last utm_* before you sign up). They record utm_source, utm_medium, utm_campaign, utm_term, utm_content, the external referring host and path, and the landing path. We use them only to tell which posts and links lead to signups — not for advertising. They contain no name or email on their own and are never set on children's pages. When you create an account, we copy first-touch and last-touch onto your parent account in our database. These attribution cookies are set even if you decline analytics cookies; rejecting analytics only stops PostHog.

    PostHog is gated by your choice in the cookie banner that appears the first time you visit a public Buildaloo page. If you reject analytics cookies, we never load PostHog and never send attribution to it. You can change your mind at any time using the link, or via "Cookie preferences" in the footer.

    On registration we also ask an optional question, "Where did you hear about Buildaloo?". Your answer is stored on your account and does not use cookies.
  • Resend — email delivery (verification emails, password resets, and tips and offers to parents who opted in). Receives parent email addresses only.
  • Deepgram — speech-to-text processing. Receives voice audio during active sessions. Audio is processed in real-time and not stored by Deepgram.
  • ElevenLabs— converts Loo's text responses to natural-sounding speech. Voice audio is generated in real-time and not stored by ElevenLabs. No personal data is shared.
  • Anthropic (Claude)— AI conversation and game generation. Receives conversation text (not voice audio). Subject to Anthropic's data handling policies.

5. Data retention

  • Account data: Retained for the lifetime of the account.
  • Voice recordings: Processed in real-time and not permanently stored.
  • Game content: Retained until the parent deletes the game or the account.
  • Conversation logs: Retained for up to 90 days for content moderation, then automatically deleted.

6. Data deletion rights

You have the right to:

  • Request a copy of all data associated with your account
  • Delete individual child profiles and their associated data
  • Delete your entire account and all associated data
  • Withdraw consent at any time

To exercise these rights, contact us at privacy (at) buildaloo.com or use the account settings in the parent dashboard. We will process deletion requests within 30 days.

7. Security

We implement industry-standard security measures to protect your data, including encrypted connections (HTTPS), hashed passwords, and secure session management. However, no system is perfectly secure, and we cannot guarantee absolute security.

8. Changes to this policy

We may update this privacy policy from time to time. We will notify registered users of material changes via email. The version number and date at the top of this page indicate the latest revision.

9. Contact

If you have questions about this privacy policy or our data practices, contact us at privacy (at) buildaloo.com.

buildaloo