Your Google Data
PokeeBee requests three Google OAuth scopes, and all three are read-only. This page explains what each one reads, why PokeeBee needs it, and why it is the narrowest scope available for the feature it powers.
What Google data does PokeeBee access?
PokeeBee accesses three Google scopes —contacts.readonly, contacts.other.readonlyand calendar.readonly — and every one of them is read-only: PokeeBee's access to your Google account never writes anything through a Google API.
| Scope | What it reads | What PokeeBee does with it |
|---|---|---|
contacts.readonly | Names, birthdays, photos of your contacts | Finds upcoming occasions; photos are cached on your device only and never uploaded |
contacts.other.readonly | Names of people you have interacted with but not saved | Same, so someone you emailed but never saved still gets a reminder |
calendar.readonly | Event titles, dates, calendar names | Finds occasions; you choose which calendars count |
Why does PokeeBee ask for contacts.readonly instead of full contacts access?
Because reading names, birthdays and photos is all the reminder feature needs. PokeeBee never creates, edits or deletes a contact, so it has no use for write access and never requests it —contacts.readonly is the narrowest scope Google offers that can still read a birthday off a saved contact.
Why does PokeeBee also need contacts.other.readonly?
Because "Other contacts" — people you have emailed or met but never saved to your address book — live outside the scope above; without contacts.other.readonly those people would never get a reminder even though you clearly know them. It is read-only, and it is the only scope Google exposes for that data at all, so there is no narrower option.
Why does PokeeBee need calendar.readonly?
Because finding an occasion means reading event titles, dates and calendar names, and calendar.readonly is the read-only version of Google's calendar scope. PokeeBee requests it instead of a scope that could also write, because it never writes an event through Google's API — you choose which calendars count.
Does PokeeBee ever write to my Google Calendar?
No — not through Google's API. Calendar write-back is a separate, opt-in permission that PokeeBee asks your phone's operating system for, not Google: when you turn it on, PokeeBee uses your device's own calendar store to add the occasions you created in PokeeBee to a calendar you choose. This goes through the device's own calendar store, not through Google's API, and all three Google scopes above stay read-only throughout.
If write-back is device-only, why does my Google Calendar sometimes show the event?
Because your phone's operating system, not PokeeBee, is what pushes it there. If the calendar you choose for write-back happens to be one your phone already keeps synced with Google, the OS syncs that new event up the same way it syncs everything else on that calendar. It can look, from your side, like PokeeBee wrote to Google Calendar; what actually happened is that the OS synced a calendar that was already syncing. PokeeBee's own Google API access stays read-only throughout.
Does PokeeBee use my Google data for anything besides reminders?
No. PokeeBee's use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. None of it is sold, and none of it is used for advertising.
What happens to my contact photos?
They stay on your device — contact photos are cached on your device only and never uploaded.
Where can I read the full privacy policy?
The complete policy, including what PokeeBee stores and for how long, is at pokeebee.app/privacy.