System Daemons Running with Zero Screen Time – iPhone Sensor Access While Disabled

I’m reporting something serious and I want clarity—not gaslighting.

My iPhone 16 Pro Max (replaced new by Apple 3 months ago) is showing multiple internal Apple system services running—AuthKitUIService, SIMSetupUIService, AuthenticationServicesUI, etc.—with 0 seconds of screen time permitted. I don’t believe 0 seconds is even a valid value, but that’s what I’ve set, and these processes are still running daily for up to 30–50 minutes.

Examples:

• AuthKitUIService: 51m
• SIMSetupUIService: 43m
• AppProtectionUIHost, BusinessChatViewService: active for unknown reasons
• Screen Time title: replaced with a blank (“ ”)—possibly spoofed
• Screen Time logs show app or setting usage across 24 hours—even when the phone is untouched
• Not logged into iCloud, no other devices signed in, no app sharing enabled

I have screenshots and logs, so please keep responses constructive.

Sensor Access logs show the Camera, Microphone, Contacts, and Messages were accessed repeatedly, even though “Sensor & Usage Data” is disabled.

Apps like ShortcutsActions and Safari accessed sensors within the hour—I don’t use Shortcuts at all.

Additional context:

My brand new Mac Pro M4 (3 weeks old) has:

• Never connected to iCloud
• Wi-Fi, Bluetooth, and Ethernet disabled
• Yet it’s still streaming data and running background Apple daemons:
• bluetoothd, sharingd, remoted, mediaremoted, universalaccess, coreduetd — confirmed via ps aux.

I don’t share data. I’ve changed passwords. I use security keys.

None of it stops this behavior.

Device status:

• Factory-reset iPhone and MacPro
• No jailbreak
• No MDM
• Verizon carrier for iPhone

Open questions:

• How are these services executing without user initiation?

• Why does the App Privacy Report contradict system sensor settings?

• Why are Apple daemons running persistently, with no UI trace or user-facing control?

If this is expected behavior, I want engineering-level documentation.

If it’s not, then Apple’s reporting channels are compromised, and privacy expectations have failed.