Privacy Policy

Account data

When you create an account, we collect your email address, name, company name, and professional role. This data is used to create and manage your account and to communicate with you about the Service.

Usage data

We collect data about how you use the Service: pages visited, features used, session duration, errors encountered, and in-product interactions. This is used for product improvement and support.

Payment data

Payment processing is handled by our payment processor. Mirvo does not store or have access to your full card details — we only receive a payment confirmation, subscription status, and billing metadata.

Communications data

We retain the content of support messages you send us via email or in-app, as well as automated notifications we send to you, for support and compliance purposes.

Cookie data

See our Cookie Policy for full details on what cookies are set and why.

Google Calendar data

This applies only if you connect a Google account to Mirvo, from Settings, Google Calendar. It describes how Mirvo accesses, uses, stores, shares and deletes the Google user data it receives.

What Mirvo accesses. When you connect, Mirvo asks Google for three permissions: your basic account identity (your Google account identifier and email address), read-only access to the list of your calendars, and access to view and edit the events of your calendars.

How Mirvo uses it. Your account identity is used to show which Google account is connected and to keep the connection tied to that account. Your list of calendars is shown to you so that you can choose which calendars block your availability and which single calendar receives your bookings. Mirvo regularly reads the events of the calendars you chose, over a limited period (from one day in the past to about 120 days ahead), so that your booking page does not offer times when you are busy. When a prospect confirms a meeting through your booking page, Mirvo creates an event at the meeting time in the calendar you chose, titled with the prospect's name and company when they gave them, or with a neutral title otherwise (never their email address). If you later move or cancel that meeting in Mirvo, Mirvo moves or deletes that event in the calendar where it created it. Mirvo does not add guests to these events, does not send Google invitations, and never changes an event it did not create.

What Mirvo stores. An authorization token, encrypted at rest; your Google account identifier, email address and the permissions you granted; the identifier, name and your access level of each of your calendars; and, for the calendars you chose, the start time, end time, busy or free status and technical identifier of each event in the synced period. Each synchronization replaces the previous set. For meetings that Mirvo wrote to your calendar, Mirvo keeps the identifier of the Google event and of the calendar, and the sync status. Mirvo does not store the title, description, location, guests or any other content of your Google Calendar events. This data is stored in Mirvo's database, operated by the sub-processors listed in our Data Processing Addendum.

Sharing. Mirvo does not sell Google user data, does not use it for advertising, does not use it to create, train or improve artificial intelligence models, and does not transfer it to third parties, except to the sub-processors that host and operate the Service, for security purposes, or to comply with the law. Mirvo staff access your Google user data only when you ask us to help you, when it is necessary for security (for example to investigate abuse), or to comply with the law.

Disconnecting and deletion. You can disconnect at any time from Settings, Google Calendar. Mirvo then asks Google to revoke its access and deletes the authorization token, the list of your calendars and all synced busy times. The sync status of meetings already written to your calendar is kept with those meetings in Mirvo, and the events already created stay in your Google Calendar unless you delete them there. When you delete your Mirvo account, Mirvo does the same for the workspaces you own. If you remove Mirvo's access from your Google Account instead, Mirvo can no longer read or write your calendars, and the data above is kept until you disconnect in Mirvo or delete your account. Database backups are kept as described in section 7.

Limited Use. Mirvo'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.