Is Google Calendar AI with MeinGPT GDPR-compliant?

MeinGPT is operated GDPR-compliantly in the EU and provides a DPA; operator SelectCode GmbH is ISO 27001:2022 certified. Only the calendar data a workflow needs is processed. Because calendar entries are personal data, a tight calendar scope is recommended on top.

Can I restrict access to individual calendars?

Yes. The permitted calendars can be set in the configuration; when they are, the assistant can only reach those. A default calendar can additionally be defined for cases where none is named in the conversation.

Can the AI cancel events or send invitations on its own?

Technically yes - but both have real external effect: cancellations are irreversible and invitations notify the attendees. These actions should therefore stay behind human approval; a read-only assistant is equally configurable.

Are time zones handled correctly?

Yes. Start and end times come back already converted to the requesting person's local time zone (ISO 8601 with offset). No recalculation is needed, and events across time zones are represented correctly.

Does the AI see my colleagues' events?

Only as far as the signed-in account may see them anyway - the assistant works in that account's user context. For other people's calendars the visible level of detail depends on the sharing settings; events marked private return correspondingly little.

How is this different from the Microsoft 365 calendar integration?

The use case is the same, the connection differs: Google Calendar runs through the Google connector via OAuth, the Microsoft 365 calendar through Entra ID and Microsoft Graph. Microsoft 365 has its own guide.

What does MeinGPT gate?

The page, the examples and one complete prompt stay open. Only the importable assistant and its full prompt pack are gated.

Integration · Google Workspace (Google Calendar)

Connect Google Calendar to MeinGPT

Read calendars and events, check availability, and create or update entries in the signed-in Google user's context.

The native Google Calendar connector reads calendars and events in the signed-in Google user's context. It can analyse availability and create, update, or cancel entries. Access can be restricted to selected calendars. Invitations and cancellations trigger real changes and should require deliberate approval.

A person connects their Google account through OAuth. The assistant sees only calendars available to that account and can be restricted to a defined selection. It reads events for specific date ranges, returns details in the local time zone, and uses a configured default calendar when none is named. New or changed events and cancellations remain controlled write actions.

Technical frame

Google Workspace (Google Calendar)

MeinGPT

Source: Google Workspace (Google Calendar)
Capability: Read calendars and events, analyse availability, prepare meetings, create and update entries - native Google Calendar connector (OAuth)
Connection: Personal Google OAuth in the user's context. Configuration can limit access to selected calendars and define a default calendar.
Data residency: Only the required date range, individual events, or attendee lists are processed for the current task. AI processing runs in the EU; Google Calendar remains the system of record.

Source, permissions, and data residency are documented separately for each connector.

Setup in the docs

Typical workflows

Prepare meetings straight from the calendar entry
Analyse availability across a date range
Analyse meeting load
Create and update events
Invite attendees after approval
Produce a daily or weekly overview

What the integration makes possible

Prepare meetings straight from the calendar entry

For an upcoming event the assistant pulls in title, description and attendees and produces a compact preparation with a proposed agenda and open points.

Analyse availability across a date range

Across a period it works out where the genuinely free blocks are - a basis for proposing times instead of scrolling through the week view.

Analyse meeting load

The assistant condenses how much time goes into which kind of meeting - by week, category or attendee group - as a basis for decisions about meeting culture.

Create and update events

An agreement made in chat becomes a calendar entry with title, time range and description - or an existing event is adjusted when something moves.

Invite attendees after approval

The assistant prepares the invitation and the attendee list; sending triggers real notifications and therefore stays a deliberate approval.

Produce a daily or weekly overview

The events of a period become a short overview with the most important meetings, what needs preparing, and the free blocks.

Clarify before starting

01A Google Workspace account exists that is allowed to see the relevant calendars.
02OAuth approval for calendar access clarified in the Google account or via Workspace administration.
03Calendars defined that the assistant is scoped to, plus a default calendar for events with no explicit target.
04Decided whether the assistant may only read, or also create, update and cancel.
05Clarified who approves inviting attendees (this triggers real notifications).
06DPA signed and the GDPR processing of calendar data approved internally.

Review the prompt and result openly

Prompt

Look at my events for the coming week. Give me a weekly overview with the three most important meetings, mark what I need to prepare for each, and list the contiguous free blocks of at least 90 minutes for focused work.

Result

**Week 32 - 12 events, 14.5 h in meetings**

| Event | When | Preparation |
|---|---|---|
| Quarterly sales review | Tue 10:00-11:30 | finalise Q2 figures |
| Customer meeting Muster GmbH | Wed 14:00-15:00 | check quote status |
| Roadmap alignment | Thu 09:00-10:00 | open points from week 31 |

**Free blocks ≥ 90 min:** Tue 14:00-16:30 · Wed 08:00-10:00 · Fri 09:00-12:00

Does this connection fit your use case?

We clarify the source, permissions, and connection required for the concrete use case. If the existing integration fits, you can move straight to setup afterwards.

Discuss the connection Start for free

Security and operations

Calendars contain personal and potentially sensitive information. Keep OAuth permissions and calendar scope as narrow as possible. Invitations, changes, and cancellations need a clear approval and logging process.

Review before choosing

Data residency - where is calendar data processed, and where do the AI requests run?
Permission inheritance - does the connector adopt the account's existing Google permissions?
Scoping - can access be restricted to individual calendars per assistant?
Action control - are cancellations and invitations bound to an approval?
Auditability - are access and calendar actions logged traceably?
Administrability - central approval of OAuth permissions, roles and revocation?

Known limitations

01Cancelling an event is irreversible, and inviting attendees sends real notifications - both actions should stay behind human approval.
02The assistant works in the user context of the signed-in Google account - without the corresponding permission it can neither read nor write a calendar.
03Details of other people's events are visible only as far as each calendar's sharing settings allow; entries marked private return correspondingly little content.
04The AI does not replace the scheduling decision - proposed times and attendee lists must be reviewed before an entry is created.

Frequently asked questions

Yes. Google Calendar is a native connector in MeinGPT. After signing in via OAuth with a Google account, an assistant can read calendars and events, analyse availability, and create, update or cancel entries.