Last updated October 8, 2026
Privacy Policy
This policy is intentionally short. We try not to collect customer data, and when another company must handle data for a service to work, we say so plainly.
Our position
Privacy is a right, not a feature. hob is designed to avoid collecting customer data unless we need it to provide the product, answer you, process a payment, or fix a problem you reported.
We do not sell customer data. We do not run analytics by default that require you to opt out.
What stays on your device
hob runs locally. Your workspaces, agent conversations, session history, and local settings are stored on your device unless you choose to send something to us.
Your normal agent traffic goes between you and the inference providers you choose, such as Anthropic, OpenAI, or other providers supported by your agent backend. hob is the workspace around those tools, not an inference provider.
When we may receive information
If you contact us or submit a form, we receive the information you send so we can respond.
If you send us a crash report or support diagnostic, we may receive redacted runtime information such as app version, operating system, error details, logs, and related context needed to understand and fix the issue.
Trials, licenses, and payments
SmartAppsCo LLC uses email addresses and signup dates to administer hob trials and licenses, deliver license keys, and send service messages such as trial-expiry reminders. Email addresses are encrypted in transit and any copies we retain are encrypted at rest. We never sell them or share them outside SmartAppsCo LLC except with providers needed to operate these services.
Payments are processed by Polar. Polar necessarily handles customer and billing information for checkout, subscriptions, tax, receipts, and payment support. Polar has its own privacy policy.
hob receives the information needed to know whether your subscription is active, help with purchase support, and meet basic accounting or legal obligations.
Remote access relay
If you use hob's remote access relay, Cloudflare handles the WebSocket traffic needed to operate that connection.
hob encrypts relay payloads client-side before they reach Cloudflare's network and decrypts them client-side after they leave the relay. The relay carries encrypted frames; it does not have the plaintext needed to read your workspace or session data.
Webhooks
If you create a webhook endpoint, services you choose send requests to hob's relay at connect.hob.dev, operated on Cloudflare. Cloudflare ends the HTTPS connection, so the request is briefly in memory on the relay.
Before it is stored, hob encrypts it to a key that only your computer holds. hob and Cloudflare cannot read stored webhook events. hob does not log webhook contents. Stored events are deleted after your computer receives them, or when they expire.
Cloudflare's network may record request metadata, such as the URL and time, to protect and operate its service. If you control the sender, you can also encrypt the payload yourself.
What we do not do
We do not sell customer data.
We do not use your local workspace data for advertising.
We do not require you to opt out of default tracking analytics.
We do not intentionally collect more information than we need to provide, support, and improve hob.
Questions or deletion requests
If you want to ask about your data or request deletion of information you sent to us, contact us and we will handle it directly.