Privacy

Private by design.

I built TrailSail for my own work, so the privacy rules are the ones I wanted for myself: no account, no cloud, no telemetry. Six rules, enforced everywhere, and you can check every one of them in the files on your own disk.

Keys and tokens live only in the Keychain

API keys and control tokens are generated on your server and travel once, inside the Tailscale-encrypted session, during pairing. They are never typed, logged or synced — each Mac holds its own in the macOS Keychain.

Pairing is safe by design

Pairing codes are single use, expire in ten minutes, and are stored hashed on the server. Device tokens are stored hashed too, so revoking a device is a server-side act, not a keys-on-disk story.

No telemetry, and updates are your choice

No telemetry, no accounts, no third-party services, unless you add a Brave or Tavily key yourself. TrailSail talks to the server you configured, and to the public web when you ask it to. One more request is yours to allow or refuse: on first launch it asks whether it may check trailsail.app once a day for a newer version. That is a request for one small file; it carries the app's version number and, like any web request, comes from your IP address. Nothing about you, your Mac or your chats is sent. Say no and it never contacts trailsail.app unless you press Check now. Change it any time in Settings → General → Updates.

Your network, and nothing else

The server is reachable only on your Tailscale network; nothing is opened to the internet. The control API binds to localhost on the server and is published only through Tailscale.

Everything else is a file you can open

The SQLite database, attachments, notes, tool logs, the server's config. If you can read markdown and a shell, you can audit the whole app's memory.

The web stays the public web

Tools that fetch web content block private and Tailscale addresses, and fetched text is marked untrusted before the model sees it. Instructions in a web page are data, not commands.

This website is static: no analytics, no cookies, no tracking. Like any web server, it keeps an ordinary log of requests (the address a request came from, the file asked for and the time). That log is used only to count downloads, and the server deletes it automatically after a short time. If you email Yard8 Limited about a Business licence, that email and the details on your invoice are the only information held about you. Your server counts the people who use it by their Tailscale login, to know whether a licence is needed; that count stays on your server and is never sent to Yard8 or anyone else. If you ask for an email about new versions, your email address is kept with Mailchimp, the service that sends those emails, and is used for nothing else. Every email has an unsubscribe link, which removes you. The two forms on this site, for reporting a problem and for emails about new versions, use Google reCAPTCHA to keep bots out. It is the one outside service the site uses. It is loaded only once you start filling a form in, never on a page you are just reading; Google may then set cookies and collect information about your device and how you use the page, under its own Privacy Policy and Terms of Service. What you send in a report, with your email address, is kept in Yard8's private issue tracker and used only to deal with that report. Back to the top.