Privacy

Last updated: November 9, 2026

HubVibe (hubvibe-io.com), contact hubvibe@hubvibe-io.com. This page says exactly what the service receives, keeps and shares.

What we receive with each call

The request you send (for example a URL to audit, text to translate, or a name, email address, phone number or IP address to check), your IP address and user agent, and the payment details: for crypto, your wallet address and transaction hash; for cards, a payment reference from Stripe. We never see card numbers.

What we keep

Sales record, for every purchase: time, tool, price, payment method, wallet and transaction (or payment reference), receipt id, the request body (up to 16 KB), your IP address with an approximate location looked up on our own server (country, region, city, network), and your user agent. For a credit pack bought by card, it also keeps the short source label of the link you arrived on (for example "ads"), if there was one. This is our accounting and tax record, and it is kept.
Call ledger: tool, timing, provider used, cost, payer, and fingerprints (hashes) of the request and the result. No request or result content.
Retries: when you send an idempotency key, the result is stored so that a retry returns it without a second charge.
Results to collect (jobs handed back as a link) and generated videos: 48 hours.
Agent-to-agent tasks: 15 minutes.
Page monitoring: the baseline text of a page you ask us to monitor, until the next check replaces it.
Server logs: each request's IP address, path, status and user agent, rotated by size (typically a few weeks).
Human project requests: the contact details, company, selected service, page count and project description you submit with consent, plus the approved scope, quote, order status and delivery record. A random access token protects the customer status page; only its one-way hash is stored.
First-party storefront events: aggregate events such as a services-page visit, service view, concierge start, recommendation, quote request, checkout start, verified purchase and completed delivery. Concierge messages are not stored in this event log. HubVibe does not add third-party advertising or analytics scripts.

Who receives what

Only who is needed to do the job you bought: the service that performs it (for example Google Cloud for AI, speech, image, video, maps and BigQuery jobs; Brave Search; X; and public sources such as SEC EDGAR, Coinbase, Polymarket and government data portals), the website you ask us to read or audit, and the payment processors (Coinbase's x402 facilitator, Stripe, and the public blockchains a payment settles on). Human card checkout is hosted by Stripe. We do not sell data, show ads, use advertising cookies, or install third-party analytics.

Public human-project intake does not accept document uploads. Do not place confidential documents, passwords, payment data, private keys, or secrets in the project description. If a project later needs documents, HubVibe must identify the authorized secure transfer method, retention terms, and relevant third-party AI processing before the customer sends them.

Read-aloud widget

The standard customer-hosted read-aloud widget does not send page content, selected text, or listening activity to HubVibe and does not include HubVibe analytics. Speech voices and processing are supplied by the visitor's own browser, operating system, and configured device services, which remain subject to those providers' settings and privacy terms.

Your choices

Email hubvibe@hubvibe-io.com to ask what we hold about a wallet, key or receipt, or to have it deleted where we do not need it for our accounting and tax records.