Legal & risk
Last updated: October 2026. Operator: HEPH Protocol Foundation. Contact: legal@heph.network.
1 · Terms of use
HEPH provides open-source software, smart contracts and a web interface for machine identity, spending limits, Uniswap v4 swaps and machine-to-machine payments. HEPH does not custody funds: the operator owns the Machine Account, and the machine holds only a capped, revocable session key.
You are responsible for your devices, keys, fleet configuration and compliance with the laws that apply to you. You must not use HEPH for unlawful activity, to evade sanctions, or to register false machine identities or attestations.
The service and contracts are provided as is, without warranty. To the maximum extent allowed by law, HEPH is not liable for indirect or consequential loss, lost profits, or loss caused by smart-contract bugs, key theft, third-party services or chain outages. We may update these terms; continued use means acceptance.
2 · Privacy
Machine Passports, registry entries, spend policies and transactions are public on-chain by design and cannot be deleted. Do not register personal data as machine identity or metadata.
Off-chain, we collect only what you submit (for example the pilot form: operator name, machine type, device count, email) and basic technical logs. We use it to run the pilot and reply to you, keep it only as long as needed, and do not sell it. To request access or deletion of off-chain data, contact legal@heph.network.
3 · Token disclaimer
$HEPH is a utility and trust-bond token: operators stake it to unlock the Gold tier, and it can be slashed. It is not an investment product, shares, debt or a promise of profit, and its price can fall to zero.
Burns, fee splits and staking rules described on this site are design intentions. Staking parameters shown in the demo are proposals, not final. The Pons V2 bonding-curve pool is third-party infrastructure and its audit status should be checked before any launch participation. Nothing here is financial, legal or tax advice. Access may be restricted in some jurisdictions.
4 · Regulatory notice
Automated machine payments, stablecoin settlement and device identity may fall under payment, e-money, AML or data rules. Rules differ by country and change over time.
Operators in Indonesia should check requirements from OJK and Bank Indonesia, and tax treatment of USDG and token income. Operators elsewhere should confirm the local position before running a fleet on HEPH.
5 · Risk disclosure
Smart-contract risk: the hook, router, registry and paymaster may contain bugs even after audit. Key risk: anyone holding a machine’s private key can impersonate it until the operator revokes it. Attestation risk: hardware attestation can be faked or become outdated.
Chain and stablecoin risk: Robinhood Chain, USDG and bridges can fail, pause or lose peg. Market risk: the machine economy on Robinhood Chain is close to zero today, so liquidity and counterparties may be thin.
Risk register
| Risk | Mitigation |
|---|---|
| No DePIN ecosystem on Robinhood Chain yet | Start with one pilot partner; bridge fleets already on other chains |
| Machine key stolen from device | Secure element/TPM, capped session keys, operator kill switch |
| Fake machine data or attestation | Hardware attestation for Gold, slashing of operator stake |
| USDG lacks EIP-3009-style authorization | Facilitator uses ERC-4337 UserOp + paymaster |
| Bug in hook or router | Audit, immutable hook, spend caps as second defence |
| Regulation of automated payments and device identity | Legal advice; Indonesian operators check OJK and Bank Indonesia rules |
| Pons V2 audit not finished as of Sep 2026 | Check the latest status before launch |