Blowhorn Download

Trust Center Privacy

What Blowhorn stores, and where

Last updated 9 October 2026. This page covers this website, the Layer5 Blowhorn app and its Chrome extension. Layer5's own privacy policy covers Layer5 Cloud and every other Layer5 service.

This website

blowhorn.ai is a static site served by GitHub Pages. It sets no cookies, runs no analytics and loads no fonts, images, styles or scripts from third parties: they are all served from this site. Its one request to another host is the Download section's release lookup, described below. The newsletter form sends nothing unless you submit it.

  • GitHub serves the pages and keeps its own server logs. Those are covered by the GitHub privacy statement.
  • The Download section asks GitHub's public API for the newest release from your browser. That request reaches GitHub like any other request your browser makes, with your IP address and the usual request headers. With JavaScript off, no request is made and the page links to the releases page instead.
  • The site has one form, the newsletter signup in the footer. It is the same Layer5 newsletter signup as on layer5.io. When you submit it, your browser sends the email address you typed to Layer5's newsletter list on Mailchimp and opens Mailchimp's confirmation page. Layer5's privacy policy covers that list. The site collects nothing else you type.

The Blowhorn app

On your Mac

  • Browser sessions for LinkedIn, X, Reddit and Hacker News live in Chrome profiles on your machine. They never leave it.
  • Configuration lives in .blowhorn.yaml inside the installation. The store connection, including its password, lives in ~/.config/blowhorn/store.yaml, readable only by your user account.
  • For LinkedIn, X, Reddit and Bluesky, the secret a run signs in with is read from profiles/<name>/config.yaml inside the installation, and blowhorn profile set writes it there.
  • Run logs are written to the logs/ directory of the installation. The menu-bar app keeps its preferences and state under ~/Library/Application Support/Blowhorn/.

In Chrome, through the Blowhorn extension

The extension works only for the Blowhorn app on your Mac, over Chrome's native messaging. It acts only on the sites Blowhorn supports, only in the Chrome profiles you install it in, and only when the app asks. Everything it reads goes to that app and nowhere else: it reports to no server of its own, and it keeps nothing itself.

  • Sign-in information: a session cookie or token on a supported site, read when the app needs to reuse a sign-in you already have. Today that is your Slack workspace session, which the app keeps in your organization's store (below).
  • Your communications: the posts, comments and messages the app asks it to enter and send as you.
  • Page content: what a page shows, read to tell when an action has finished; a screenshot when an action needs a person to check it; and an export you asked a site for, such as an analytics or connections export, which it catches and hands to the app.

In your organization's store on Layer5 Cloud

  • The content queue, schedule, profiles, run ledger and analytics. Every row is scoped to your organization's id.
  • Platform credentials, such as API tokens and app passwords, in the credentials table of your Layer5 Cloud organization. Blowhorn reads them when it checks which profile may act on which platform. GitHub, Hacker News and Slack runs authenticate with the stored value; for Slack that is the workspace session captured from your Chrome, or a Slack app token you enter. LinkedIn, X, Reddit and Bluesky runs read theirs from the local config.yaml above.
  • Layer5 Cloud's handling of that data is governed by the Layer5 privacy policy.

What the app sends

  • Posts, comments, reactions and invitations to the platforms a profile is configured for, when an approved row is due or when you run a command. Nothing is published from a dry run.
  • A version check that lists the releases on Layer5's Blowhorn release channel, hosted on GitHub. The check needs GitHub credentials: when a GitHub token is already on your Mac (GH_TOKEN, GITHUB_TOKEN or gh auth token), the app sends it with that request, and updating downloads the disk image published with the newest release, installs the Blowhorn app from it into /Applications and relaunches. Without a token, the update button opens that release page in your browser and the app downloads nothing itself.
  • No usage analytics and no crash reports. The app carries no analytics or crash-reporting library.

Questions

Open an issue on the site repository for anything about this page, or contact Layer5 through the channels on its privacy policy.