Privacy Policy

Yardarm is a local-first desktop application. We do not operate any servers, we do not collect any data, and the app contains no analytics or telemetry.

Effective date: July 29, 2026

What we collect

Nothing. Yardarm has no accounts, no sign-up, no login, no analytics, no crash reporting, and no telemetry. The developers of Yardarm never receive your prompts, your code, your usage data, or any personal information. There is no Yardarm server for your data to be sent to.

Where your data lives

Everything Yardarm stores stays on your computer:

• Projects, chats, transcripts, and checkpoints are kept in a local SQLite database in your user data directory (on macOS, ~/Library/Application Support/yardarm/).
• Configuration and credentials (API keys, OAuth tokens) are stored in Mastra Code's local config files (~/.mastracode/ and its app-data directory), shared with the mastracode CLI. They are only ever sent to the provider they belong to.
• Git worktrees and checkpoints are ordinary git data inside your repositories and the app data directory; they never leave your machine unless you push them.

Network connections the app makes

Yardarm only talks to services you configure. Depending on your setup, data may be sent to:

• Model providers you configure — prompts and code context go to whichever model endpoints you connect (via your own API keys, OAuth subscriptions, or an OpenAI-compatible server). With a local provider (Ollama, LM Studio, …) inference traffic stays on localhost. Each provider's own privacy policy governs that traffic.
• Update checks — the app queries GitHub Releases for new versions. This is the only network traffic Yardarm itself initiates, and automatic checks can be turned off in Settings → About.
• Voice dictation (optional, off by default) — if you enable it, audio is sent to the speech-to-text provider you selected, using your own API key, only while you record.
• Connectors and MCP servers you add (optional) — services you explicitly connect (e.g. GitHub, GitLab, Supabase, Netlify, Vercel, Sentry, or any MCP server you configure) exchange data with the agent under their own terms and privacy policies.
• Git hosting — pushing, pulling, and PR/MR flows use your own git remotes and the gh/glab CLIs with your own credentials.

If you configure none of these, Yardarm works offline with local models and sends nothing anywhere.

Cookies and tracking on this website

This website is a set of static pages. It sets no cookies and includes no analytics, trackers, or third-party scripts.

Children's privacy

Yardarm does not collect data from anyone, including children, and offers no accounts or online services directed at any audience.

Changes to this policy

If this policy changes, the new version will be published at this address with an updated effective date. Because the app collects nothing, changes are expected to be rare and editorial.

Contact

Questions about this policy: support@yardarmdev.com or open an issue on GitHub.