Privacy Policy

Last updated August 11, 2026

Horde is a content-operations service. It helps teams collect articles, evaluate and curate them, publish an owned website, prepare email issues and social drafts, and coordinate engagement. This policy covers the app, public publisher pages, email subscription flows, and the optional Chrome extension.

What we store

• Account: your name, email, and a hashed (never plaintext) password. On a first signup with a work email, Horde may use the company domain to read the public company website and prepare editable, private publication settings, sources, and a first Edition.
• Workspace: teams, source URLs, article links, feed excerpts, extracted article text, retrieval status, curation notes, scores, first-party items, prompts, drafts, campaigns, and activity.
• Audience: subscriber email addresses, consent/import provenance, confirmation and unsubscribe state, and delivery status. Only the publication owner can export subscriber addresses through the web app or a dedicated, explicitly confirmed agent action.
• Notifications: if you enable them, a push subscription for your browser or device.
• Operations: security logs and basic request metadata needed to prevent abuse and operate the service.

How information is used and shared

We use this information to run the features you request, secure the service, troubleshoot delivery, and improve reliability. We do not sell personal information. We send only the information needed to service providers that process it for us:

• Cloudflare Email Service is the primary email delivery provider; Resend may be configured as a fallback by a deployment.
• Configured AI providers—xAI or Cloudflare AI Gateway and Workers AI—receive article titles and extracted article text plus a workspace's scoring criteria when AI relevance scoring is enabled. Source research sends the workspace's editorial focus and uses the selected provider's public-web search. When you use Ask Horde, the configured provider receives your chat messages, relevant workspace state, and the results of actions it requests. Conversation history, action logs, and approvals are stored with your Horde account. Gateway request logging follows the deployment's Cloudflare settings.
• Slack may receive operational signup/workspace notifications and the account email, publication name, short summary, and feedback id from a troubleshooting report you explicitly approve through Horde's agent interface. Approved excerpts and tool errors are redacted before storage; web-push providers deliver notifications when enabled.
• Google Fonts may receive normal browser request metadata when hosted fonts load.

Content deliberately published to a public page or issue archive is public and may be indexed by search engines. Private drafts, member rosters, prompts, and subscriber addresses are not part of that publishing surface.

What the extension does

The Horde extension talks only to joinhorde.com. It has no access to and runs no code on LinkedIn, X, Reddit, Product Hunt, or any other site — it cannot read, post, like, vote, or scrape on your behalf. It fetches your pending nudges, shows notifications, and opens posts in a new tab so you engage manually, as yourself. Its one content script runs solely on joinhorde.com to sign you in.

Cookies and the extension

The app uses a secure session cookie to keep you signed in. The optional extension talks only to the configured Horde server. It does not read or automate activity on LinkedIn, X, Reddit, Product Hunt, or other social sites; it fetches pending nudges and opens destinations so you can act manually.

Data control

Email support@joinhorde.com to request access, correction, export, or deletion. Email recipients can unsubscribe using the link in every message. We retain information while an account or publishing record is active and as needed for security, compliance, backups, and opt-out suppression.