Local records and remote processing
Missions normally execute on your Mac and keep their local records there. A remote model still needs the messages, code and tool results included in its requests. Local execution does not mean all content remains on the device.
| Path | Where the request goes |
|---|---|
| Skyflo with your own model key | Directly to the chosen model provider. |
| External coding agent | Through that agent's configured account and provider path. |
| Skyflo-managed model | Through Skyflo's service to the model provider. |
| Voice Mode | Audio to OpenAI through Skyflo's voice service. |
| Skyflo Cloud | Mission data and working-copy contents needed for remote execution. |
Read the current Privacy Notice and managed-content disclosure for collection, processing and retention details. These guides explain controls; they do not replace those documents.
Keys and connected access
Built-in model keys stay in macOS Keychain. Skyflo Cloud machines do not receive your Mac's provider keys or an account-wide GitHub credential. They do hold mission data and limited credentials for that mission, so repository contents still require care.
Switching agents can ask for consent to replay history to the new destination. Revoking that choice prevents future replay; it cannot recall requests already processed.
Memory and phones
Memory stored locally can enter a remote model request when recalled. Turn off Use memory in tasks to stop ordinary recall. This is separate from automatic learning and from explicitly requesting a Skill.
Pairing a phone enables remote sharing for supported mission views. Notification text can disclose project details. Remove a device when it should no longer have access, and review notification preferences on every linked phone.
Support and account requests
Use the account console's privacy controls and the support page for account or data requests. Share the minimum diagnostic information needed. Never include API keys, passwords or authentication tokens in a support message.