How HYVV protects your money and data
HYVV moves real money between real people. Here’s how payouts move, how every one is recorded, and what we haven’t done yet.
On this page
How a payout moves
Your customers pay into your company’s own Stripe account. HYVV calculates every share, records it on the ledger and sends each payout through Stripe Connect.
| Protection |
|---|
Everyone gets their own Stripe account LiveStripe verifies each person who gets paid through HYVV and collects the bank account they’re paid into, in Stripe’s own forms. HYVV doesn’t store those details. One Express account each |
Only settled money is split LiveHYVV only splits revenue that has settled in your Stripe account, and holds back any cash reserve you set before anything is split. Settled charges only |
No share is paid twice LiveEvery Stripe transfer is keyed to its receipt, so a retried payout reuses the same request instead of sending the money again. Amounts are checked in whole cents before anything is sent. Keyed to its receipt |
Receipts anyone can check
Every payout has a receipt with its own fingerprint. Share a receipt link and the other person can verify the figures themselves.
Illustrative example · sample company NovaCraft Studios
A record you can check, not just trust
Tamper-evident: how every entry is written, and how a later change would show.
| Protection |
|---|
Hash-chained, append-only LiveEach money event is written once and linked to the one before it with a SHA-256 hash. Corrections are new entries, so history is never rewritten. SHA-256 chain |
Every chain re-verified NightlyAn automated job walks every company’s chain and flags any entry that no longer matches its hash. 04:00 UTC |
Transfers reconciled with Stripe NightlyA second job compares recent Stripe transfers with HYVV’s records and writes any difference to the ledger. 03:00 UTC |
Fingerprinted documents LiveDocuments are drafted from HYVV templates and the terms you set, signed inside HYVV, and stored with a SHA-256 fingerprint. SHA-256 per document |
Scoped access, protected sign-in
Your company records are sensitive. This is how access to them is controlled.
| Protection |
|---|
Access scoped per company LiveYou only see the companies you belong to. Membership is checked on every request, and admin-only actions check your role. Checked per request |
Two-factor sign-in LiveTurn on an authenticator app in Settings → Security, with one-time recovery codes in case you lose your phone. Authenticator app |
Sessions you control LiveSign-in attempts are rate-limited. See every device signed in to your account and sign any of them out — or all of them at once. Sign out everywhere |
Passwords and secrets LivePasswords are stored only as bcrypt hashes. Two-factor keys and recovery codes are encrypted with AES-256 before they’re saved. bcrypt · AES-256 |
Sensitive changes are logged LiveRole changes, member removals, ownership transfers, disconnecting Stripe and deleting a company are written to an audit log. Audit log |
HTTPS everywhere LiveEvery page and request is served over HTTPS, and browsers are told to always use it (HSTS). HSTS |
Built on providers that publish their own audits
We don’t reinvent payments or hosting. We build on established providers and keep HYVV’s own surface small.
| Protection |
|---|
Stripe for payments LivePayments and payouts run on Stripe, which is certified as a PCI DSS Level 1 service provider. Card details are entered on Stripe’s hosted checkout, not on HYVV’s pages. Stripe-hosted checkout |
Vercel for hosting LiveThe HYVV website and app run on Vercel, which publishes its own SOC 2 report. Website and app |
Signed, authenticated back end LiveHYVV only acts on Stripe events that carry a valid Stripe signature, and scheduled jobs refuse requests without a secret. Signed webhooks |
What we haven’t done yet, stated plainly
| Item |
|---|
Certifications Not yetHYVV doesn’t hold a SOC 2 report or other certification of its own yet, and we don’t claim audits we haven’t had. |
Refunds after a split BuildingIf a payment is refunded after it was split, the receipts it produced are marked refunded. Shares already paid out aren’t recovered automatically. |
Paying out owed shares Not yetIf someone hasn’t finished their Stripe setup, their share is still calculated and recorded on the ledger as owed to them. It isn’t paid out automatically once they finish. |
Bug bounty Not yetWe don’t run a paid bug bounty. We do want to hear about anything you find. |
Evaluating HYVV for real money?
We’ll walk you through the architecture in detail.