com.sec.android.app.chromecustomizations Copy

Labelled "ChromeCustomizations" on the device and signed by the Samsung OEM keys that also sign the Android framework. It declares no permissions at all and has no user interface, which is the shape of a small partner customisation package rather than an app. Chrome on Android supports device "partner customisations": the browser reads a small set of values supplied by the device at startup rather than from any user setting. In current Chromium the reader is PartnerBrowserCustomizations, which supports a partner homepage ("homepage"), disabling bookmark editing ("disablebookmarksediting") and disabling Incognito mode ("disableincognitomode"). Partner bookmarks are supplied separately, by the partner bookmarks provider documented elsewhere on this site. Samsung publishes no documentation for this package, so while the name and the absence of permissions both point to it being Samsung's implementation of that customisation surface on Galaxy devices, we could not confirm that mapping from a Samsung or AOSP source, and we have not verified on hardware which values, if any, a given Galaxy build actually supplies. Version note: this is a Chrome-side mechanism rather than an Android platform one, so it moves with Chrome rather than with the Android release. The implementation has shifted within Chromium's own tree, and the values are now read through a delegate that a downstream build can replace, so behaviour can differ between Chrome builds. We could not source any change tied to a specific Android version. In our sample the package appears only on Samsung devices, across API levels 28 to 37. For Android Enterprise, EMM and kiosk use it has no enrolment or management role. It is worth knowing about for one reason: where a device does supply partner values, Chrome's homepage or its Incognito availability can differ from a stock device without any policy being applied, which is easy to mistake for a misapplied EMM configuration. Removing this package is not a documented way to control Chrome's behaviour, and because its effect on a given build is unverified, it is better tested on one device than assumed.

• PartnerBrowserCustomizations.java - Chromium source →
• Package provenance for com.sec.android.app.chromecustomizations - Android System App Database →

• Signed by the device maker's own signing key (Samsung), so it is an OEM preinstall, but 2 different certificates appear across the fleet, so OEMs ship their own builds of it. It also signs the Android framework, so it is a platform-level key on its device(s). Inferred from the certificate appearing only on Samsung devices (508 packages, 10196 observations).
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.