Security
In short
Usher Up runs entirely on Cloudflare's network. There are no servers of our own to patch, no database of our own to leak. Handoffs are small, encrypted, and deleted after 90 days.
In transit
Every request to Usher Up uses HTTPS with TLS 1.2 or higher, enforced at the edge. Calls we make to email, webhook and CRM providers use HTTPS as well. Webhook deliveries carry an HMAC SHA-256 signature over a timestamp and the body so your receiver can verify the message came from us and was not altered or replayed.
At rest
Handoffs are stored in Cloudflare Workers KV, which encrypts data at rest. Our own API keys are stored as encrypted Worker secrets, never in code or configuration files, and are not readable after they are set. When you add a webhook or connect HubSpot from your account page, we encrypt the webhook signing secret or the HubSpot key with AES-256-GCM before storing it, under a key held only as a Worker secret. We show a new signing secret once, when it is made. After that your account page shows only the last four characters of either one.
Access
Reading a stored handoff requires an administrative token. Only the people who run Usher Up hold one, and the Cloudflare account that hosts the service is protected by two factor authentication. There is no other path to a stored handoff: no database console, no export job, no copy outside Cloudflare's store.
Retention
Each handoff expires 90 days after it was created and is deleted automatically. A business can ask us to delete a handoff earlier. Account data is deleted 30 days after an account closes.
Abuse protection
The sign-up form is protected by Cloudflare Turnstile. The handoff endpoint rejects requests without a consent confirmation, limits message sizes, caps the number of handoffs per business per day, and is rate limited per source. We can block an assistant that misbehaves.
Reporting a problem
If you find a security issue, use our contact form. Please give us a reasonable time to fix it before publishing. We do not run a paid bug bounty but we do say thank you and credit researchers who want it.