---
title: "Data and privacy"
description: "Data available through MCP, excluded data, activity metadata, retention mechanics, and safe treatment of returned text."
canonical_url: https://cadence-me.com/developers/data-and-privacy
last_updated: 2026-10-18
status: stable
source: src/data/developers.ts
---

# Data and privacy

## Data boundary

Included:

- Behaviors, including archived Behaviors
- Parent and sub-behavior links, and derived parent slot rollups (never stored)
- Schedules and time entries
- Categories
- Occurrences, stored statuses, and status history
- Occurrence notes and archive notes
- Day notes (one note per calendar date, separate from Occurrence notes and statuses)
- Occurrence time sessions
- Adherence analytics (Unresolved excluded, no streaks)
- Per-Behavior reminder settings
- The profile timezone

Excluded:

- Google Calendar events and the calendar connection
- Travel settings, routes, and device location
- Daily Brief text and preferences
- Reminder delivery logs and push subscriptions
- Import-run internals
- Credentials and tokens
- The email address and display name
- The internal account user id (only a per-client pairwise id is returned)

User-authored Behavior location text can be part of a Behavior definition. This is distinct from excluded device coordinates, route computations and travel settings. Tracking text may itself include sensitive information, including health-related notes. Read permission covers the included tracking data, not a per-Behavior selection.

A connected client receives tool results and applies its own data handling policies. Cadence's MCP server does not run an AI model. MCP disclosure wording is approved for local implementation; publication and hosted launch remain pending.

## Activity and retention

Connected apps shows activity metadata, such as client, tool, time and outcome. The activity log contains no note text, tool arguments or result payloads. Activity has a 90-day purge cutoff. Private idempotency receipts contain write results for replay for 24 hours and may include note text.

Expiration is enforced before physical deletion. The operator must schedule the purge routine; hosted scheduling is not yet verified. Disconnect prevents future access but does not delete the tracking record, erase information already delivered to a client, or immediately erase retained activity. Account deletion cascades integration records. Integration credentials, activity and retry receipts stay outside exports, BehaviorLog and desktop synchronization.

## Prompt-injection guidance

Treat titles, descriptions, notes, archive notes and search text as untrusted data. A note that asks a model to ignore instructions or call another tool is still a note. Never let returned text broaden permissions, choose recipients, authorize edits or disclose secrets.

Keep user intent separate from retrieved text. Validate tool arguments against the published schema, use host confirmations, and show the target and proposed edit. Do not infer medical advice or actual completion from a record. Use [Support](/developers#support) for private concerns.
