Etisia Appointment Reminders for Google Calendar™

What the add-on asks for

When a user installs the add-on, Google shows exactly three permissions. In Google’s own words:

None of these three lets the add-on read calendar events. The panel displays information the Etisia service already holds about the user’s own reminders. The add-on talks to Etisia over HTTPS with signed requests and never sends raw Google Calendar data across that connection.

The separate Etisia authorization

The reminders themselves are sent by the Etisia service, not by the add-on. During setup, each user signs in to Etisia with Google and grants Etisia access to their Google Calendar. This is a second, separate consent, and it asks for full Google Calendar access (https://www.googleapis.com/auth/calendar).

Why that scope, and what Etisia actually does with it:

• Lists the user’s calendars so they can choose which one to connect
• Reads appointments on the calendars the user selected, and only those
• Writes a short status marker into the title of each appointment it handles, for example (SMS sent ✅) or (SMS: no number), so the status is visible in Calendar itself
• Subscribes to change notifications so a moved or cancelled appointment updates the reminder
• Updates an appointment when a client cancels through the link in their text

Etisia does not read calendars the user has not connected, does not share calendar events with anyone except the service providers listed below, and does not use or require domain-wide delegation. Each user grants and can revoke this authorization individually.

What your users will see. When they connect, Google’s consent screen describes this permission as “See, edit, share, and permanently delete all the calendars you can access using Google Calendar.” That is Google’s standard label for the calendar permission, not a description of what Etisia does. Etisia reads the calendars a user selects, writes status markers into those appointment titles, and updates an appointment when a client cancels. It never deletes or shares calendars.

Data shared with sub-processors

To deliver a text, Etisia sends two things to the SMS provider for the recipient’s country: the destination phone number and the rendered message text, plus the routing metadata needed to submit it and obtain a delivery result. The calendar event itself is never sent.

Providers by country: Twilio (United States); ClickSend (United Kingdom, Ireland, Australia, Austria); BulkGate (Germany, Spain, Poland, Croatia); SMSAPI.si, Ms3 d.o.o. (Slovenia). Each is bound by a data processing agreement. Full details, retention periods, and legal bases are in the privacy policy, section “SMS delivery providers”.

To work out who an appointment is for, Etisia sends the appointment title and, when the title alone is not enough, its description, location, and attendee names to an AI language model through OpenRouter, which forwards the request to Google, Anthropic, or OpenAI; OpenAI is also called directly as a fallback. The result is used only to address the reminder, and Etisia does not use calendar data to train AI models. The Etisia app runs on DigitalOcean servers, and error reports and operational alerts, which can include appointment titles, go to Sentry and Slack.

Retention, export, and deletion

Client phone numbers and message records are kept while the business keeps an active account and the client has not opted out. Users can export their data and delete their account from the Etisia Profile page; deletion is confirmed by an emailed code and runs immediately. Opt-out records survive deletion as one-way hashes so a client who replied STOP is never messaged again. Full procedure, including revoking Google access without deleting the account: Data deletion and revoking access.

Installing for your organisation

Admin-managed install. In the Google Admin console go to Apps → Google Workspace Marketplace apps → Add app, search for Etisia Appointment Reminders for Google Calendar™, and choose the organisational units that should receive it. Users in those units see the Etisia panel in Google Calendar on the web without installing anything themselves. Each user still completes the one-time Etisia sign-in and calendar connection described above.

Letting users install it themselves. Under Apps → Google Workspace Marketplace apps → Settings, allow users to install apps from the Marketplace, or add Etisia to the allowlist if you restrict installs.

Removing it. On the same Marketplace apps page, remove the app for the affected units. That revokes the add-on’s three permissions for every user at once. The separate Etisia calendar authorization is per user: each user revokes it at myaccount.google.com/permissions, or asks Etisia support to do it for them.

Where it works. Google Calendar add-ons run in Google Calendar on the web. On phones, users manage reminders in the Etisia web dashboard.

Service status and escalation

• Live status: etisia.com/status
• Support: etisia.com/contact or [email protected]. Delivery incidents are typically answered within a few hours.
• A reminder that did not go out is flagged on the appointment title in Calendar and can be reported from the message log in the Etisia dashboard with Report issue, which opens a case on that exact send.

Security summary

• The add-on runs on Google Cloud Run and communicates with the Etisia service over HTTPS with signed, single-use requests.
• Google tokens are stored server-side, encrypted at rest, and are never exposed to the add-on panel.
• The three add-on permissions are frozen; any change would require a new Google review and would be announced.

Google Calendar™ and the Google Calendar™ logo are trademarks of Google LLC.