Privacy notice

KushBitx collects only the data needed to operate, protect and improve the service. It does not ask for private keys or seed phrases.

Past close-service enquiries

KushBitx no longer offers reconciliation or close services and no longer accepts enquiries. Past enquiries (a work email and anonymous answers about the problem): the last one was received on 7 October 2026. Each is deleted automatically from the website intake store 90 days after receipt, so all are deleted by 5 January 2027. Notification emails about them remain subject to the mailbox and email-provider retention policies. To ask for earlier deletion, email admin@kushbitx.com.

Business email

Emails we send through Brevo, our email provider, carry an anonymous open-tracking pixel that Brevo adds and we cannot switch off. Links in our emails are plain and are not tracked. Opens are counted without being linked to your identity in our Brevo account, and we do not use this data for marketing.

Anonymous product measurement

The site may store random event and session identifiers plus allowlisted source and campaign labels for up to 30 days. These events contain no submitted fields, email addresses, request references, wallet addresses, policy contents, spend amounts, full URLs or referrers. Do Not Track suppresses optional browser events and replaces optional enquiry attribution with direct/none.

API reliability measurement

We retain bounded server observations for up to 30 days: route, HTTP status, policy decision, response duration, retry guidance and test/canary/automation labels. Optional random client and flow IDs are hashed; these are caller-declared identifiers, not verified customers. Completed report IDs are hashed to deduplicate delivered receipts. No request body, wallet address, payment signature or recovery key is copied into this measurement. Do Not Track disables optional client and flow linkage. Reliability counts still operate without identifiers.

Reports and payments

Paid requests store the submitted check input, result, service, payment evidence and recovery record for 30 days so the original report can be restored. Payment authorization and settlement use public Base transaction data. When a signed payment attempt fails, we keep a failure record for up to 90 days: time, route, service, failure stage and reason, a truncated user-agent and a keyed one-way hash of the IP address (never the address itself), so failed payments can be investigated. Calls to the MCP server at /mcp are processed in the same way as direct API requests; for each tool call we record the tool name, outcome and latency, never its arguments. When an MCP client connects, we record only the client name and version it declares (clientInfo), nothing else. Never place a private key, seed phrase or recovery phrase in a request.

Free trial keys. For each trial key we store a hash of the key (never the key itself), the project name, its daily limit, and when it was first used and expires. For each day we store counts of checks and of ALLOW, REVIEW and BLOCK results. We do not store the transaction, addresses or token from a trial request. Trial records are kept until 2027-01-31, then deleted.

Evidence Chain release candidate

When you explicitly create an Evidence Chain, we store its payment intent (including recipient, amount and optional sender), protected-policy decision and any requested evidence events. Access requires the policy agent key and expires with its 30-day pilot. Evidence is append-only: records cannot be edited after they are written. The whole chain is deleted automatically 30 days after its last record; use non-sensitive pilot data only. No signing keys or payment signatures are requested by these routes. Direct preflight and settlement checks require separate pilot activation.

SpendGuard

The stateless preview is evaluated without saving the proposed recipient, amount, policy or decision. If you explicitly create a protected policy, its rules and decisions are stored for the 30-day pilot. Only credential hashes are stored; one-time admin and agent keys cannot be recovered.

Feedback and pilot requests

Feedback is stored for the project team for up to 180 days from receipt and is then deleted automatically. A company-pilot request stores the contact email, company or project, expected decision range and workflow description for 90 days so KushBitx can respond. Do not include wallet secrets, signatures or recovery material.

Prepaid credits

When you top up prepaid credits we keep:

• the paying Base wallet address and network;
• a one-way hash of your credit key (never the key itself);
• the balance (paid, bonus and used credits) and the daily limit;
• a ledger of top-ups, deductions (time, service, credits and request reference) and refunds, with the payment and refund transaction hashes;
• signed account actions (rotate, revoke, daily limit, refund): wallet, action, value and nonce.

We do not keep check inputs in this ledger. A check result is held for 24 hours only, so a retried request is not charged twice. We keep the account, top-up, ledger and refund records for 10 years after the account closes, because they are accounting records of payments received and returned (Sultanate of Oman). The key hash is deleted when the account closes.

Backups

Cloudflare keeps automatic point-in-time recovery data for the website database for up to 30 days. Before a database change, KushBitx may take a manual export; it is stored offline by the company and deleted within 90 days. Deleted records disappear from backups when those periods end.

Service providers and protection

KushBitx uses Cloudflare hosting and its database for website intake, Brevo for business emails, and Gmail for the owner's mailbox. The older operations-server register described above is being deleted. For the existing tools, KushBitx uses hosting infrastructure, public Base RPC services, an x402 facilitator and market or security-data providers to answer requests. Only the request data needed for the selected check is sent. Per-source abuse controls retain bucket-specific hashed identifiers rather than raw source addresses in the application database.

AI tools

Client data is not processed with an AI tool until KushBitx has approved a commercial route for it, after reviewing the product terms, training, retention and sub-processors. We do not train models on client data.

Your rights

You may ask us to tell you what personal data we hold about you, to correct it, or to delete it, by emailing admin@kushbitx.com. We reply within 30 days. We may need to keep some records where the law requires it (for example the payment records above), and we will tell you which ones. Data written to the Base blockchain (payments, approvals, addresses) is public and permanent: neither we nor anyone else can delete it.

Contact

For a privacy question or a request concerning submitted contact data, email admin@kushbitx.com.