Who writes here
Every guide carries the name of the person who wrote it, a line explaining why they are qualified to write about that topic, and the date it was published. Click any byline and you get their profile, their background and everything else they have written.
We do not publish anonymously, and we do not publish under a house byline. If nobody is willing to put their name to a page, the page should not exist.
What we actually test, and what we do not
This matters more than any claim about expertise, so we are specific about it.
We do test the settings we tell you to change. When a guide says where a control lives in Snapchat, Android or Google Family Link, somebody opened that app on a real device and followed the path. When a screen has moved in an update and our instructions no longer match, that is a bug in the guide and we fix it.
We do not run comparative lab tests of competing products, and we do not publish benchmark numbers. Where a guide mentions another company's app, it is describing publicly documented behaviour, not a test result. We say so rather than implying a rigour we do not have.
We are not clinicians. Guides touching on sleep, anxiety, addiction or self-harm describe what research bodies and health services say, with a link, and stop there. We do not diagnose, and we say plainly when something needs a professional rather than a phone setting.
How we handle sources
- Platform behaviour comes from the platform. If we describe what WhatsApp shows in a notification, the source is WhatsApp's own documentation or the app itself — not another blog's summary of it.
- Research claims get a link to the study or the organisation, not to a news article about it. Where evidence is thin or contested, the guide says so instead of picking the finding that suits us.
- Legal points are described as varying by country, because they do. Nothing here is legal advice, and guides say when to check local law.
- Numbers get dates. A statistic without a year is not worth printing.
Where AI is used, and where it is not
We use AI tools the way most publishers now do: for research summaries, for drafting structure, and for catching clumsy sentences. We think pretending otherwise would be dishonest.
What does not happen: no guide is published as machine output. Every page is rewritten by the named author, who adds the specific detail, the judgement calls and the honest limits that a model cannot invent — and who is accountable for what it says. Where a guide describes a menu path, a person walked it. Where it makes a recommendation, a person stands behind it.
If a page ever reads like it was generated and shipped, that is a failure on our part and we would like to know.
Reviewing and updating
Guides about apps go stale quickly, because the apps change. Two things follow from that:
- Dates are shown, not hidden. Every guide shows when it was published and, if it has been revised, when. We do not quietly bump a date to look fresh — an updated date means the content changed.
- Some guides carry a “checked by” line. Where a second person has read a page against the current version of the app, their name and the date are on it. Where no second person has, there is no line — rather than a review badge nobody earned.
Independence, and how we make money
We build a parental monitoring app, and we write guides for parents. That is a conflict of interest and the only honest thing to do is name it.
What we do about it:
- Guides answer the question, not the sales pitch. Where the best answer is a free tool built into the phone — Android's own Family Link, Apple's Screen Time, a platform's own Family Center — the guide says so and explains it properly. Several of our guides recommend doing nothing at all.
- We say what our own product cannot do. Encrypted messages cannot be read. Our own pages say this repeatedly, because the alternative is selling something that does not exist.
- Nobody pays for coverage. No sponsored guides, no paid placements, no affiliate links in the guides.
- Advertising, where it appears, is clearly advertising and is never allowed to shape what a guide says.
Corrections
We get things wrong. When it is pointed out, we fix the page, note what changed, and move the updated date. We do not silently edit and pretend the error never happened.
If something here is wrong, out of date, or reads as sales copy dressed up as advice, tell us on the contact page. Specific corrections — a setting that has moved, a claim that no longer holds — are the most useful mail we get.
Read more
The about us page explains why the app is built to be visible rather than hidden, and which features we deliberately refused to build. The parental control guides are the work itself. The privacy covers what we collect from this website and from the app.