Google explained Pulse to a press outlet before it explained it to Android users

The first thing anyone does with an app they do not remember installing is try to open it, and Pulse does not open. There is no app drawer entry. On a Pixel it sits at Settings > Google services > All services > Privacy & security > System services, several taps away from where a worried person starts looking ^[6]. The arrival mechanism is unglamorous: Google says system services update on their own schedule, separately from the OS, which is how a package turns up on a phone nobody touched ^[7].

Users type the name into a search box, land on a forum thread or a news post, and then either uninstall something unrelated or decide the phone is compromised. Support teams tell themselves users do something else: open the Play Store listing and read the data-safety section, which says Pulse may collect app information and performance data and does not share it with third parties ^[5]. That is a real answer to a question almost nobody knows to ask, and the same listing never says what the thing is for ^[9].

The 10 million figure will get more respect than it deserves. A listing a few days old passing 10 million downloads ^[2] reads like uptake, but Google's own account is that the service had been present since March and the update only made it visible in settings ^[3][4]. What the counter measures is Google's distribution, not a decision any user made ^[11]. An install base assembled that way records Google's shipping decision, not any user's demand.

What Pulse does is still secondhand. BGR reports the service is understood to help maintain Android and keep devices secure, and infers it likely watches battery drain, memory usage and CPU activity ^[12], which would sit alongside the crash, app-not-responding, wake-lock and memory tracking Android already performs ^[13]. For app teams the adjacency worth noting is the enforcement end: Google already shows which apps drain the battery and has said it will add labels and warnings for apps that consume excessive resources ^[14]. That telemetry, invisible to users now, is exactly what developers will have to answer for once those labels and warnings ship.

The Safety Core comparison holds for sequence, not substance. That one scanned for unwanted content, per BGR's account ^[10]; Pulse, on the reporting available, reads resource telemetry ^[12]. What the two share is the order of operations, and the order is what costs a support team its afternoon.

The next one of these comes down to four questions, and the answers decide how much of that afternoon you lose. Can a user locate the thing on their own device? For Pulse, yes, if they know the path ^[6]. Does the listing say what it does? No ^[9]. Does it declare what it collects? Yes ^[5]. Is there a clean way out? No, since Google warns that disabling system services can break features or cause other issues ^[8]. Pulse answers two of four ^[16].

Given that score, the sensible move is to leave it installed and put the effort into the written answer rather than the removal, and the tradeoff is plain: you are accepting a service whose purpose you know only through a statement to a reporter ^[3] in exchange for not breaking device features on a hunch ^[8]. If someone genuinely fears malware, BGR's steer is the right one, which is Play Protect, with Advanced Protection for people who want the tighter setting ^[15]. That two-of-four score is the baseline against which to judge the next silent push.