Explain before asking
Permissions should be presented with a clear connection to the feature they support.
Privacy by design
Family guidance works better when everyone understands how it works.
Kidder is designed around understandable permissions, purposeful access, parent choice, and respect for a child’s growing independence.
Privacy by design
Principles that shape the product experience.
These principles describe Kidder’s product direction. Formal policies remain the source for specific legal and data-handling terms.
Use what is necessary
Access should be tied to a specific product purpose—not requested without context.
Keep families in control
Parents should be able to review settings and make informed choices as needs change.
The minimum-necessary principle
Access should follow purpose, not precede it.
Kidder’s product experience should ask only for access connected to an enabled capability, explain why it matters, and avoid presenting broad access as a vague requirement.
Respect for children
Safety should support trust, not replace it.
Kidder is intended to help parents guide and protect. Screen Time, App Usage, and recent activity should provide context for conversation, age-appropriate independence, and thoughtful family boundaries.
- Use activity summaries as context, not a score
- Explain family expectations clearly
- Review Rules as children grow
Choice for parents
Settings should stay understandable over time.
Parents should be able to revisit protection choices, understand what a setting affects, and decide what continues to fit their family.
- Review permissions during setup
- Adjust routines and rules later
- Use formal request paths when needed
Formal information & choices