Encryption at rest [1] protects against someone who has access to the
encrypted bytes from not being able to decrypt it. That is, if someone got the raw bytes off our storage somehow, it's not useful to them. If someone has access to your
account, then the storage system can't tell if it's you or not.
Data in Datastore (and Firestore fwiw, that needs an update) is encrypted at rest, and today's paper discusses how it's also encrypted in transit between your app and the service. I don't believe Datastore supports Customer Supplied Encryption Keys [2] (yet) but that lets you have a key that even Google can't decrypt the data without you providing it. That's a pretty good way to separate permission from keys.
Disclosure: I work on Google Cloud.
[1] https://cloud.google.com/security/encryption-at-rest/default...
[2] https://cloud.google.com/security/encryption-at-rest/custome...