Calendar, full access
Reads and edits every event in the person's calendars.
In one line
Can see, add and change every event in all your calendars once you allow full access
Reads and edits every event in the person's calendars.
Calendars show meetings, attendees, travel, doctor visits and routines.
What it can and can't do
What the user does: You tap Allow Full Access when the app asks about your calendar
It can
- List meetings, places and attendees
- Change or delete events that already exist
- Add new events
- Check your calendar again later without asking each time
It cannot
- Reach any event before you tap Allow Full Access
- Use the old single request on iPhone; iOS 17 split it
- Keep access after you turn it off in Settings
How it differs between platforms: iPhone shows Allow Full Access or Don't Allow; Android shows Allow or Don't allow.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Supported |
| First version | Android 6.0 (API 23) | iOS 17 |
| Permission or entitlement | READ_CALENDAR, WRITE_CALENDAR | NSCalendarsFullAccessUsageDescription (iOS 17); NSCalendarsUsageDescription earlier |
| Protection level | dangerous | prompt |
| How access is granted | prompt | prompt |
| What the user sees | Allow or Don't allow | Allow Full Access, Don't Allow |
| How long it lasts | Until revoked; auto-reset after months unused | Until revoked |
| How to take it back | Settings > Apps > Permissions > Calendar | Settings > Privacy & Security > Calendars |
| Store policy | Play: sensitive data policy | App Review 5.1.1 |
| API | CalendarContract | EKEventStore.requestFullAccessToEvents |
| Notes | None | requestAccess(to:) is deprecated in iOS 17; read and write are split |
Data you get
What comes back: Events
Shape: list
How often: on request, EKEventStoreChanged notification
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
events | list | events | 0 to thousands | to the minute |
Technical limits
- iOS 17 and later require the new keys; old key stops working for new targets
The story
What it is
Lets the app read and change every event in all your calendars.
For you
The prompt says the app wants full access to your calendar. If you allow it, the app can see meetings, locations and guests, and edit or delete them.
For makers
Full access lets a smart assistant plan your day, find clashes and join calls. It is powerful and sensitive, since the calendar shows where you are, who you meet and your appointments.
Where you see it
| Type | Example | Apps |
|---|---|---|
| productivity | A meeting assistant joins your calls and writes notes from your calendar. | Zoom, Otter.ai |
| productivity | A day planner shows calendar and tasks in one view. | Fantastical |
| travel | A travel app finds flights that fit between meetings. | None named |
| health | A wellness app finds time for breaks. | None named |
| analytics | A work tool measures how much time you spend in meetings. | None named |
| enterprise | A sales app logs customer meetings automatically. | Salesforce |
| ads | An ad SDK could read events to guess interests, which store policies forbid. | None named |
Risks
- Reveals where you are and who you meet
- Edits or deletes events
- Health visits visible
Android and iPhone in short
- Android: Android has a calendar permission group for read and write.
- iPhone: iOS 17 split read and write, and the older request call is deprecated.
Good uses and abuse
Legitimate uses
- Scheduling
- Meeting assistants
Known abuse
- Inferring locations and relationships
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 2 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2015-10, Android 6.0 (API 23): Runtime calendar permission
- 2023-09, iPhone iOS 17: Full access key and write-only option introduced
Related capabilities
Related
- Calendar, write only. Can add events to your calendar without seeing anything already in it
Sources
How well checked: Based on official documentation.