You'll notice
Useful3 Signal3
More accounts now qualify for memory sync through an extra OAuth-scope path.
What's wrong with this entry?
Anonymous. No account, no email.
What
The check that decides whether memory sync is available gained an extra way to qualify: an account on a first-party base URL with the right OAuth scopes now passes even if the previous conditions do not.
Details
- Still requires the
allow_memory_synccompliance permission, which is denied under HIPAA and zero-data-retention modes. - The added branch is one of three alternatives; exactly which accounts the third branch admits is not fully determined by the code.
Evidence
allow_memory_sync
Strings lifted out of the shipped bundle, so the claim above can be checked against them.