DSH PRO
Download
DSH PRO

Privacy

Privacy policy

Effective 24 August 2026

The honest summary is that there is almost nothing to collect. DSH PRO runs on your Mac. Your credentials, your prompts, and the analytics you see all stay on the machine or go straight to the provider you signed in with. We do not run a server that your work passes through, so there is no account, no profile, and no usage history sitting with us.

What stays on your Mac

The parts of DSH PRO that hold your data never leave the computer it runs on.

  • Credentials. When you sign in, the resulting tokens or API keys are written locally as plaintext YAML at ~/.dsh/.credentials.yaml with 0600 file permissions. They are never sent to us. They go only to the provider you authenticate with.
  • Session logs. The harness records each session on disk so you can look back at it. Your prompts and the agent's model calls go directly from your Mac to whichever provider is connected.
  • Usage and analytics. The heatmap, token counts, and call counts in the Usage panel are computed locally from your own session logs. That reporting is built on your machine and stays there.

What the app sends over the network

On its own, the app makes only two kinds of network request, and neither carries your account or your usage to us. The third kind is the one you drive yourself — the Preview tab is a real browser.

  • An update check. The app periodically makes a plain GET to the file version.json on this site to see whether a newer build exists. Like any web request, this reveals your IP address to our web host. It carries no account information and no usage data.
  • Your provider's endpoints. Sign-in and every model call go directly to the OAuth and API endpoints of the provider you connected. Your prompts and completions travel straight there, not through us.
  • Sites you browse in Preview. Pages you open in the Preview tab load directly from your Mac to those sites, exactly as in any browser. Nothing about what you visit passes through us or is recorded by us, and the pane refuses permission prompts and file downloads outright.
  • No telemetry. There is no analytics, no telemetry, and no crash reporting sent to us. There is nothing of the sort in the app.

What the website uses

This site uses the services below for analytics, fonts, and optional newsletter updates.

  • Google Analytics. We use Google Analytics to see how many people visit and which pages they read. Google sets its own cookies for this and handles that data under Google's privacy policy. Block it with any content blocker and the site works exactly the same.
  • Google Fonts. The page loads the DM Sans web font from fonts.googleapis.com and fonts.gstatic.com.
  • The newsletter form. The beehiiv form loads when you choose “Get release updates.” If you submit it, the information you enter is sent directly to beehiiv and handled under beehiiv's own privacy policy.
  • A theme preference. Your light or dark choice is stored in the browser's localStorage. The site no longer stores a marker for an intro animation. Third-party services may also store data as described above.

Third parties

A few services see your data because you chose to use them. Each handles it under its own terms and privacy policy, which we do not control.

  • The AI providers you connect — for example ChatGPT, Grok, Kimi, or OpenRouter, or whichever service a plain API key belongs to. Your sign-in, your prompts, and your model calls go to the one you picked.
  • beehiiv, but only if you subscribe to the newsletter with your email.
  • Google Fonts, which serves the web font this site uses.
  • Google Analytics, which counts visits for us under Google's own privacy policy.

Your choices

  • Skip the update check. It is the only thing the app reaches out to on its own. Stay offline, or block the request to dsh.bytefwd.com, and it will not run.
  • Block analytics. Any ad or content blocker stops Google Analytics, and every part of the site keeps working without it.
  • Leave the newsletter. If you subscribed, every beehiiv email has an unsubscribe link that removes you.
  • Remove your credentials. Delete ~/.dsh/.credentials.yaml, or sign out inside the app. Signing out removes the credential from this Mac. It is a local action, not a server-side revoke. To end a provider's access to your account, revoke it in that provider's own account settings.

Changes to this policy

If this policy changes, we update this page and the effective date at the top. There is no account and no mailing list tied to the app, so this page is where any change is recorded.

Contact

DSH PRO is made by ByteForward. Questions about this policy can go to the ByteForward YouTube channel.