What ReKid knows about your child
The honest answer is: almost nothing, and that is a design decision, not a promise.
The four safety layers
Each layer can refuse on its own. The design is fail-closed: when a check cannot complete, the result is dropped rather than shown.
The query
Runs before the model. Blocks the search outright and records the reason. Confusable characters, leetspeak and spacing are normalised first, so disguised spellings are caught too.
The proposed address
Runs on every address the model returns. Blocks adult and high-risk top-level domains, known adult and gambling domains, and unmoderated user-content platforms.
The fetch
Follows redirects one hop at a time and re-checks the destination at every hop. Refuses private, loopback and link-local addresses, so an address cannot be used to reach inside the server.
The page text
Scans the beginning of the real page HTML — title, description and body text. A page whose content trips a rule is dropped even though its address passed.
What the safety layers block
The list below is the topic dictionary, not the whole system: pages are also judged by their address and their actual text.
| Category | Examples of what is blocked |
|---|---|
| Adult content | Pornography, nudity, sexual material, adult sites and adult top-level domains |
| Drugs, alcohol, tobacco | How to obtain or use, purchase sites, vaping |
| Gambling | Betting sites, casinos, odds, loot-box promotion |
| Violence and weapons | Graphic violence, gore, weapon purchase, explosives |
| Hate and extremism | Hate speech, terrorist or extremist material |
| Self-harm | Handled with care — see below |
| Dating and stranger chat | Dating apps, random-stranger video chat |
| Unmoderated user content | Social networks, forums, comment sites, chat platforms |
Self-harm is handled differently
A child asking about self-harm is not misbehaving. ReKid does not return search results for these questions, and it does not scold. It shows a short, warm message encouraging the child to talk to a grown-up they trust, alongside a helpline. Nothing about the question is attached to a name, because ReKid does not know any names.
Two links, no passwords
When you get a licence you receive two links. They belong to the same account and share the same allowance, but they are different secrets — neither can be derived from the other.
The grown-up link
Opens settings, the plan, the remaining allowance and both links. Keep this one to yourself.
The kid link
Opens the search screen and nothing else. This is the one you give your child. From it, the grown-up link is invisible.
Why not a password?
A password would mean collecting and storing one more secret about a family, and children are famously good at watching a parent type. Two separate links give real separation with nothing extra to store and nothing to forget.
What ReKid knows about your child
The honest answer is: almost nothing, and that is a design decision, not a promise.
What rekid.uk stores
- A one-way hash of the access key — the key itself is never written down and cannot be recovered from the database.
- A salted hash of the IP address, used only for rate limiting.
- A two-letter country code, taken from a header the network already sends.
- The search text and the resulting page, so a repeated question can be answered instantly.
What rekid.uk never stores
- No name, no surname, no date of birth, no school.
- No email address and no password — there is nothing to sign in with.
- No raw IP address anywhere, in any table or log.
- No location beyond the country code. No GPS, no city, no third-party lookup.
- No advertising identifiers and no third-party trackers, because there are no ads.
The bridge between this site and rekid.uk is one-way
getrekid.com knows who you are, because you bought something. rekid.uk does not, and cannot ask. This site can tell that account holder X owns key Y; rekid.uk only ever sees key Y. It has no way to learn who searched for what, and neither do we.