How Reploy uses Google user data

The permissions we ask for

When you connect Google Calendar, Google asks you to approve a specific list of permissions. Reploy requests these and nothing else:

• See your calendars and events (calendar.readonly) — so Reploy knows when you are already busy.
• Create and change events (calendar.events) — so a booking a customer makes appears in your calendar, and moves or disappears when the booking changes.
• Your email address (userinfo.email) — so the app can show you which Google account is connected.

What each one is actually used for

Checking when you are free

Before Reploy offers a customer a time, it reads the times you are already booked so it never gives away a slot you cannot do. It uses the times only. The titles, guests, notes and locations of your existing events are not read for any other purpose, are not shown to customers, and are not stored by Reploy.

Creating your bookings

When a customer books, Reploy writes that appointment to your calendar, and updates or removes it if the booking is later changed or cancelled. Reploy only ever touches events it created itself.

What we never do

• We do not sell your Google data.
• We do not use it for advertising, or share it with advertisers.
• We do not use it to train AI models, ours or anyone else's.
• We do not let a human read it, except where you ask us to for support.

Limited Use

Reploy's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Turning it off

Disconnect Google Calendar at any time in Reploy under Settings, or revoke access directly from your Google account permissions. When you disconnect, Reploy deletes the tokens it holds for your account. Events already written to your calendar stay in your calendar, under your control, and Reploy keeps managing your bookings in its own calendar as normal.

Questions

Email info@reploysolutions.com. Our full Privacy Policy covers everything else we handle.