Google API Disclosure

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

This page explains how Linkssi (the "Service") accesses, uses, stores, and shares Google user data when you connect Google Calendar from Bookings. It supplements our Privacy Policy.

1. What Linkssi is

Linkssi is a creator and business platform for bio link pages, lead capture, bookings, and related tools. The Google integration is an optional Bookings feature: you connect your Google account so Linkssi can keep your booking calendar in sync and avoid double-booking.

Application home page: https://linkssi.com/
App name on the Google Cloud OAuth consent screen: Linkssi

2. Google APIs and OAuth scopes we request

When you choose to connect Google Calendar, Linkssi requests these OAuth scopes:

https://www.googleapis.com/auth/calendar — create, update, and delete calendar events for bookings you accept through Linkssi, and read calendar free/busy information so we can show accurate availability.
https://www.googleapis.com/auth/userinfo.email — read the email address of the Google account you connect, so we can show which account is linked in the dashboard.
https://www.googleapis.com/auth/userinfo.profile — read basic profile identity for the connected account (display context in the integrations UI).

We request only the scopes needed for the Bookings + Google Calendar integration described on this page. Connecting Google is optional; Linkssi works without it.

3. How we use Google user data

We use Google user data solely to provide and improve these user-facing Bookings features:

Availability — read free/busy ranges so public booking pages do not offer times that conflict with your connected calendar.
Event creation — create calendar events when someone books an event type you publish.
Event updates / cancellations — update or delete those booking-related events when a booking changes or is cancelled.
Google Meet (optional) — when an event type is set to a Google Meet video meeting and you have not set a custom meeting URL, create a Meet conference link on the calendar event.
Account label — store and display the connected Google account email so you can confirm which calendar is linked.

These uses are limited to providing or improving prominent, user-facing features in Linkssi Bookings. We do not use Google user data for advertising, credit scoring, personalized ads, or unrelated product analytics beyond operating this integration.

4. What Google user data we access and store

OAuth tokens — access token and refresh token for the connected account, plus token expiry metadata.
Account email — the Google account email returned by userinfo.
Calendar identifier — the calendar we sync to (typically the primary calendar you select/connect).
Free/busy ranges — time ranges we need to compute availability (processed to block booked slots; not sold or shared for other purposes).
Booking event fields we write — titles, start/end times, descriptions, attendees, and Meet/conference data for events Linkssi creates from your bookings.

We do not sell Google user data. We do not use Google user data for serving advertisements. We do not allow humans to read Google user data except: with your explicit consent for support; where required for security investigations (e.g. abuse); where required by law; or where data is aggregated and does not identify you.

5. Sharing and transfers

Linkssi does not transfer Google user data to third parties except as allowed under the Google API Services User Data Policy Limited Use requirements, for example:

To provide the Bookings features described above (including writing events back to Google Calendar / Meet via Google’s APIs).
For security purposes (investigating abuse or protecting accounts).
To comply with applicable law.
As part of a merger, acquisition, or sale of assets, only with explicit prior user consent where required by Google’s policy.

Infrastructure providers that host Linkssi (for example our hosting provider) may process encrypted or protected application data as part of operating the Service. They are not granted independent rights to use Google user data for their own purposes.

6. Storage and security

OAuth tokens and integration metadata are stored in our production database for your account’s Calendar integration row.
Access is limited to Linkssi application code that operates the Bookings sync; dashboard access requires your logged-in session.
Transport uses HTTPS. Passwords for Linkssi accounts are stored as bcrypt hashes (separate from Google tokens).
When you disconnect Google Calendar in Dashboard → Bookings → Integrations, we revoke tokens with Google when possible and delete the local integration record.

7. Retention

While connected — tokens and sync metadata are kept so the integration can keep working.
After disconnect — integration tokens and calendar link metadata are removed from our active integration store.
Booking records you own in Linkssi — remain subject to our normal account retention rules in the Privacy Policy (they are your Linkssi booking data, not a continuing mirror of your full Google Calendar).

8. How to connect and disconnect

Sign in to Linkssi and open Dashboard → Bookings → Integrations.
Choose Connect Google Calendar and complete Google’s OAuth consent screen.
To disconnect later, use the disconnect control on the same Integrations screen. You can also revoke Linkssi’s access from your Google Account permissions.

9. Limited Use affirmation

Linkssi’s use of information received from Google APIs complies with the Additional Requirements for Specific API Scopes / Limited Use requirements, including:

Limiting use to providing or improving user-facing features that are prominent in our UI.
Not transferring Google user data except as allowed by Limited Use.
Not using Google user data for serving advertisements.
Not allowing humans to read the data except under the narrow exceptions Google permits (consent, security, legal compliance, or aggregate non-identifying data).

10. Related policies

11. Contact

Questions about this disclosure or Google data practices: use the contact page.