Provide On-Device Content Classification
SafetyCore supplies common infrastructure that compatible Android apps can use when they need to classify content for a safety feature. The classification happens on the device, so the service can return a result to the requesting feature without sending the classified content or result to Google. It is designed for privacy-preserving support rather than a standalone gallery, scanner, or messaging tool.
The service is active only when an integrated app connects to SafetyCore and specifically requests classification. That means its behavior depends on the feature calling it, the device build, and the content-safety capability being used. Users should judge the visible warning or setting in the calling app rather than expect a separate SafetyCore dashboard.
Power Sensitive Content Warnings in Google Messages
Google documents SafetyCore as the underlying technology for Sensitive Content Warnings in Google Messages. When that separate, optional feature is available and enabled, it can support warnings around potentially unwanted content before a user views or shares it. The purpose is to add a safety step without moving the image or classification result to Google servers.
Sensitive Content Warnings are not the same as a general-purpose message scanner that is always active. The requesting app decides when classification is needed, and feature availability can depend on Android version, device build, region, and rollout status. Review the relevant Messages safety setting to understand what is enabled on your phone.
Work as a System Component on Compatible Devices
SafetyCore is delivered as an Android system service rather than a conventional app with its own home screen. Compatible features can call it in the background when they need on-device classification, while Android settings can expose the component, package name, permissions, or update controls. This design keeps the service close to the operating system features that depend on it.
Google's documentation describes SafetyCore for Android 9 and later, but the downloadable package on this page lists Android 12L+ as its minimum. That difference matters when choosing a package variant: compatibility depends on the build, device architecture, and system delivery path. Do not treat a normal app launch as the expected way to use it.
Review Privacy, Permissions, and Update Choices
SafetyCore is intended to support privacy-preserving processing, but the complete experience also depends on the app that requests classification. Check the integrating app's safety settings, notification choices, and any explanation shown when a warning appears. If the component appears in Android settings, use that page to review its version, permissions, storage, and update options rather than looking for controls inside an independent interface.
Keeping the component current can matter when Android features rely on it, while disabling or removing system services may affect compatible protections on some devices. Before changing it, confirm your Android version, read the device manufacturer's guidance, and consider whether the relevant feature is enabled.
