Kidcyclopedia Unlock everything

Privacy

Last updated: 16 November 2026

Kidcyclopedia is made for children. This page says what happens to information when your family uses it. It is written in plain words on purpose. If anything here is unclear, write to us and we will explain.

Who we are

Kidcyclopedia is run by Sticky Wicket Labs LLC.

We are the only company that runs Kidcyclopedia. The companies we use to run it are listed below, with what each one receives.

The short version

The child's side of the app

The child's side is everything outside the Grown-ups' Corner: the first page, the cards, the library, the scrapbook, and the screens that say "ask a grown-up".

We do not collect personal information from children. The child's side does not ask for a name, age, photo, voice or location. There is no child account. It sends nothing about which cards your child reads, and no identifier of the device. We do not ask a child for more than the app needs, because it needs nothing.

Counts, not children. The app counts how its cards are used, never who uses them. When one of a few things happens on the child's side (a card from one of our ads reaches the screen, stays on it for 10, 30 or 90 seconds, is heard, or is followed by another card; the library is opened; the gift card at the bottom of the table appears, is tapped or is closed; the screen that says new cards open with a grown-up appears; and, on a visit from one of our ads, the grown-ups' strip at the top appears or is tapped, or "Save for tonight" is tapped), the app sends our database two things only: what happened, and which of our ads brought the device ("direct" if none, "tonight" if it came from a link a grown-up emailed to themselves). While we test how many cards to give free to visitors from one of our ads, the second also says which of the two groups the device is in, named by how many cards it was given free (for example "KC-08-fly-p10"). Our database adds one to that day's total and keeps nothing else: no identifier, no visitor number, no card, no time of day, no device details, and no internet (IP) address (like any request, it passes through Supabase's server logs, described below). A device counts each thing at most once a day; it remembers what it has already counted that day on the device itself and never sends that memory. The daily totals are deleted after 90 days, like our other counts.

The app does need to download cards, pictures and recordings from our website to show them. Like every website, our web host sees each download's request, including the internet (IP) address it came from. That is used only to deliver the page and keep the service safe, as described under "How long we keep things". And if a grown-up has signed in or opened a gift on the device, the app checks with our database that the family's unlock is still valid, using that grown-up's sign-in. That check carries nothing about what the child does.

The one exception is the synced reading history described below. Only a grown-up can turn it on, and it is not offered to customers today.

What stays on the device. The app keeps these things on the device itself, so it can work, and never sends them from the child's side:

Clearing this site's data in the browser removes all of it.

In the Android app

The app from Google Play does less than the rest of this page describes.

In the iPhone and iPad app

Kidcyclopedia is not in Apple's App Store yet. When the iPhone and iPad app is released, it will do less than the rest of this page describes:

Buying in the iPhone and iPad app. The purchase will be made through Apple's App Store, behind the grown-ups' gate. Apple will take the payment under its own privacy policy, and we will never see card details. The app will send our server Apple's transaction number for the purchase; our server will ask Apple whether it is paid, and keep a record of it with Apple's transaction numbers. So that the purchase opens the right family's library, the app will hand Apple a random code made from the family's account (never a name or an email). No email will be needed to buy. If a grown-up is signed in, the purchase will follow that email to their other devices, like a purchase on the website.

What we collect from grown-ups, and why

Signing in. A grown-up can sign in with an email address and a one-time code we email to them. There is no password. We keep the email so the family's unlock works on every device they sign in on.

Buying. The full app is a one-time purchase. Stripe takes the payment. We keep a record that the purchase happened: the email you paid with, the price, the date, Stripe's reference to the payment, and the random visitor number of the browser you bought on. We use it to unlock the app on your family's devices, to answer refund requests, and to count which price was bought. We never receive or keep card numbers.

Buying in the Android app. In the app from Google Play, the purchase is made through Google Play instead, behind the grown-ups' gate. Google takes the payment under its own privacy policy, and we never see card details. Our server asks Google whether the purchase is paid, and keeps a record of it: Google's order number and purchase reference, the country Google gives for it, the date, and whether it was a test purchase. So that the purchase opens the right family's library, the app hands Google a random code made from the family's account (never a name or an email). No email is needed to buy. If a grown-up is signed in, the purchase follows that email to their other devices, like a purchase on the website.

Gifts. When you buy a gift, we keep your email, the "from" name you type and the note you write, with the gift's code. Please know that the note may name a child: it is shown to the family who opens the gift, it is stored by us, and it is passed to Stripe with the payment. We email you the code once, through Resend. We never write to the family you give to.

Opening a gift. A gift opens with one tap, without an email. To keep it open on that device, the app makes an anonymous account for it: no name, no email, just a random account that holds the unlock. A grown-up can add an email to it later, to open the gift on another device.

Passing it on. A family that has unlocked can share a link. We keep the link's code, which family it belongs to, and which purchases came through it, so we can give the reward. We never write to the family the link is shared with.

Saving a card for tonight. If a grown-up asks us to email them a card, we use the address once, to send that one email through Resend. We keep only a scrambled fingerprint of the address (it cannot be turned back into the address) for 12 months, so we never email it twice, and we count how many of these emails went each day. Nothing about the child is asked for.

Waitlists. If you join a waitlist, we keep your email and what you waited for. We use it once, to say the thing is ready.

Asking for free access (teachers, schools and libraries). If you fill in the form on /schools/ or /libraries/, we keep what you type: your name, your role, your school or library, its town and country, your email and, if you give them, roughly how many classrooms or devices and your message. We use them to reply to you and to set up your access, and we email ourselves a copy (through Resend) so we know a request came in. They are kept in our database at Supabase until you ask us to delete them: write to the email address at the top of this page and we will delete them within 30 days. To stop the form being flooded, we also count each day's requests against a scrambled form of your email and of your network address (scrambled with a key that changes every day, so it cannot be turned back or matched across days), and delete those counts after two days. Nothing about a child is asked for.

The family's synced reading history. The app can copy a child's reading trail from the device to the family's account, so it shows on the grown-ups' page on another device. This works only on a device a signed-in grown-up has paired, and only for families we have added by hand to a family list. It is not offered to customers today. If we offer it, we will update this page first, and it will stay off until a grown-up turns it on.

Counting on the grown-ups' pages

To learn what works, we count a few things on the pages made for grown-ups: the Grown-ups' Corner in the app (behind the grown-ups' check), the gift screen a grown-up opens from a gift link, the page a friend's link opens, our website pages at /about/, /gift/ and /gift/diwali/, the pages our ads open at /go/, and the single-card pages at /q/ that grown-ups share with one another. On the child's side of the app, only the anonymous daily totals described above are counted.

There is no advertising tracker anywhere on the site and in the app. We do not use a Meta (Facebook) pixel or any other ad pixel.

Who we share information with

We use these companies to run Kidcyclopedia. Each one gets only what it needs for its job, and none of them may use it for anything else.

What we tell Meta (Facebook), and what we don't. We advertise on Facebook and Instagram, and we want those ads to reach families who end up buying, not just people who tap. So when someone starts a payment or finishes one, our server (not your browser, and never the child's side of the app) tells Meta that it happened: the page it started on, the price and currency, and a reference number for the payment. To let Meta match it to the ad that was tapped, three things go with it: the click code Meta adds to the web address when someone taps one of our ads (if you arrived that way; we keep it on your device for 28 days and send it only when you start a payment), your IP address, and the kind of device and browser you are using. We never send Meta your email, your name, your card, anything about your child, or a gift's code, "from" name or note. Visits that do not lead to a payment are never reported to Meta. There is still no Meta pixel or any other ad tracker on the site or in the app.

The voice in the app was recorded in advance with ElevenLabs, and the pictures were drawn in advance; no information about you or your child is sent to ElevenLabs or Google when the app is used (a grown-up buying inside the Android app goes through Google Play, as described above). When someone comments on our Facebook or Instagram posts, we may use Google's Gemini to help draft our public reply: the comment's words go to Google for that, never the commenter's name.

We share information with the authorities only when the law requires it. If Sticky Wicket Labs LLC is ever sold or merged, this policy would still apply to the information we hold, and we would tell you first.

How long we keep things

Your rights as a parent

You can, at any time:

Write to hello@stickywicketlabs.com from the email your family uses, or call or write to us at the address above. We will answer within 30 days. Step by step, with or without the app: how to delete your account. Deleting the information may switch off the unlock on your devices; we will say so before we do it, and refund rules are in the terms.

If you think a child has given us personal information, tell us and we will delete it.

Keeping it safe

Everything sent between the app and our services is encrypted in transit (HTTPS). Only the people who run Kidcyclopedia can reach the database, and only for running it. Card details are held by Stripe, never by us. No system is perfectly safe, and if something goes wrong that affects your information, we will tell you.

Changes

If this policy changes in a way that matters, we will say so on this page, change the date at the top, and ask for a parent's consent again where the law requires it.

Contact

hello@stickywicketlabs.com · 678-642-6727 · 2108 N ST, STE N, SACRAMENTO, CA 95816