Talk to us.
Write, don't book. Every message below reaches a person who reads it, and you get a real answer rather than a slot on a calendar. If a call turns out to be the right next step, we'll offer one — but nothing here requires you to have one first.
Or use your own mail client
Some things are easier from your own inbox, and a threaded reply beats a form every time. These all reach the same place:
| Address | For |
|---|---|
| hello@burnledger.io | Anything commercial — pricing, evaluation, connectors, or a question before you sign up |
| support@burnledger.io | An existing account: billing, verification records, a system that won't connect |
| security@burnledger.io | Vulnerability reports — please read the security policy first |
| legal@burnledger.io | Contracts, DPAs, and anything for counsel — see Legal for current status |
| privacy@burnledger.io | Data protection requests about your own personal data |
What happens after you send
The message lands in an operator inbox that is checked on the same rhythm as the on-call alerts. You get a reply from a person within two business days — the same commitment the security policy makes for vulnerability reports, held to deliberately, because a response time you can't keep is worse than none advertised.
If your question is about whether BurnLedger fits a particular datastore, say which one and roughly how it's reachable — publicly addressable warehouses work today, VPC-only databases do not yet, and it's fairer to tell you that in the first reply than the third.
One thing worth knowing first
If you're evaluating the product rather than buying it, you may not need us at all. The verification record anatomy page states plainly what a verification record proves and what it doesn't, the verifier checks a real verification record in your browser with nothing installed, and the $1 tier issues verification records against a hosted demo datastore without you connecting anything of your own. Those answer most of what a first call would.