Two inboxes. One rail.
Hive operates as a small, deliberate team. Sales conversations, founder conversations, and the treasury rail all use the same calm, exact channels. We respond inside one business day for sales; same-day for regulated counterparties.
Where to write.
No ticket queue, no chatbot funnel. Each inbox below is read by the human it belongs to. We answer in plain language.
[email protected]
Pricing, pilots, security reviews, regulated evidence fit, ViewKey access, and procurement walkthroughs. Include your jurisdiction and one-line use case in the first message.
[email protected]
Strategic conversations, design partnerships, technical questions on the receipt rail, and anything that needs the founder. Please reserve this line for substantive asks.
[email protected]
GDPR and CCPA requests, data-subject access, deletion, and portability. Privacy posture is described on /privacy. We respond within statutory windows: 30 days GDPR, 45 days CCPA.
Calendar · security review
For pilot counterparties: 30-minute security review walking through the receipt schema, ViewKey access model, restricted-geography routing, residency posture, and SOC 2 / ISO readiness.
The settlement rail.
Hive settles in USDC on Base 8453. The treasury address below is the same address bound into every receipt as the settlement counterparty. If a vendor or auditor needs to verify a settlement hash, they verify it against this address.
What we do not do.
Hive does not maintain:
- a chat support funnel
- a ticket queue
- a sales-development outreach team
- a partner channel program
- cold outbound automation
- conferences or speaking circuits
Conversations happen in writing, in plain language, in the two inboxes above. Decisions move quickly because the surface area is small.
Open the diligence room.
If you have read the platform, the compliance posture, and the trust model — and you want to see how the receipt rail behaves against your own data — open the diligence room. We respond same day for regulated counterparties.