Questions & disclosures

Not yet. The consumer app is not on sale, and there is nothing to download.

Institutional enquiries are open. Schools, organizations, networks and platforms can talk to us now about pilots and deployments.

The Android Consumer App is in testing with app blocking, screen-time schedules, web filtering and family location. Safety checks work with the permissions you enable and the content Android makes available.

RoseShield Messenger has controls for connections within Messenger. For iPhone and iPad, we’re developing app and web limits, screen-time controls and outgoing text protection through the RoseShield keyboard.

Channel partner agreements are signed in South Africa, Kenya, Uganda, Cameroon and Ghana, with a cooperation framework in the United Arab Emirates.

The first two school pilots are signed in Kampala, and RoseShield Messenger is entering broad pilot testing with a major international children’s organization.

Those are agreements and pilots beginning, not results to report.

Not yet published. Until it is, treat performance claims on this site as our claims rather than verified evidence.

When findings exist, they will be published by harm category, threshold and model version — including where the engine underperformed.

No independent certification today. We will not suggest otherwise, and your technical team will establish it either way.

Expanding the programs already agreed, publishing findings from them, and consumer availability.

You see flagged safety concerns and the reasons behind them. Your family settings determine what content and context are shared for review, helping you understand the concern and decide how to respond.

Guardian alerts can tell you when a safety concern needs attention, according to your settings. In apps and devices with RoseShield built in, incoming checks can hold harmful content before your child sees it.

An unsafe outgoing message can also be paused in an app with RoseShield built in, or while the RoseShield keyboard is active. A plain explanation gives your child a moment to reconsider before sending. Alert delivery needs an internet connection.

A flagged concern, its risk rating and the reason it was flagged. Content and context can be included where your family or safeguarding settings call for them, helping the designated adult understand the concern.

RoseShield is designed to be part of an open family conversation. Explain the controls you choose, how safety prompts work and when an adult may receive an alert.

RoseShield checks content on the device first, using the cloud when deeper analysis or Guardian support is needed. Apps with the SDK share content for local checks on supported builds. The API route sends the content supplied by the app to the analysis service.

Device checks use the content Android or a RoseShield-integrated build makes available. The information shared for analysis, alerts and review follows the deployment’s settings.

Your rules guide RoseShield’s response. Set safety preferences and thresholds; RoseShield uses them to block, warn and alert. You decide how to follow up.

In a school or organization, the designated safeguarding authority sets the policy and decides how to respond to concerns and meet reporting obligations.

RoseShield looks for signs of grooming, sextortion, bullying and self-harm. The SDK checks text, images, voice and video your app shares with it. Android and Core use the content their device access allows.

Router is in development for website filtering and network rules. It adds network protection alongside app and device content checks.

Supported on-device safety checks can keep working offline. An internet connection delivers Guardian alerts, updated settings and model updates, and supports configured cloud analysis. API analysis also needs a connection to the service.

Our demonstration shows examples of harmful text detected in English, Swahili and French. Talk to us about the languages and content that matter to your family or community, and the evaluation options available.

It will. The question that matters is what a mistake costs.

A mistaken low-risk pause has limited consequences. Your child sees a brief explanation and can rewrite the message.

A mistaken adult alert has much greater consequences, so the threshold for notifying an adult is set much higher.

On lower-risk interventions, yes, and that is a setting you control. As they get older you can let more through, keeping firm limits for serious risks.

Hard limits remain for serious risks at every age.

Independent performance findings have not yet been published. A useful evaluation looks at the content, language, type of risk and response threshold involved, including missed concerns and mistaken flags. Talk to us about evaluating RoseShield in your setting.

RoseShield provides safety checks, controls and alerts. It supports parents and safeguarding teams; it does not replace them. Your settings guide automatic blocks, warnings and alerts, while you decide how to follow up and whether to make a report.

Support resources may be linked from alerts. If a child is in immediate danger, contact local emergency services.

Choose protection for the setting. The SDK checks content within the app that integrates it. Core brings deeper protection to supported RoseShield-integrated Android and AOSP builds. The Android Consumer App uses enabled permissions for device controls and accessible content checks.

For iPhone and iPad, protection is in development around app and web limits, screen-time controls and the RoseShield keyboard. The keyboard can check outgoing text while active; ordinary iOS apps cannot inspect every incoming message inside other apps.

Router is in development for website filtering and network rules on traffic routed through the school or home network. Device protection can extend safety tools beyond that network. A school’s safeguarding responsibility continues beyond its network coverage.

In an institutional deployment the customer is the controller and ChildSafe.dev is the processor. The operator agreement comes as a schedule to the contract.

Retention, residency and sub-processor disclosure are set per deployment.

Contact us with questions about your data or to request deletion. We’ll explain what we hold and the next steps for your request.

Where a school or organization controls the data, we pass the request to them. Their safeguarding records follow their retention policy and applicable requirements. We do not sell data or add enquirers to marketing lists.

No. What constitutes grooming, exploitation or a reportable offense is a matter for the law where you are. The engine detects and scores; your authority decides.