RoseShield reads text, images and voice on the device, scores what it finds, acts on the thresholds you set, and hands anything serious to a person. What changes between products is where it runs and who the responsible adult is — never the detection itself.
RoseShield is built into the phone itself, so it is working the first time your child turns it on. Messages, photos, voice notes, video and the web — whatever they open, it is already there.
Nothing to download, nothing to set up, and no app your child can delete. This is the version phone makers and mobile networks put on the handset before it ever reaches a family.
Built to help you meet the obligations arriving in every major market at once, rather than one jurisdiction at a time.
Download it at launch, set the limits you want, and that is the setup done. Routine protection stays between your child, their device and you. Serious or uncertain cases follow the escalation rules you set.
Screen time, app blocking, friend approval and family location are all included — alongside RoseShield’s on-device harm detection.
A place for children to talk where the engine sees each message, image, call and voice note in the moment — rather than a report about it three days later.
Runs on-device inside an application you already ship. No platform fight, no new distribution problem, and a sandbox to try before you commit to anything.
A safety team is expensive. Most teams shipping a product for young people cannot fund one, and are facing the same obligations as the platforms that can.
One integration gives you detection, scoring and a review path — built to help you meet what is arriving in every major market at once.
Runs across the network an organization already operates, alongside the systems it already has. Deploy it on one part of the estate or all of it.
Nothing leaves the building. The appliance runs locally, around the clock, with no cloud dependency.
For schools & organizations →
Courses, groups, messaging and events in one place, for organizations that need young people to connect somewhere the engine can see. Organizations that need a complete protected learning and social environment typically use Campus.
The safeguarding view sits beside the learning view rather than in a separate system, so the person responsible for a child is looking at one screen, not three.
Router covers the network an organization runs, including every device connected to it. The Consumer App covers a phone a parent provides. Core and the SDK cover a device or a product a platform ships. Each deployment matches a different scope of responsibility.
Matching the deployment to the responsibility keeps the coverage and the accountability in the same place.
Most people arrive knowing the risk they need to close, not the product name. Describe the situation and we will tell you which piece fits — or that none of them does.
Talk to us