CalDiet Privacy Notice

Effective September 1, 2026

Google sign-in data

CalDiet uses Google Identity Services only to sign you in. It receives your Google account identifier, verified email address, and display name. The Google ID token is verified by the server and is not stored. CalDiet does not request access to your Google Calendar, Google Drive, contacts, or Gmail.

What CalDiet stores

Your CalDiet user record: Google account identifier, email address, display name, and creation/update timestamps.
A cryptographic hash of each CalDiet session token and its expiry time. The default session lasts 30 days.
For uploaded-file feeds, the filtered events and filter settings you chose, encrypted at rest with CalDiet's server key so CalDiet can host the subscription.
When a calendar pulls any subscription, a one-way feed key, generic feed label, content digest, last-pull time, pull count, and aggregate event total. This sync log stores no source URL or shift title. If you are signed in when you create a link, the dashboard associates that one-way key with your account.
If you opt in to Alerts, the encrypted feed capability, polling state, and the browser push endpoint and keys or native push token needed to detect changes and deliver notifications.
If you opt in to Team, the group name and invite code; your display name, role, sharing choice, hashed membership capability, and encrypted feed capability; and an encrypted 14-day schedule cache used to calculate the roster. Sharing is applied when the roster is read, so lowering the sharing level takes effect immediately.
If you use cover requests, the date, structured request status, participating member identifiers, and an encrypted shift title/time snapshot. That snapshot is decrypted only for an authenticated Team read, then redacted according to your current sharing choice. Cover requests accept no message or notes text.

Basic paste-a-link setup stores no server-side configuration. The source URL and filter settings are encrypted inside the private subscription link instead of being stored as an account record; only the aggregate sync metadata listed above is recorded when a calendar pulls it. Alerts and Team are optional; enabling either stores the encrypted feed capability and the feature data listed above. The plaintext QGenda URL is never stored.

How the data is used

The account data is used to authenticate access to CalDiet. Calendar data is used to produce the filtered subscription you requested and, only when you opt in, to detect changes, calculate the Team roster, answer the fixed “who is on call today?” intent, and coordinate structured cover state. Schedule decisions are deterministic and based on the shift types you confirm. The reviewed source-title set is retained only as one salted digest; individual unselected titles are not stored in the private link. Unselected source titles are replaced with a generic label before Team caching, upstream event identifiers are replaced with opaque CalDiet identifiers, and notification payloads contain no member, date, or shift detail. Source shift titles are not sent to a remote AI provider. The application code does not use Google account data for advertising.

Deletion

Use Delete account on the CalDiet home page to delete your user record, sessions, Google identity record, signed-in dashboard and sync-history records, account-attributed notification channels, and uploaded-file feeds created or claimed while signed in. Alerts and Team use separate capabilities and are not necessarily attached to a Google account. Leaving a Team deletes your membership and the cover requests you created; any cover you had offered for someone else is reopened. Web push records are also deleted when the browser unsubscribes or the endpoint becomes invalid, and invalid native push tokens are pruned. Use the support contact below to request deletion of a remaining notification record.

A basic paste-a-link feed is not an account record. Remove the subscription from your calendar and stop using or sharing its private link to stop access to it.

Contact

For privacy questions, use the support contact listed on CalDiet's Google consent screen.

Google's handling of information is governed by Google's Privacy Policy.