Google API Privacy Policy

Last updated: July 8, 2026

This policy explains how Mirando S.A.S. ("Mirando", "we", "us", or "our") handles Google user data for the optional Google Calendar integration in the Mirando web application available at mirando.ai.

Mirando is a real-estate platform for real-estate professionals. Connecting Google Calendar is optional. If you do not connect Google Calendar, Mirando does not access Google Calendar data from your Google account.

Google Limited Use disclosure

Mirando'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.

Mirando uses Google user data only to provide or improve user-facing Google Calendar, scheduling, and follow-up features that are visible in Mirando and requested by you. Those Calendar features are the complete use of Google user data in Mirando.

Google user data Mirando accesses

Mirando accesses Google user data only after you connect your Google account through Google's OAuth authorization flow. Mirando requests only the Google OAuth scopes needed for the Calendar integration:

Account identification

• Email address and OpenID (userinfo.email, openid) are used only to identify the Google account you connected and associate that connection with your Mirando account.

Google Calendar

• Read your calendars and events (calendar.readonly) is used to show your calendars, availability, agenda, and upcoming appointments in Mirando.
• Create, edit, and delete events on calendars you own (calendar.events.owned) is used to schedule, update, or remove calendar events when you request that action in Mirando.

How Mirando uses Google user data

Mirando uses Google user data only to:

• identify the Google account connected to your Mirando account;
• display your calendars, availability, agenda, and upcoming appointments inside Mirando;
• create, update, or remove calendar events on calendars you own when you request that action;
• send calendar invitations or event update notices when you request that behavior; and
• keep recent calendar changes reflected in Mirando so you can see meeting history, avoid duplicate processing, and follow up from the same Mirando interface.

These uses are part of Mirando's user-facing Calendar, scheduling, and follow-up functionality.

Artificial intelligence and Google user data

Some of the user-facing Calendar, scheduling, and follow-up features described above are powered by artificial intelligence. When you use one of those features, limited Google Calendar data (for example, event titles, dates and times, locations, and attendees) may be processed by Google's Gemini AI models, operated by Google, solely as input needed to produce the result you requested — for example, when Mirando's assistant shows your agenda, schedules an appointment you asked for, or associates a calendar event with one of your clients.

• Mirando does not use Google user data to develop, improve, or train generalized (non-personalized) artificial intelligence or machine learning models.
• Google user data is used with AI models only as real-time input to provide the user-facing feature you requested, never as training material.
• Mirando does not transfer Google user data to any other third-party AI tools. The AI models Mirando uses do not retain Google user data or use it to train models.

How Mirando stores Google user data

Mirando stores only the Google user data needed for the Calendar integration. This may include:

• OAuth access tokens, encrypted refresh tokens, granted scopes, and the connected Google account email;
• calendar IDs, Google event IDs, iCalUIDs, update tokens, update timestamps, and links between Mirando records and Google Calendar events; and
• event details needed for Calendar, scheduling, and follow-up features, such as title, description, start and end times, location, attendees, organizer, response status, recurrence, event status, and related event links or attachments when present.

How Mirando protects Google user data

Refresh tokens are encrypted at rest using AES-256-GCM. Mirando uses HTTPS, production access controls, and restricted employee access to protect Google user data.

Authorized Mirando personnel may access Google user data only when needed to keep the Calendar integration working, respond to a request from you, or meet a legal obligation.

How Mirando discloses Google user data

Mirando does not disclose Google user data except to service providers that process it on Mirando's behalf for the user-facing Calendar, scheduling, and follow-up features described in this policy.

Service providers may process Google user data only under Mirando's instructions and only for those user-facing features.

How to revoke access and delete data

You can remove Mirando's access to your Google data at any time:

• In Mirando, go to Settings > Integrations and disconnect Google Calendar. When you disconnect, Mirando deletes stored Google OAuth tokens, revokes the corresponding Google access where possible, and stops future Calendar access.
• In your Google Account, visit myaccount.google.com/permissions and remove Mirando's access.

Calendar-derived scheduling, follow-up, or reminder records already created in Mirando may remain in your Mirando account so the user-facing history and reminders continue to work. To request deletion of those records or any other personal data Mirando holds, email soporte@mirando.ai.

Changes to this policy

Mirando may update this policy from time to time. We will post any changes on this page and update the "Last updated" date above.

Contact

If you have questions about this policy or how Mirando handles Google user data, email soporte@mirando.ai.

Mirando S.A.S. (RUT: 220641810013), Uruguay.