HeyCC
Data-flow workflow

Local data, iCloud sync, and model requests are three separate facts.

HeyCC stores app data on the device. When related settings are enabled, supported data may sync through the user’s own iCloud. Content required for an AI request can separately be sent to the selected model provider.

HeyCC shown across an iPhone home screen and Apple Watch

On deviceApp configuration and supported local data.

Through iCloudOnly supported data when the relevant sync setting is enabled.

To a model providerMessages or attachments needed to answer a request.

Reusable audit prompt

For this workflow, list: (1) data stored on the device, (2) data eligible for iCloud sync, (3) data that remains device-local, and (4) content sent to the selected model provider. Mark anything not verified as unknown. Do not use “private” or “local” as a substitute for the actual data flow.

Workflow

  1. List the app data involved in the workflow.
  2. Confirm what remains on the device.
  3. Review whether supported iCloud sync is enabled.
  4. Identify content sent to the selected model provider.
  5. Use non-sensitive test data to verify expected sync behavior.

Expected deliverable

A four-part data-flow record: local storage, iCloud-eligible data, device-only data and provider-bound request content. Selective sync should not be described as an all-data backup.

iCloud ownership does not imply that model requests stay on the device or inside iCloud.

Questions

Does all HeyCC data sync through iCloud?

No. Sync is selective, depends on supported data types and settings, and some data remains device-local.

Does iCloud sync mean AI requests never leave the device?

No. Model requests are a separate data flow to the selected provider.

Is every workspace backed up automatically?

Do not assume that. Backup and sync behavior depend on settings, supported types and the installed version.

Continue

All templatesFull data-flow guideProduct factsOfficial downloads