Self-hosted by default.

BotLatch runs in the operator's environment. Chat visitors do not create accounts, and unQbd does not receive visitor messages or client transcripts from a normal self-hosted installation.

Data in the installation

The local database stores owner account data, client and bot configuration, aggregate delivery metrics, and report-link records. Transcript storage is off by default and follows the configured retention window when enabled.

External services

License activation sends the license key, installation name, and activation identifier to BotLatch.com. Email is sent only when the operator configures SMTP. The connected n8n workflow and its own services process messages under the operator's control.

Purchase records

For eligible Managed Payments transactions, Stripe acts as merchant of record and processes payment details, tax, receipts, disputes, and transaction support under Stripe's privacy terms. Checkout and receipts present the purchase as Sold through Link, and Stripe provides payment, subscription, and order support through Link. BotLatch.com stores the Stripe customer, checkout, subscription, product, price, event, and paid-through identifiers needed to fulfill and support the purchase. It also stores keyed hashes and separately encrypted recovery copies of the customer email, license key, and delivery token. BotLatch never receives card data.

Acquisition measurement

BotLatch.com recognizes only a fixed BotLatch campaign code and keeps daily aggregate counts of campaign landing views and checkout starts. It does not store an advertising click ID, search term, IP address, user agent, or cross-site identifier for this measurement. When a campaign visit starts a Stripe Checkout Session created by BotLatch, the fixed campaign code is added to the checkout and fulfilled license record so purchases can be counted against the campaign. The fallback external checkout-link mode is not attributed. BotLatch does not use an analytics cookie for this measurement.

Logs and deletion

Application logs are designed to omit message bodies and secrets. Deleting a client removes its bots, usage records, transcripts, and report links from the live database. Operator-managed backups may retain older copies until they expire.