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.
- Postal address: 2108 N ST, STE N, SACRAMENTO, CA 95816
- Phone: 678-642-6727
- Email: hello@stickywicketlabs.com
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
- Nothing about your child leaves the device from the child's side of the app. No name, no account, no tracking, no identifier. The app only counts how its cards are used, as anonymous daily totals.
- The child's reading history stays on the device.
- The Android app counts nothing at all (see "In the Android app").
- The iPhone and iPad app is not out yet. When it is, it will count nothing at all either (see "In the iPhone and iPad app").
- We collect information only from grown-ups: an email to sign in, a purchase, a gift.
- We do not show ads. We do not sell or rent data to anyone.
- When a grown-up starts or finishes a payment, our server tells Meta (Facebook) that it happened, so our ads reach families who buy. Never your email, your name or anything about your child.
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:
- the reading history: the cards read, the trail, the journals, the starred cards, and the settings;
- the free-card count: how many of the free cards have been used, and which closed cards were tapped (shown to you in the Grown-ups' Corner). The only part of it that leaves the device is the group described above, on a device in that test;
- when the gift card last appeared at the bottom of the table, so it does not keep coming back;
- whether the device is unlocked;
- the price this browser is shown, a random visitor number, and the name of the ad that brought you, if any. These are used only by the grown-ups' pages (see "Counting on the grown-ups' pages"), except that the anonymous daily totals above say which of our ads brought the device (its number, such as "KC-03", not the ad's full name);
- which of those anonymous totals the device has already added to today.
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.
- It counts nothing. It sends none of the anonymous daily totals described above, and none of the counts in "Counting on the grown-ups' pages", not even from the Grown-ups' Corner. There is no PostHog and no other analytics in it.
- It keeps no visitor number, and it sends no identifier of the device.
- The reading history stays on the device. The app never copies it to the family's account.
- On the child's side, it fetches only the voice that reads the cards aloud (the recordings and their timings), from our website. The words, the pictures and the sounds are inside the app. If a grown-up has signed in, opened a gift or bought the app on the device, the app also checks with our server, using that account, that the family's unlock is still valid. That check carries nothing about what the child does.
- Signing in, buying and gift codes start only in the Grown-ups' Corner, behind the grown-ups' check. Signing in is optional. They keep only what Google Play's Data safety section for the app lists: the email of a grown-up who signs in, the random account that holds the unlock, and the record of a purchase. Looking up a gift code also sends a random number made for that one look-up, which our server keeps for a day to stop people guessing codes.
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:
- It will count nothing. It will send none of the anonymous daily totals described above, and none of the counts in "Counting on the grown-ups' pages", not even from the Grown-ups' Corner. There will be no PostHog, no other analytics and no ads in it.
- It will keep no visitor number, and it will send no identifier of the device.
- The reading history will stay on the device. The app will never copy it to the family's account.
- On the child's side, it will fetch only the voice that reads the cards aloud (the recordings and their timings), from our website. The words, the pictures and the sounds will be inside the app. If a grown-up has signed in or bought the app on the device, the app will also check with our server, using that account, that the family's unlock is still valid. That check will carry nothing about what the child does.
- Signing in and buying will start only in the Grown-ups' Corner, behind the grown-ups' check. Signing in will be optional.
- It will not open gift codes. Apple does not allow an app to be unlocked with a code, so a gift code can be opened on our website instead.
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.
- Our own counts (kept in our database): that a price was shown, that a buy, gift or share button was pressed, that a payment or gift was finished, that a waitlist join was finished, and on the /about/ page, how long the page stayed open and whether the sample cards were played. On a card page (/q/), only that the page was shown and whether "Open this card in the app" was tapped: not which card, and not the ad. On the pages our ads open (/go/), that the page was shown, how long it stayed open, whether the card on it was played, and that a buy, gift or try button was pressed, with which version of the page was shown beside the ad's name. Each count is kept against the browser's random visitor number, the price shown, and (except on a card page) the name of the ad or link that brought you. Never an email, a name, a gift's code or its note.
- PostHog, our product analytics tool, hosted in the EU. It counts a short, fixed list of steps in the Grown-ups' Corner, the gift screen and a friend's page, such as "the corner was opened" (and which way the grown-up came in: from the gift card at the bottom of the table, from the screen that says new cards open with a grown-up, from the "Unlock" label, or from the Grown-ups button), "the unlock was seen", "the payment was started", "a gift was opened". It gets a random code made on the device the first time one of those pages counts something. The code is not linked to a name, an email, an account or the visitor number above. PostHog is set to discard IP addresses, and we never build profiles of people. It records the kind of device and browser (for example, "iPad, Safari"), never the web address, what was typed, or what a child read.
- Vercel Web Analytics, from our web host. It counts visits to our website's pages for grown-ups: /about/ (with this page and the terms), the pages for buying a gift at /gift/, the pages for teachers and librarians at /schools/ and /libraries/, the pages our ads open at /go/, and the card pages at /q/. It never runs in the app: not on the child's side, and not in the Grown-ups' Corner. It does not run on a gift's link either, which only hands over to the app. For each visit it gets the page's address, with a gift's code and every click code taken out first (only the name of the ad that brought you is kept), the site you came from, the country, and the kind of device and browser. It uses no cookies and stores nothing on the device.
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.
- Supabase (our database, sign-in and server code; data stored in the US, us-west-1): the grown-up information above, the purchase and gift records, our own counts, and the IP address of requests in its server logs.
- Vercel (our web host): every request to the website and the app, with its IP address, in its request logs; and the visit counts from our website's pages for grown-ups (Web Analytics, described above), never from the app.
- Stripe (payments): the buyer's email, card details and the billing postal code and country, the price, and for a gift its code, the "from" name and the note; and, so we can tell Meta about the payment, the ad's click code, the IP address and the kind of browser it was started from.
- Resend (email): the buyer's email address and the gift email's content (the code and the "from" name); and the address a grown-up asks us to send a card to, with that email (the card and its link).
- PostHog (product analytics, EU): the counts from the grown-ups' pages described above.
- Google (Gemini, which helps draft our public replies to comments on our Facebook and Instagram posts): the words of the comment being answered. Never the commenter's name, and nothing from the app or the site.
- Google Play (payments in the Android app): Google handles the purchase itself. We send Google the purchase reference to check that it is paid and to confirm it, and the app gives Google the random code that stands for the family's account. Never a name, an email or anything about your child.
- Apple (payments in the iPhone and iPad app, once it is released): Apple will handle the purchase itself. We will send Apple the purchase's transaction number to check that it is paid, and the app will give Apple the random code that stands for the family's account. Never a name, an email or anything about your child.
- Meta (advertising): that a payment was started or finished, the page it started on, its price, currency and reference number, the ad's click code, the IP address and the kind of browser. Described just below.
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
- Our own counts and product analytics: 90 days, then deleted.
- The fingerprint of an address we sent a card to: 12 months, then deleted.
- A gift's "from" name and note: deleted 12 months after the gift is opened or refunded, or 12 months after it was bought if it is never opened.
- Account email and family records (the unlock, the anonymous account of a gift device, a pass-it-on link, a waitlist email): kept while the account exists. Deleted within 30 days of a request to delete them.
- Purchase and payment records: 7 years, because tax law and card disputes require it. Stripe keeps its own copy for the same reasons.
- Server and request logs at Supabase and Vercel: a short time, under their own policies, to run the service and keep it safe.
- Vercel's visit counts (Web Analytics): kept by Vercel under its own policy.
- Everything on the device: until you clear the site's data in the browser, or delete the app.
Your rights as a parent
You can, at any time:
- ask to see the information we hold about your family;
- ask us to delete it;
- tell us to stop collecting any more of it.
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.
- 16 November 2026: added "Asking for free access": what the form for teachers, schools and libraries keeps, and why. Vercel's visit counts also run on those two pages.
- 13 November 2026: added "In the iPhone and iPad app": what that app will do when it is released.
- 13 November 2026: added "In the Android app": what the app from Google Play does not do.
- 11 November 2026: Vercel, our web host, now counts visits to our website's pages for grown-ups (see "Counting on the grown-ups' pages"). Never in the app, and never on the child's side.
- 10 November 2026: we now tell Meta when a payment is started or finished, with the ad's click code, the IP address and the kind of browser, so our ads reach families who buy (see "What we tell Meta").
Contact
hello@stickywicketlabs.com · 678-642-6727 · 2108 N ST, STE N, SACRAMENTO, CA 95816
