Last updated 4 November 2026
Privacy & Legal.
How Gyro handles your data.
On this page
At a glance.
- Stored on your Mac
- Sessions, settings, logs, and app state. Local data
- Shared with your provider
- Prompts and task context can include files and command output. Provider details
- Telemetry off by default
- The website code includes no analytics or tracking scripts. Telemetry details
Local sessions and settings
Gyro stores sessions, settings, logs, and app state on your Mac.
Its data folder is ~/Library/Application Support/Gyro.
It also holds local workspaces, worktrees, and browser captures.
No Gyro account is required for v0.1.0.
API keys saved through Gyro’s provider settings are stored in macOS Keychain. Agent CLIs manage their own logins and may keep credentials and history outside Gyro’s data folder. Credentials you supply through environment variables remain managed by you.
What model providers receive
Provider-hosted agents receive prompts, attachments, conversation context, and tool results needed for a task. That context can include file contents and command output. An agent’s own tools may read additional files or contact external services while working. Review your provider’s permissions and privacy settings before sharing sensitive material. For these connections, Gyro does not operate a proxy for model traffic; your provider’s policies apply.
Gyro connects to Ollama only through a loopback HTTP endpoint on your Mac. A configured remote custom model endpoint receives your requests and context. Running a model locally does not prevent tools, package downloads, or other services you use from making network requests.
Telemetry and this website
App telemetry is off by default. This website’s code includes no analytics, advertising, tracking pixels, account gate, or third-party scripts. Fonts, icons, and product images are served from this website.
The app can also fetch the public model catalog from
usegyro.io/model-catalog.json. That request sends
normal connection metadata to the website host, without provider
credentials or task content. App update checks contact GitHub;
provider CLI version checks can contact provider services or
package registries.
Website storage and external services
The website saves your selected light or dark theme in your browser’s
local storage as gyro.site-theme, so your choice applies
across every page and future visits. Without a saved preference,
pages use the light theme. Clear this website’s
browser data to reset the preference. The website’s code does not set cookies.
Cloudflare serves the website. The Download, Install, and Changelog pages request public release information directly from the GitHub API; GitHub also hosts release downloads. These connections send normal request metadata, including your IP address and browser information, to the service receiving them. Release requests omit browser credentials. External links open sites governed by their own policies.
See Cloudflare’s privacy policy and GitHub’s privacy statement for how those services handle request data.
Delete your data
Delete individual sessions inside Gyro. To remove all local
app data, first save any work you need from Gyro’s local
workspaces and worktrees, quit Gyro, and delete
~/Library/Application Support/Gyro. This removes
the data in that folder; it does not undo changes to your
projects or delete files stored elsewhere.
Before uninstalling, remove saved provider API keys using the
Remove control in Gyro’s provider settings.
Removing Gyro.app or its data folder does not delete those
Keychain entries. If you have already uninstalled Gyro, use
macOS Keychain Access to identify the entries with service
Gyro and accounts beginning provider:;
remove only the entries you intend to delete.
Sign out of agent CLIs through their own tools and manage any environment-based keys separately. Removing a stored API key does not revoke it with its provider. Data already sent to an AI provider, remote endpoint, GitHub, or another external service is managed by that service; use its data controls or privacy request process. Clear this website’s browser data separately to remove its saved theme choice.
Optional Gyro Cloud
Paid Gyro Cloud is not active, and subscriptions can’t be bought yet. The app can show Account, Plan & billing, and Cloud settings while the service is being prepared; seeing them doesn’t mean a paid service is available. A Gyro account is optional: the local app and your own model providers work without one.
These settings don’t back up your chats or turn on hosted AI by themselves. The Cloud service being prepared would process account, device, and subscription information, plus the work you select for backup, report sharing, or managed AI. Managed AI is separate from your own provider connections: selected task context would pass through Gyro to an AI provider. Cloud storage would use service-managed encryption, not end-to-end encryption.
Before this service accepts production customer data, we will publish a Cloud privacy notice and service terms identifying the responsible operator and contact, the data processed, purposes, recipients, retention, and your privacy rights. Price, renewal, cancellation, and withdrawal information will be shown before any purchase. Until then, this page covers the local app, your provider connections, and this website, and its local-data wording doesn’t describe a future hosted service.
Version, license, and support
Gyro v0.1.0 is early software: it may change, fail, or lose compatibility. It uses Apache License 2.0 and comes without warranties beyond the law. Support is best-effort.
The public local app does not require a Gyro account. Paid Gyro Cloud is not enabled by installing the app; see Optional Gyro Cloud for its current status.
Trademarks and assets
Apple, GitHub, and the displayed AI provider marks belong to their respective owners. They identify platforms and integrations; their use does not imply affiliation or endorsement. Font and icon licences are separate from rights to use those trademarks.
Security and support
Report security issues privately through GitHub’s security reporting channel. For product help, use the support guide or open an issue. Public issues are visible to others: do not post API keys, private code, or sensitive personal information.