Privacy
dino runs on your Mac. It collects no telemetry, analytics or crash reports, and your code and prompts go only to the model providers your agents use.
dino is open source, so all of this can be checked in its code.
What stays on your Mac
Your sessions, their scrollback, your settings, your API keys and tokens, and your usage statistics live in dino's folder on your Mac (~/.config/dino). dino's local proxy runs inside dinod on your Mac, not on a server.
What leaves your Mac, and where it goes
- Your agents' requests, to their providers
Each agent talks to the provider it uses (Anthropic, OpenAI and so on) on its own login, as it would without dino. Claude Code's and Codex's requests pass through dino's local proxy on the way, unchanged, so dino can show their usage. When you choose a route for an agent (OpenRouter, your ChatGPT plan, a coding plan, a model on your Mac), its requests go there instead.
- Update checks, to GitHub
Once a day, dino asks GitHub for its latest release and downloads it from GitHub when you update. Turn this off in Settings → General → Updates.
- GitHub, with your own
ghloginPull requests, their checks, auto-fix and auto-merge, and automations that start on GitHub events, go through the GitHub CLI you're signed in to, only for the repositories you use them in.
- Installing an agent
When you install an agent from Settings, dino runs that agent's own installer, which downloads it from its maker.
The optional dino account
You don't need an account. If you sign in, it's only to sync settings between your Macs, through dino's account service at cloud.meetdino.com (its code is in the same repository, and you can host your own). It keeps:
- your email address, and your GitHub or Google account's id if you sign in with one;
- each signed-in Mac's name, macOS and dino versions, and when it was last seen;
- the settings you sync: routing, policies, each agent's mode, model and effort, worktree options, fallback chains, SSH hosts, repository variables (by git remote) and terminal and tmux settings. They travel over TLS and the service can read them, so your account page can show them.
It never receives your API keys or tokens, your code, your prompts, your conversations or your usage. Sign-in links are emailed through Resend. The service runs on Vercel with a Neon Postgres database, and its logs leave out tokens, codes, request bodies and query strings; counters that limit requests per IP address are kept for a day, and a Mac's sign-in request keeps the IP address it came from, to show you when you approve it, until a day after it expires. On your account page you can see and export what it holds, sign out your Macs, and delete the account, which is erased 30 days later.
Experiments, off unless you turn them on
- The free models pool runs agents on NVIDIA NIM's hosted models with your own NVIDIA key, so their requests go to NVIDIA. dino picks the model for each turn; with a TypeSafe key added too, up to 8,000 characters of each turn go to TypeSafe to help it pick.
- Computer use for agents without their own downloads open-computer-use, a pinned and checksummed release, from npm once. Using it sends nothing anywhere.
This website
meetdino.com is hosted on Vercel and loads its fonts from Google Fonts. It has no analytics and sets no cookies; the Light and Dark switch is remembered in your browser only.
Questions
Open an issue, or for something private, use GitHub's private reporting form, which only the maintainers see.
Last updated October 6, 2026.