Private calendar integration

Calendar context for better bowling planning.

Miranda Ineko uses a read-only Google authorization to help authorized household users and The Dude review potential bowling events without giving the agent permission to change a calendar. Google’s authorization can technically read event details from calendars visible to Miranda’s account; the application enforces a single approved calendar and a smaller set of returned fields.

Read-only event details No Gmail access. No calendar writes. No sharing changes.

One explicit calendar, one bounded capability.

What is read

Event titles, descriptions, locations, dates, times, status, and update time from the explicitly mapped Potential Bowling Events calendar.

Why it is used

To help Miranda Ineko and The Dude identify and discuss possible bowling events with authorized users.

What is excluded

Gmail, contacts, Drive, attendees, organizers, attachments, conferencing, reminders, calendar administration, invitations, and every write operation.

Who can use it

This is a private, non-public assistant capability. Access is limited to separately authenticated household principals approved by the operator.

The calendar owner remains in control.

A calendar owner can end this calendar’s availability by removing its share with Miranda. The operator of Miranda’s authorizing Google account can separately revoke the application’s entire Google authorization. An authorized user may also ask the operator to disable internal access. Calendar text is treated as untrusted data and cannot authorize communications, purchases, registrations, or other external commitments.