Hushgate

Privacy Policy

Effective October 12, 2026.

TeeBox LLC is a South Dakota limited liability company (LLC). This Privacy Policy explains how TeeBox (we, us, or our) handles personal data. It applies when you visit Hushgate sites, request beta access, use Hushgate, or receive Hushgate email (together, the Service).

TeeBox is the controller of the personal data described here unless we state otherwise. This policy does not govern a third-party service that you connect to Hushgate. That service's privacy policy governs its processing.

Data we collect

Access and contact data

When you request access or contact us, we collect your email address, the use case that you describe, and your messages. Cloudflare Turnstile and our network providers can process an Internet Protocol address, browser details, and security signals to detect abuse.

Workspace and identity data

We process your email address, workspace identifier, invite and enrollment state, billing state, and GitHub login if you request source access. We process passkey public keys, credential identifiers, and ceremony data. Hushgate does not receive the biometric or device unlock data that protects a passkey.

The console keeps a session credential in the current browser tab. The console does not put that credential in a cookie, local storage, or session storage.

Connector and request data

We process the connector destinations, authentication settings, policies, and credentials that you provide. Credentials and policy documents are stored as authenticated ciphertext under a workspace key. Hushgate does not store the plaintext workspace key.

The gateway processes requests that your agent sends so that it can authenticate the caller, apply your policy, and forward an allowed request. Depending on the policy, this processing can include a method, path, query, headers, and request body. The gateway does not write request bodies, header values, query values, or credentials to application logs. A connected service receives the data that an allowed request directs Hushgate to send.

Billing data

Stripe collects and processes payment-card and billing details. We receive Stripe customer, Checkout, subscription, invoice, payment-method status, product, price, and transaction references. We do not receive the full card number or card security code.

Communications and service data

We process email delivery records, support messages, request identifiers, timestamps, policy decisions, service state, error classes, and other bounded operational data. We design application logs to exclude credential values and request contents. Infrastructure providers can process network and security metadata when they deliver or protect the Service.

How we use data

We use personal data to:

Depending on the applicable law, we rely on performance of a contract, legitimate interests in providing and securing the Service, consent, and legal obligations. You can withdraw consent when consent is the basis, but the withdrawal does not affect earlier processing.

Artificial intelligence models

Ordinary gateway traffic does not automatically go to an artificial intelligence model. Hushgate does not send customer request bodies, credentials, header values, query values, or customer records to a model as part of normal gateway processing.

We can use synthetic data and reviewed non-secret summaries to test optional model-assisted features. If we later send your personal data to a model provider, we will describe that processing. We will update this policy before we enable the feature for customer data.

How we disclose data

We disclose data only as needed for the Service, your instructions, or a legal purpose. Recipients can include:

portal;

encrypted backup storage;

confidential virtual machine and network delivery;

request;

reasonably necessary; and

to appropriate safeguards.

We do not sell personal data. We do not share personal data for cross-context behavioral advertising, and we do not use personal data for targeted advertising.

Retention and deletion

We keep workspace and subscription data while the workspace exists and as needed to provide the Service. Cancellation stops forwarding but does not delete the workspace. You can export available configuration and separately delete the workspace.

Workspace deletion removes live workspace records, destroys the current live workspace key, revokes sessions, and starts cleanup with Stripe and GitHub. Vendor cleanup can finish later. Encrypted backups can retain historical ciphertext, wrapped keys, and encrypted email recipients for up to 30 days. The storage provider applies expiry asynchronously, so final removal can occur later.

We retain billing, transaction, dispute, tax, security, and legal records as needed for legitimate business and legal requirements. Stripe and other providers retain data under their own policies. We keep access requests, communications, and operational records only as long as reasonably needed for their purpose.

Security

We use administrative, technical, and organizational safeguards that are designed to protect personal data. These safeguards include encrypted transport, a confidential-computing environment for the gateway, encrypted workspace material, access limits, and logs that exclude request contents and credentials.

No safeguard gives absolute security. Hardware, firmware, software, networks, connected services, and human actions can fail. The Security page describes important limits.

Your choices and rights

You can choose not to provide data, but some data is required to provide the Service. You can update billing details through Stripe's customer portal. You can export available workspace configuration and delete your workspace through the console.

Depending on where you live, you can have rights to request access, correction, deletion, restriction, portability, or objection. You can also have a right to withdraw consent or complain to a data-protection authority. We can ask you to verify your identity before we act on a request. Applicable law can permit or require us to keep some data.

To make a privacy request, use the contact information below. We do not discriminate against you for exercising a privacy right.

International processing

TeeBox is based in the United States. We and our providers can process data in the United States and other countries. Those countries can have different data-protection laws. Where required, we use an approved transfer mechanism or another lawful safeguard.

Children

The Service is not directed to children under 18, and we do not knowingly collect personal data from a child under 18. Contact us if you believe that a child has provided personal data.

Changes to this policy

We can update this policy as the Service and law change. We will change the effective date and give any notice that applicable law requires. A material change will apply prospectively unless the law permits otherwise.

Contact