Refund Policy

The rule. We do not refund BitcoinDatabase payments. The exceptions are three specific billing or service failures, set out below, and nothing else. The demo on the site runs real queries against the indexed chain before you pay, so you can see the response shapes and the data coverage first, and a plan can be cancelled from the billing portal inside your console whenever you choose.

Three cases in which we return a charge

These are the only grounds for a refund. Each needs to be backed by the payment and account records, and the refund never exceeds the charge it concerns.

• Billed twice. An error in our billing collected payment two times for the same period.
• A proven charge you never authorised. Someone used your card without permission, you report it within 14 days of the charge, and the records confirm it. The outcome follows the evidence rather than the claim, and we may ask you to confirm you have reported the card misuse to your issuer.
• The service was entirely unavailable. A fault on our side, confirmed by us, left the API, SQL and dashboards unusable for a continuous period, you reported it while it was ongoing, and we could not resolve it. Slower queries, a single endpoint misbehaving, rate limits, and faults in your own code, network or infrastructure are not covered.

A refund we approve is returned only to the card that was charged, is limited to what you paid for the affected period, and is our full liability for that charge. One refund gives no entitlement to another.

Requesting a refund

Write to support@bitcoindatabase.com from the email address tied to your account within 14 days of the charge. State the date and amount and which of the three cases applies. Requests that arrive later or from another address are not considered, and declined requests are not reopened.

What the fee covers

Developer, Growth, Scale and Enterprise are subscriptions billed monthly or yearly. Each one opens your API key, SQL access and dashboards for the period, with the monthly query and call allowance listed on the pricing page. The fee pays for that access for the period. It is the same whether your key sends one request or uses the full allowance. Overage beyond the allowance is billed for queries and calls already served and is final in the same way.

By subscribing you ask us to begin providing the service immediately. If a statutory withdrawal right or cooling-off period would otherwise apply to you, you accept that it ends once we start providing the service at your request.

Things that never qualify

• Changing your mind, ending the project, or switching to another data source.
• Sending few or no queries during a paid period.
• A renewal, including one collected after a failed attempt on your card.
• Believing the plan was a single payment. The pricing page, checkout, confirmation email and console all say that it renews.
• Forgetting to cancel before the renewal date, or cancelling just after it.
• Overage your key ran up, including traffic from a script, a loop in your own code or a key you exposed publicly.
• On-chain figures that changed after a reorganization or as new blocks confirmed, or analysis results that did not match what you expected.
• A feature that the pricing page does not describe, or that behaves differently from how you assumed it would.
• Buying the wrong plan or term.
• The remaining days of a period after you cancel. We never pro-rate.
• Use of your account or API key by anyone you shared it with.

Cancelling, renewals and failed payments

A plan renews until you cancel it. Open the billing portal from your console and cancel there, without contacting us. Cancelling switches off every later renewal from that moment, your key keeps working until the end of the period already paid, and cancelling does not count as a refund request.

Each new period begins on its renewal date and is payable from that date. When a card declines, the operator of our payment system retries that same unpaid invoice over the next few days. That is one amount being collected, not a second charge. A renewal paid after such retries is not refunded, even if you cancel once the new period has begun, and your access lasts until that period ends.

Our records

Signing up means accepting our terms of service, which include this policy, and our privacy policy. Before payment, checkout shows the plan, price, billing period and the fact that it renews.

For each subscription we keep the purchase time, the plan and price shown, your acceptance of the terms, the emails we sent you, and an account activity log with sign-ins, API key creation, query and call counts, SQL sessions and dashboard use, together with the technical details recorded with each event. The operator of our payment system keeps its own record of every payment, including the country that issued the card and the result of bank authentication such as 3D Secure. Unauthorised-charge claims are assessed against both sets of records.

Chargebacks

If a charge looks wrong, contact us before your bank. A chargeback raised without contacting us first is a breach of our terms of service. We respond by sending the records above to the card issuer, and the account and its API keys are closed permanently.

Purchases before October 14, 2026

A subscription bought before that date keeps the refund terms that applied on the day it was bought.