Google Calendar integration
Google Calendar integration
How the Google Calendar integration in the booking systems kveo builds works, and which Google data it uses.
What the integration does
Some of the booking systems kveo builds for businesses, currently the Bowlit booking system (bowlit.no), can add each booking to the business’s Google Calendar. When a booking is made on the website, the system creates an event in the calendar the administrator chose. If the booking changes, the event is updated, and if it is cancelled or deleted, the event is removed. Staff see every booking in the calendar they already use.
Who signs in with Google
The connection is set up once by the business’s administrator, who signs in with a Google account, approves the permissions and chooses the calendar. Customers who book on the website do not sign in with Google and do not give any Google permission.
Permissions and data used
The application requests four permissions: openid and userinfo.email (which Google account is connected), calendar.calendarlist.readonly (choose a calendar) and calendar.events (create, update and delete the booking events in the chosen calendar).
- Events contain booking details such as the booking code, activity, time, number of people and the contact details the customer entered.
- The refresh token is stored encrypted on the server and is never sent to the browser.
- Google user data is not sold, not used for advertising and not used to train AI models.
Disconnecting
The administrator can disconnect in the booking system at any time. The token is then revoked at Google and deleted. Access can also be removed in the Google Account. Events already in the calendar are not deleted when you disconnect.
Read the full privacy policy on Google user data Terms of service