meeting-template

Privacy policy — Meeting Template for Google Calendar

Last updated: 2026-05-25

This document explains what data Meeting Template for Google Calendar (the “Extension”) handles and how.

Short version

The Extension stores only your template text and two boolean settings (Auto-insert, Overwrite) in your browser’s own chrome.storage.sync area. It makes no network requests, has no analytics, no telemetry, and no third-party services. Your data never reaches us or anyone else — it lives on your device and (if you’re signed into Chrome) syncs through Google’s own Chrome Sync to other Chrome installs where you’re signed in. We never see it.

What data the Extension touches

Item	Where it lives	When
Your template text (Markdown)	`chrome.storage.sync`	Auto-saved as you type in the popup
`autoInsert` toggle (boolean)	`chrome.storage.sync`	Saved when you toggle the switch
`overwrite` toggle (boolean)	`chrome.storage.sync`	Saved when you toggle the switch
The HTML rendering of your template	Injected into `calendar.google.com`’s Description field	Only when you click Insert, when Auto-insert fires on a new event, or when live-sync replaces a matching description

That’s the complete list. The Extension does not read your calendar events, your contacts, your emails, or any other data on the Calendar page beyond what’s needed to find the Description input element.

What the Extension does NOT do

No network requests. The Extension never fetch()s, XMLHttpRequests, opens WebSockets, or otherwise communicates with any server we operate.
No analytics. There is no Google Analytics, Mixpanel, Sentry, or similar SDK loaded.
No telemetry. We do not count installs, opens, clicks, or errors.
No third-party scripts. The Extension bundles only its own code plus a few standard libraries (Tiptap, Preact, DOMPurify, marked, turndown) at build time. No runtime fetching of third-party code.
No content read from Calendar. The content script reads the Description input’s current contents (to decide whether to replace, append, or skip) but never persists, transmits, or analyzes them.
No account or sign-in. The Extension does not authenticate, does not use OAuth, does not request access to your Google account.

Why each permission is requested

Permission	What it does	Why we need it
`storage`	Read/write the `chrome.storage.sync` area	Persist your template and toggle settings across browser sessions and devices
`scripting`	Programmatically inject the content script into Calendar tabs	Only used so that Calendar tabs which were already open before you installed or updated the Extension don’t require a manual reload before the Extension works in them
`host_permissions: ://calendar.google.com/`	Read and modify pages on `calendar.google.com` only	The Extension’s only function is to insert your template into a Google Calendar event Description, which requires the content script to run on that origin

The Extension does not request <all_urls>, tabs, cookies, webRequest, or any other broad permission.

Data storage and “sync”

chrome.storage.sync is Chrome’s own storage API. If you’re signed into Chrome with a Google account and have Chrome Sync enabled, Chrome will sync your stored values to other Chrome installations where you’re signed in. This is Google’s infrastructure, not ours. We never receive, see, or have any access to your stored values. You can review or clear them at any time:

Open chrome://extensions/
Find “Meeting Template for Google Calendar” → Details → Extension options or Inspect views → service worker → Application → Storage → Sync Storage
Or simply uninstall the Extension to remove its storage.

Children

The Extension is intended for adult professional use in calendar workflows. It does not knowingly collect data from children under 13.

Changes to this policy

If the data-handling story ever changes, this document will be updated and the version number bumped.

Contact

Questions about this policy can be sent to pmb21656@gmail.com.