com.samsung.android.service.tagservice Copy

A Samsung background service whose English label is "Tags", localised as "Tag", "Tags" or "Etykiety" elsewhere. It is signed by a Samsung OEM key that also signs the framework package, has no launcher entry, and is not user-facing in any observation on this site. The label invites confusion with the NFC tag viewers documented separately here, com.android.apps.tag and com.google.android.tag, but this is a different thing: it declares no NFC permission at all, and nothing in its permission set touches the NFC stack. The permissions this site records against it instead describe content tagging and indexing, bearing in mind that the site records the permissions a package requests rather than which package declares them. The list includes com.samsung.cmh.data.READ and WRITE and com.samsung.android.providers.media.CMH, which reach Samsung's Content Management Hub media database; com.samsung.android.provider.indexing.permission.ACCESS_PROVIDER together with the platform GLOBAL_SEARCH permission; com.samsung.android.bixby.service.bixbysearch.permission.BIXBY_SEARCH; OCR service access; read access to Samsung Notes and to the Gallery provider; and READ_MEDIA_IMAGES. It also includes a large block of binds into Samsung's on-device AI stack, among them com.samsung.android.aicore and the scs.ai image, text and search services. This site aggregates permissions across observations rather than per build, so the builds in which those AI binds appear cannot be established from it. Samsung documents the user-visible end of this without naming a package: its Gallery support pages state that "The app organizes your photos and videos into categories such as people, locations, and objects" and that "You can search for media using specific keywords or tags associated with the content". Whether this package is the tagging engine behind Gallery search, behind wider system search, or behind both could not be sourced, so treat the connection as our reading of its permissions. Version note: Samsung's Common Criteria mode application lists record "Tags" at version 1.5.25 on the Galaxy Note20 Ultra 5G for Android 10 and 1.6.16.0 on the Galaxy S21 Ultra 5G for Android 11, so the package long predates Samsung's current AI features. This site records it at API 33 to 37 (Android 13 to 17) at versions 6.0.00.10 to 6.0.00.50, with up to 71 declared permissions. The AI service binds listed above suggest integration with Samsung's on-device AI stack; whether that represents a genuine broadening of the package's role since the Android 10 and 11 versions above, and in which release it happened, could not be sourced, and Samsung publishes no changelog for it. For Android Enterprise, EMM and kiosk use it has no enrolment or policy role and presents no user interface. The privacy question is worth noting on company-owned devices: a service that indexes images, notes and other content and can bind on-device AI services is processing user content, although every permission above is local and we found no evidence of off-device transfer. Disabling it would be expected to degrade tag-based and content search in Samsung apps rather than break them, which may be an acceptable trade-off on kiosks and single-purpose devices that do not depend on Samsung content search. On general-purpose handsets the search regression is the cost, and other dependencies are unverified, so test on one device first.

• Samsung Gallery: Using the search function - Samsung Gulf →
• Galaxy Note20 Ultra 5G (SM-N986B, Android 10) Common Criteria mode application list - Samsung Knox Documentation →
• Galaxy S21 Ultra 5G (SM-G998B, Android 11) Common Criteria mode application list - Samsung Knox Documentation →
• NFC basics: the tag dispatch system - Android Developers →
• Package provenance for com.samsung.android.service.tagservice - Android System App Database →

• Signed by the device maker's own signing key (Samsung), so it is an OEM preinstall, and that single certificate is consistent across all 17 device profiles. 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).
• Its largest observed manifest declares 71 permissions: 4 runtime (user-granted), 2 signature or system-level, 4 install-time and 61 vendor or uncatalogued.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.