Resources · Legal
Both documents are effective May 12, 2026. Enterprise clients on a negotiated custody agreement should read these as the baseline that agreement modifies.
Effective May 12, 2026. These terms are a contract between holdway and the institution named on the account ("you", "the client"). By opening an account you agree to them.
holdway provides custody of digital assets: we safekeep assets you deposit into your segregated wallets, execute transfers your authorized users instruct under your configured policy, and report on holdings. Nothing more. In particular, holdway:
"Digital assets" means the assets we list as supported from time to time — currently BTC, ETH, and USDC, with ERC-20 tokens by written arrangement. "Your policy" means the quorum, allow-list, and time-lock configuration active on your account. "Business day" means a weekday other than a U.S. federal holiday.
Accounts are opened in the name of a legal entity after completion of the onboarding described on our Compliance page. On opening, you designate authorized users and assign each a role — administrator, approver, initiator, or viewer. Between us and you:
We may refuse or offboard an account where required by law or by the sanctions and screening obligations described in Section 6.
You configure the controls on your account — approval quorums (for example, 3-of-5), withdrawal allow-lists, and time-locks. We enforce that configuration exactly as set. When an instruction satisfies your configured policy — the required quorum has approved, the destination is allow-listed, and any time-lock has elapsed — the instruction is binding: we will execute it, and once broadcast to a blockchain network it cannot be reversed by holdway or by you.
The consequences of that rule cut both ways, and we state them plainly:
We may delay execution of a policy-compliant instruction only where Section 6 (screening), a legal compulsion, or a genuine operational incident published on our status page requires it, and we will tell you when we do.
Fees are set out in your order form and consist of:
Fee changes require 30 days' written notice and never apply retroactively. Undisputed invoices are due within 30 days. For non-payment we may suspend new deposits and non-essential features; we will not withhold withdrawals of your existing assets to collect a fee dispute, though our agreed lien for unpaid fees under Section 5 survives.
Three consequences follow:
You may not use the service to:
We screen transfers as described in our AML program and may decline, delay, or freeze a transaction where law or a screening hit requires it. Where we do, we tell you unless we are legally prohibited from doing so. Material or repeated breach of this section is grounds for immediate termination under Section 9.
Our undertaking is narrow and real: the service will be operated with the diligence and professional competence described in these terms and our documentation, and we will maintain the control environment described on our Security page, as evidenced by our SOC 2 Type II examinations. Beyond that, the service is provided "as is".
Blockchain networks are third-party systems we do not control. Accordingly, we do not warrant:
Supported assets may be added or removed with 30 days' notice; on removal you will have a reasonable window to withdraw before support ends.
Indirect and consequential losses — including lost profits, lost revenue, and lost opportunity — are excluded for both parties, foreseeable or not. For direct losses, holdway's aggregate liability in any 12-month period is capped at the greater of the fees you paid us in that period and USD 100,000.
The cap does not apply to: loss of client assets caused by holdway's breach of Section 5 (segregation and title); holdway's fraud or willful misconduct; or any liability the law refuses to let a contract cap. Nothing in this section limits your obligation to pay fees. Our insurance program, described under Insurance, sits behind these obligations; it does not replace them, and its policy limits do not define our liability to you.
Either of us can walk away without cause by giving 30 days' written notice. We may terminate immediately where you materially breach these terms (including Section 6), become insolvent, or where continuing the relationship would put us in breach of law. On termination, asset return works as follows:
Fees stop accruing when the account holds no assets. Sections 5, 8, and 10 survive termination.
These terms are governed by New York law, disregarding its conflict-of-laws rules. The state and federal courts sitting in the Borough of Manhattan, New York have exclusive jurisdiction, and each party waives objections to that venue and, to the extent permitted, the right to a jury trial.
These terms, your order form, and any negotiated custody agreement are the entire agreement; where they conflict, the negotiated agreement controls, then the order form, then these terms. Assignment needs the other side's written consent; a transfer to an affiliate, or as part of a merger or a sale of substantially the whole business, is permitted with notice. Notices to us go to hello@holdway.xyz; notices to you go to your account administrators. If any provision is unenforceable, the remainder stands. Delay caused by circumstances genuinely outside a party's control is excused — but nothing, ever, excuses holdway from its segregation obligations in Section 5.
Effective May 12, 2026. Questions to privacy@holdway.xyz.
holdway is the controller of personal data processed in connection with the custody service and this website. This policy covers data about our clients' personnel — authorized users, beneficial owners, control persons — and about visitors to holdway.xyz and applicants who write to careers@holdway.xyz.
Two boundary notes. First, our clients are institutions; where your employer gives us your details as an authorized user, your employer decides that you are on the account, and we process the data to run it. Second, this policy does not cover on-chain data: blockchain transactions are public by the nature of the networks, and no custodian can delete them. What we control is the mapping between on-chain addresses and identified clients, and that mapping we protect as confidential.
We do not buy data about you, we do not collect data from social media, and we do not run advertising trackers on this site.
Each use rests on a stated legal basis:
We do not sell personal data, do not use client data to train machine-learning models, and do not use it for third-party marketing.
We share personal data with three kinds of recipients, and no others:
Where data moves across borders to a subprocessor, we use recognized transfer mechanisms and keep the documentation available to clients on request.
Personal data stays with us while the account is open, then for whatever period statute demands. Indicative periods:
AML minimums apply even to deletion requests: where you ask us to delete data we are legally required to keep, we restrict it instead. Restricted data is removed from operational systems, locked to compliance access only, excluded from any other use, and purged when the statutory period expires. That is the honest version of "delete", and it is the one a custodian can actually promise.
The controls that guard client assets guard personal data too:
Details are on our Security page. If we suffer a personal-data breach, we notify affected clients without undue delay, with enough detail for you to act, and notify regulators where required.
Depending on your jurisdiction, you may have the right to:
Exercise any of these by writing to privacy@holdway.xyz. Requests are identity-checked and answered inside 30 days, and if a legal obligation prevents us from fulfilling a request we will say so plainly and cite which one. You may also complain to your data-protection authority; we would prefer you write to us first, but that is your right regardless.
We update this policy when practices or law change. Material changes are notified to account administrators by email at least 30 days before they take effect, with the previous version available on request. The effective date at the top of this page always reflects the current version. We never use a policy change to retroactively justify processing that was not permitted when it happened.