Privacy Policy

Google data accessed

The integration requests only the Google OAuth scope calendar.events.readonly. At the Google authorization layer, this scope can technically view event details across all calendars accessible to Miranda’s authorizing Google account. The application adds a narrower, independently enforced boundary: it sends event-list requests only for the single protected calendar mapped as Potential Bowling Events and returns only a limited field projection.

The normalized result may contain an event title, description, location, start and end, all-day status, event status, and provider update time. The application does not request or use Gmail, Contacts, Drive, calendar-list, sharing, access-control, event-write, invitation, notification, attachment, conferencing, or reminder capabilities. Although Google’s underlying event objects may contain attendee and organizer information, the application’s fixed request and projection exclude those fields from returned results.

How the data is used

Event information is used only to help authorized users and the internal bowling specialist known as The Dude review, discuss, and plan around potential bowling events. A locally hosted AI model processes requested event data to generate the user-facing answer or bowling-task result. Google user data is not sent to a third-party AI model and is not used to train, retrain, or improve a generalized AI or machine-learning model.

Calendar content cannot grant authority to send messages, register for events, make purchases, alter calendars, or create external commitments.

Google API Services User Data Policy

Miranda Ineko Calendar Access’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Storage and retention

The Google OAuth credential is retained in a protected file on the operator's self-hosted system until it is revoked or replaced. The calendar broker processes event details on demand and does not maintain a separate event cache or event database.

Relevant calendar results or excerpts may appear in the self-hosted conversation or task records of authorized users when needed to answer a request. Those records have no promised automatic expiration and remain until an authorized user or the operator deletes the record. Security audit records contain the authenticated internal principal name and class, logical calendar name, requested time window, result count, and outcome; they do not contain Google calendar identifiers, Google event identifiers, or event text. Audit records remain with the self-hosted operational logs until host log rotation or operator deletion.

Disclosure and sale

Google user data is not sold, rented, used for advertising, or disclosed to data brokers. It is made available only to the operator, authorized household users, and the operator's self-hosted Miranda Ineko components as necessary to provide the requested calendar assistance.

Security

The integration uses separate authenticated internal principals, a fixed calendar mapping, bounded query windows, a restricted Google-only network path, protected credential files, and a projection that removes provider identifiers and unnecessary fields. Event text is treated as untrusted external data.

Your choices

A calendar owner can stop this calendar from being visible to Miranda by removing its calendar share. Only the operator of Miranda’s authorizing Google account can revoke the application’s entire OAuth grant through Google Account permissions. Revocation stops future Google access but does not automatically erase excerpts already retained in local conversation, task, or operational records.

An authorized user may request deletion by emailing the contact address below and identifying the conversation, task, or date range involved. The operator will review and delete identified local conversation and task records under the operator’s control; operational audit records will be deleted where technically feasible or will expire through host log rotation.

Contact

Questions or privacy requests may be sent to mirandaineko@gmail.com.