AgentM
I just checked, I sideloaded a temporary root, and set App Manager with root permissions via KernelSU so I could see the signatures of all Sandboxed Google Play apps and the UID's of the apps. This is what they are really installed as:
Google Play Services: UID: 10252 (shared /w Google Services Framework) 3 Signatures signed by Google Inc. NOT by my system certificates, which are signed by me, Tryptamine, or GrapheneOS (my own build. On regular releases by GrapheneOS ALL system apps are signed only by GrapheneOS. Same signatures and UID for Google Services Framework {Shared UID}).
Google Play Store: UID 10251 3 Signatures signed by Google Inc. Same as above.
System apps on GrapheneOS (that have full system permissions) have UID of 1000. Root apps have UID 0. I have NEVER seen a single app in an official GrapheneOS build, or my own build with UID 0, full root privileges! It would be unnecessary and giving too much privilege to any one app. Even the base "GrapheneOS" app is only "1000!"
Most system apps in GrapheneOS also may be signed by my build keys (release key, not the higher trust platform key), but they don't have UID 1000. They don't need full system permissions, so they don't get them! Only very few system apps need full system permissions. This is a sign that GrapheneOS is working on the principal of least privilege. Which is a great thing!!
Yes, also I can see the SELinux policy is also not the same for the Sandboxed Google Apps as it is for the system apps:
System:
platform:privapp:targetSdkVersion=34:partition=system:complete
Gapps:
default:targetSdkVersion=34:complete
Time to go back to my nice & safe unrooted GrapheneOS!