A new platform for children with no safety design yet
The idea exists and the technical team is ready, and what is missing is someone to design the platform's data and how its session ends, from the start.
A Dawani service
Safe digital platforms for children
We design digital platforms children use, for bodies and companies that want a platform standing up to a parent's own question: is this actually safe for my child? We build every platform around collecting as little data as possible, and test its gray prototype with real children before any launch.
What you get
- A scope document naming the platform's collected data and the reason for every field
- A plain gray prototype of the platform, tested with real children with their parents' consent
- A design for how a session ends, with no daily streaks and no random rewards
- A success indicator and a guardrail indicator agreed before launch
How we work
Every data field in the platform passes through our design laws, and before any launch we test a plain gray prototype with real children. We review every data field with the Data Minimisation Canvas, and review the whole platform against the Dawani Child-Safe Design framework.
When you need this service
Three situations that need a platform designed safe from the start
An existing platform whose collected data you want reviewed
The platform already works, and you want to know which data field is actually necessary and which can be dropped.
A platform you want parents, not only the child, to trust
The goal is a platform the child opens with their parents' trust, not one they hide from them.
How the service runs
Four stages, a gate after each
1 Understanding the goal
We start from the platform's goal as you describe it, and from the children who will use it, by age and context.
Gate: The goal leaves this stage once we agree on a specific aim for the platform, not a general description of its idea.
2 Written framing
We write the platform's scope: its data fields, the reason each stays, and what stays out of this version.
Gate: The framing leaves this stage once the platform's scope is written and agreed, instead of staying a verbal understanding.
3 Gray prototype and testing with children
We build a plain gray prototype of the platform, and real children try it with their parents' consent.
Gate: The prototype leaves this stage once the platform works with children as intended, not once the internal team is pleased with it.
4 Delivery and measurement
We deliver the platform, and measure it against the success indicator and the guardrail indicator agreed from the start.
Gate: This last stage is never left behind; the guardrail indicator stays with the platform for its whole life, not only at launch.
In scope and out of scope
| Aspect | In scope | Out of scope |
|---|---|---|
| The platform's design and data | Data fields and their reasons, how a session ends, and the gray prototype tested with real children. | Hosting the platform or its day-to-day technical operation, unless agreed within the proposal. |
| Legal compliance for data protection | Design questions that reduce what is collected in the first place, and questions we raise for your legal adviser. | A legal compliance certificate or a legal opinion; that stays with its own competent authority. |
| Timeline and price | A proposal built on your platform's own case once we understand it, naming what is out of scope as clearly as what is in it. | A time or price announced in advance, before the request is understood. |
| The outcome for the child | A success indicator and a guardrail indicator agreed before we start. | A guaranteed outcome for every child who uses the platform. |
Before you write to us
A tool, a post and a reference
Data Minimisation Canvas
A tool that runs in your browser: asks why each data field was collected, before you describe your platform to us.
Open the toolRetention without addiction
A post separating retention built on value from retention built on compulsion, with an alternative to each common addictive trick.
Read the postThe Dawani Child-Safe Design framework
The reference every platform we design is measured against, from its data fields to how a session ends.
Open the frameworkBefore a first conversation
Questions often asked about this service
Does reducing data mean the platform loses useful features?
Not necessarily. We first ask what actually breaks in the platform if we do not collect a specific field; if the answer is nothing, we drop it without losing a real feature.
Can the platform work without a personal account for the child?
In many cases yes, by tying it to a parent's account instead of a separate account for the child; we settle this during the written-framing stage.
What is the difference between a feature that encourages return and one that creates addiction?
A return-encouraging feature rewards a real value the child remembers; an addictive feature rewards continuing itself, regardless of its value.
Start here
Have a digital platform children will use?
Describe your situation plainly, and we will get back to you within a few working days.
Your path: government body
Your idea arrived.
A real person from the Dawani team will read it and reply within a few working days. Thank you for thinking about kids.
Updated: