This notice covers the Apex Kitchen recipe, grocery, food-block and Google Calendar integration.
Connecting Google Calendar grants permission to read the calendar list and manage calendar events. The requested scopes are calendar.calendarlist.readonly and calendar.events. These permissions are broader than the integration’s current behavior: it uses calendar names, identifiers and access permissions to verify the designated Apex calendar, then accesses food-block events associated with this installation.
Apex sends Google the food-block and recipe title, preparation start and end times, reminder setting, completion or cancellation status, and a Cooking Buddy link. It reads event details back to verify saved information. This data is used to provide and maintain the calendar feature, not for advertising, profiling or AI-model training.
The local installation stores recipes, imported source files, grocery information, food blocks, calendar identifiers, synchronization details, and technical request or error logs. Google authorization credentials are stored locally in files protected by filesystem permissions. Setup and maintenance backups may contain previous data or credentials.
The browser stores a random reminder-device identifier, countdown state and details of an unconfirmed food-block save. These support reminders, countdown recovery and duplicate prevention.
When a Google Drive folder is configured, imported recipes and import reports are written to its local synchronized folder. Google Drive for Desktop handles cloud transfer. This Calendar connection does not request Google Drive API access.
People authorized to access the Apex installation may see its kitchen information. Google Calendar events and Drive files remain subject to their sharing settings. Google processes information sent to its services under its own policies. This kitchen integration contains no advertising or third-party analytics features and does not send data to AI APIs. The hosting website’s own practices apply separately to visits to these information pages.
You can stop Calendar access through your Google Account’s connected-app settings. Revoking permission stops future authorized access; it does not automatically remove existing Google events, Drive files, local records or backups. Disabling sync within Apex also does not revoke Google authorization.
The current integration has no automatic retention expiry or single action that deletes every copy. The installation administrator must review local records, imported originals, logs, credentials and backups when handling deletion. Browser site data can be cleared separately. Existing Google events and Drive files must also be removed separately where appropriate.
For privacy questions or help deleting local information, contact the person who manages your Apex installation using the support contact shown on the Google authorization screen.
Updated October 28, 2026.