Privacy, kept short.

Nothing about your child

This is the heart of it: nothing about your child ever leaves the phone — no child profiles, no progress files, no behavioural data, no analytics reach us. In the app, learning content and narration are fetched anonymously, so we hold no record of what your child read, tapped, or played. A “kid space” is only a parent-chosen nickname, a symbol, and an age range — never your child’s real name, photo, voice, or any identifier. How much time each kid has used or earned lives only on the device — for your eyes, never ours — and resets daily. Private by construction, not by policy: our servers have no place to put a child’s data.

What we collect (from you, the parent)

In the app: your phone number. You sign in with it and a one-time code we text you — there is no password, and no Google or email sign-in. Your number isyour account: it is what your subscription is held against, which is why Slate works on any phone you sign in on. Kid spaces live only on your phone — our servers store nothing about them. Slate holds no passcode of its own: ending Slate Time uses your phone’s own lock, which we never see. (Older versions of the app kept a Slate parent code on the phone. It never left the device either, and updating from the store removes it.)

When you pay: the payment itself is handled by the store — Google Play Billing on Android, Apple’s In-App Purchase on iPhone and iPad — or by Razorpay if you subscribe on this website. Your card number, CVV, UPI PIN and bank login never reach us — you type those into the payment provider, never into Slate. What we keep is your subscription’s state (which plan, whether it renewed, when it runs out) and the receipt the provider sends us. For a web payment that receipt can name the method used — a masked card, meaning its last four digits and issuer, or your UPI ID — and we keep it as the record of what you paid.

On this website: nothing personal for simply reading it. The site keeps an anonymous record of visits — which pages were opened and which link brought you — and keeps it with no time limit, so we can compare this month with any month before. Nothing in it names you. Your browser is given a random number, kept in a cookie, so that five hundred visits can be told apart as, say, a hundred and twenty devices. It is attached to no name, no phone number and no account, it is never handed to anyone, and clearing your cookies ends it. We also note how far down a page you read, which is how we tell a page people finish from one they leave. Your network address is scrambled into a short code before it is stored, so we can tell one busy visitor from a hundred and keep robots out of the counts, and cannot read the address itself. If you came here from a Facebook or Instagram link, we tell that ad network, from our server, that its click reached this site, whether it reached a store link (by your tap, or by one of our campaign pages opening your phone’s store for you after its short countdown; one visit counts once either way), and, if you then subscribe here, the plan and the amount paid. With each we send the click id it put in the link, an anonymous browser id and your browser’s user agent (the line every browser sends naming itself and its version), and for a visit or a store link also your network address, which Meta uses to match its click. Never your name. If you subscribe here without coming from such a link, Meta still hears of the payment, with its plan and amount and your browser’s user agent but no click id and no browser id. If you create an account, start a free trial, pay or renew, we also send Meta your phone number in hashed form, as described below. There is no ad network script on the page. Joining the community happens on WhatsApp, not here. If you subscribe here, it is the same phone number and one-time code as the app, and Razorpay takes it from there.

Your phone number, hashed: when you first sign in and so create your account, start a free trial, make the first payment of a subscription, or are charged for a renewal, on any phone or on this site, we also send Meta your phone number in hashed form: run through a one-way formula (SHA-256) before it leaves our server, the way Meta asks for it. Meta compares it with the numbers on its own accounts to tell whether one of its ads reached you. That is how a sign-up, a trial or a payment on an iPhone, which passes no click id to the app, can be counted at all. With a payment or a renewal go its plan and amount, and with a payment made on this page also your browser’s user agent, which Meta requires for anything that happened on a website, whether or not a link of theirs brought you. A first payment on this site that Meta has not already heard about from this page (because you closed it before the payment confirmed, or the payment was still going through when the page checked) we tell it about this way, a few minutes later. A hash of a phone number is still personal information, so we say so here. We send it only with those four events, never when you sign in again or at any other time, we do not keep the hashed copy, and it never says anything about your child.

One piece of history: an early version of this site had a waitlist form that asked for a name and phone number. The form is gone and we collect neither here any more. If you signed up through it back then, email us and we’ll delete your entry.

What we never do

We do not sell your data. We show no ads, and the app contains no third-party advertising, analytics, or tracking SDKs. We do not follow you across other companies’ apps or websites, and we hand nothing to data brokers. The only things an ad network hears from us are what became of its own click, a payment made on this site whether or not its click brought you, and, as described above, your phone number in hashed form when you create your account, start a free trial, make a first payment or are charged for a renewal. About its click, it hears that it reached this site, whether it went on to a store link (tapped, or opened for you by a campaign page’s countdown), whether you subscribed here and for how much, and, on Android, that the app was then installed, a free trial started and the first payment of each subscription was made, with its plan and amount. Google Play passes the click’s id to the app, or, when the ad opened the store directly, the ad network’s own record of which ad it was, and we pass that back. With it goes a random number the app makes up once, when it is installed, so the network can tell that the install, the trial and the payment belong together. It is not an advertising ID and says nothing about you. We also send the phone’s model, Android version, language, time zone and screen size, which Meta requires for an app event.

We do not send marketing spam. And — to say it plainly — we never track your child.

Security

Data is encrypted in transit. Your account is protected by your phone number and the one-time code sent to it, and ending a Slate session requires your phone’s own lock — Face ID, Touch ID, a fingerprint, or your PIN, pattern or passcode. That check is the operating system’s; Slate is only told whether it passed.

Children’s privacy

Slate is used by a child but set up and managed by a parent. Because nothing about the child ever leaves the device, we meet children’s-privacy rules — India’s DPDP Act and equivalents elsewhere — by design. A parent is always in control.

Your rights (DPDP Act)

Under India’s Digital Personal Data Protection Act, you can ask us to show, correct, or delete your data, and withdraw consent, at any time. Email support@slatekids.com and we’ll act promptly.

When you delete your account — from Settings → Delete account in the app, or by writing to us — your number, your subscription record and everything else held against it go, and it cannot be undone. If that number bought a plan through the App Store or Google Play, or used a free trial, one small record stays behind: a scrambled, one-way form of the number (the digits cannot be read back out of it), the store’s reference for that plan, and which free trial the number used. If it did neither — no store plan and no trial — nothing stays behind at all, and a plan bought on this website leaves no store reference either.

That record holds no name, no digits, no payment details and nothing whatsoever about your child. It exists for two reasons: so a plan bought on one number cannot be claimed by a different number — even where the store links a later purchase to the same plan — and so a free trial cannot be taken again and again by deleting and starting over. Sign back in with the same number and you pick your own plan back up — the store part of the record is deleted the moment you do. Otherwise we stop using it two years after the deletion (or two years after the store last linked a new purchase to that plan, if that is later), and records past that point are deleted.

Changes

If anything here changes, we’ll update this page and the date above.