Google Calendar Integration
Connect Google Calendar to Ekosistem App so Lets Meet bookings respect your existing busy times and write new bookings to your calendar automatically.
What does this integration do?
Conflict prevention
Lets Meet shows your availability, marking blocks already busy on Google Calendar as 'unavailable'. Members cannot book conflicting slots.
Auto-write to calendar
When a new booking is accepted, the event is automatically written to your Google Calendar. No manual copy-paste.
Only calendars you select
If you have multiple calendars, you choose which ones we use. The rest are never read.
Google OAuth scopes requested
- calendar.calendarlist.readonly — only to list your calendars' names so we can ask 'Which calendars should I check?'. No access to event content.
- calendar.events.freebusy — only busy/free time blocks on the calendars you select. No event titles, attendees, descriptions, or other content.
- calendar.events.owned — to write bookings we create into calendars you own (including your primary) and delete them on cancellation. Never writes to other people's calendars.
How to install
- 1
Sign in to Ekosistem App and open Lets Meet → Manage.
- 2
Click 'Connect Google Calendar'. A new tab opens to Google's authorization screen.
- 3
Sign in to Google and grant the three requested narrow permissions (calendar.calendarlist.readonly + calendar.events.freebusy + calendar.events.owned).
- 4
You're redirected back to Ekosistem App; a list opens where you choose which calendars to use.
- 5
Lets Meet is now synced — conflicts are auto-filtered and new bookings are auto-written to your calendar.
How to uninstall
From within Ekosistem App
- 1
Open Lets Meet → Manage → click 'Disconnect Google'.
- 2
Your tokens are deleted from our database immediately.
From Google Account
- 1
Go to myaccount.google.com/permissions.
- 2
Find Ekosistem App and click 'Remove Access'.
- 3
Google revokes the token; on our side the connection is auto-cleaned on the next API call (the 'invalid_grant' response).
How we handle your data
- OAuth refresh tokens are stored encrypted with AES-256-GCM in our database. Plaintext is never logged.
- For availability queries we only call freebusy.query — event content (titles, attendees, location, description) is NEVER read.
- Data is never used for advertising, never sold to third parties, never used to train AI/ML models, never read manually by our staff.
- Our usage adheres to the Google API Services User Data Policy, including the Limited Use requirements.
- See Section 8 of our Privacy Policy for full details.
Need help?
For questions about this integration, email info@ekosistem.app. We typically respond within 1 business day.