Trust and safety
Trust needs clear promises, accountable operations and visible limits.
This centre explains what families should be able to expect, which risks require active ownership and which safeguards remain design commitments under validation.
What families may expect
Household control, truthful information and adult responsibility are the starting conditions.
A family should understand why an opportunity is shown, where its facts came from, what will be shared before contact and how to correct or withdraw information. Children should not need public profiles to participate.
Commercial payment, institutional interest or product engagement must not silently change relevance, visibility or family choice.
Accountable operation
A safety feature is credible only when someone owns the response behind it.
Future operation requires named responsibility for identity, provider facts, privacy requests, reporting, blocking, safeguarding concerns, marketplace disputes, security incidents and assisted-answer errors.
Each route needs intake, priority rules, response expectations, escalation, correction and an appeal path where appropriate. A badge or report button cannot replace staffed procedures.
Current status and escalation
The site separates principles being tested from controls that are ready to operate.
Huddle currently presents a prototype and an operating design under specialist, legal and technical review. It does not claim a safety certification, completed privacy assessment, staffed moderation service or proven outcome.
Questions about project conduct, privacy or accessibility should use the relevant contact route. Urgent health, emergency, child-protection or statutory matters belong with the authorised local service.
Household permissions
Adults control household context; children are beneficiaries, not targets.
A future household model must show who can create, view, change and share each part of family context. Co-parents and caregivers may have different responsibilities; one adult should not silently gain control over another adult’s information, and a child should not need a public identity to join an activity.
Age assurance, guardian authority and consent should be proportionate to the action. Huddle must not sell child attention, create public popularity measures, infer vulnerability for targeting or open default direct messaging between unknown adults and children.
Location and communication
Useful coordination should not expose where a child is or create an unsafe contact channel.
Location should be limited to what is needed for discovery, travel or arrival and should not become continuous tracking. Exact household, school, routine or live child location requires a separate necessity test, permission model, retention rule and safety review.
Messaging and user-contributed content require clear participants, adult-first defaults, reporting, blocking, moderation scope, evidence preservation and escalation. A report button is not enough without trained owners, response priorities and a route for urgent safeguarding concerns.
Incidents and maturity gates
Trust is measured by prevention, response and learning — not by a badge.
Before operation, Huddle needs severity levels, on-call ownership, containment, participant communication, evidence handling, correction, appeal, regulator or authority routes where required and a post-incident review. The process must cover privacy, security, safeguarding, provider facts, commerce and assisted-answer failures.
Readiness should use explicit gates such as unresolved high-severity risks, response coverage, report handling, data-rights completion, provider-data freshness and safety-test results. Metrics support a decision to proceed, narrow, pause or stop; they do not prove that harm is impossible.