---
title: Privacy Policy
description: "How DeployHermes handles deployment credentials, user data, and runtime access."
canonical: "https://deploy-hermes.com/privacy"
last-updated: "2026-08-23"
---

# Privacy Policy

> How DeployHermes handles deployment credentials, user data, and runtime access.

Canonical: https://deploy-hermes.com/privacy
Updated: 2026-08-23

DeployHermes is built to keep deployment credentials centralized, encrypted, and easier to manage than ad hoc self-hosted setups.

## What we collect

We collect the information needed to authenticate users, manage deployments, and store encrypted provider and channel credentials.

We do not position DeployHermes as a consumer social product or as a training-data destination for your channel conversations.

## Why we collect it

The data exists to provision Hermes deployments, secure access to the control plane, and keep the runtime working across provider and channel integrations.

We aim to keep operational visibility focused on what is needed for reliability and support rather than broad data retention.

## Usage analytics

The public site uses Vercel Web Analytics for aggregate page measurement and DataFast for page and crawler analytics on the deploy-hermes.com domain.

When DataFast is enabled, it can set a first-party `datafast_visitor_id` cookie so visits and later checkout attribution can be linked without exposing server-only credentials in the page markup.

## Security posture

Deployment credentials are intended to be stored encrypted, with access governed by the control plane rather than scattered across unmanaged servers.

If you have strict compliance or data residency requirements, contact us before production rollout so the deployment model can be reviewed against those requirements.

---

- [Full documentation index](/llms.txt)
- [Complete site text](/llms-full.txt)
- [Developer portal](/developers)
- [OpenAPI contract](/openapi.json)
- [MCP server card](/.well-known/mcp.json)