Legal

The documents below are the agreement between you and ALIEN SOFTWARE LLC, a Wyoming limited liability company. They are written to be read, not to be clicked past, so this page is a map of what each one is for.

#The agreement

Terms of Service is the contract. The clause that shapes every other one is first: Clobber is infrastructure, and you are the operator of the markets you run on it. We supply the engine, the ledger and the feed. You decide what markets exist, who may trade on them, and how they end. Three consequences of that are worth knowing before you read anything else.

• We never hold your money or your users' money. The balances and holds inside the engine are double entry bookkeeping over units you define. There is no wallet, no deposit and no withdrawal, and nothing you or your users own passes through us.
• We never resolve a market. Settlement happens when your administrative key sends the command. We execute it. We do not read an oracle or judge an outcome.
• We never trade on your markets. No house account, no position, no share of anyone's outcome.

Acceptable Use Policy is the shorter and blunter document, and the one worth reading before you build. It has a list of markets that are prohibited everywhere with no exception, and then one rule for everything else: you may operate the markets you are authorised to operate, where you are authorised to operate them.

#What we commit to

Service Level Agreement carries the availability commitment per plan, the service credits if we miss it, and the support response times. Recovery objectives live on the reliability page, which says for every number whether it was measured or is a target, and only the measured ones are contractual.

Security describes how the Service is protected: tenant isolation, encryption, access control, and the durability properties the journal gives us. It is also where to report a vulnerability, at security@clobberhq.com, and we answer within one business day.

#Data

Privacy Policy explains what we do with personal data, in two capacities that give different answers to almost every question: as a controller for the people who use our dashboard and pay our invoices, and as a processor for the data our customers put through the API. It also says plainly what we can produce under legal process, and what we cannot, which for end user identities is the honest answer that we do not hold them.

Data Processing Addendum is the processor agreement, with the Standard Contractual Clauses incorporated. It needs no signature: accepting the Terms accepts it.

Subprocessors lists every third party involved in running the Service and what each one does. We give 30 days' notice before that list changes.

#For regulated customers

Financial Services Addendum is optional and applies only when an order form says it does. It is for customers that are financial entities subject to an outsourcing or third party risk regime, and it carries what those regimes ask a provider to put in writing: audit and inspection rights for you and for your competent authority, subcontracting conditions, incident notification deadlines, and an exit plan. It states no compliance with any regulation, because that is not ours to state.

#What changed, and when

Every document in this set carries one effective date, so that a reader can tell at a glance which version they agreed to. When one document changes, the whole set is restamped and the change is listed here.

15 September 2026. A review of the agreement against what the product actually does, and against what a regulated buyer asks for.

• Terms of Service. Signed attestations are statements about a recorded fact and never a payment instruction, and a settlement system built on one belongs to the customer (1.4). Public demonstrations on test networks, Solada among them, are outside the Terms and the SLA (2.4). What your terms with your own users have to say, and why we can enforce that one clause (3.7, 18.7). Data loss has a defined remedy: restoration from the journal and the snapshot, with your own exports still your responsibility (new section 10, which moved the sections after it down by one). A defect is corrected rather than paid for (13.5). Thirty days to dispute a record or an invoice, twelve months to bring an action (6.6, 14.6). Our own intellectual property indemnity is capped for the first time (14.4). Export survives a suspension, and extended journal retention is available for customers whose own rules need it (4.5, section 11). What happens if we wind down, and escrow for Enterprise (12.6, 12.7). The Service is offered to businesses and not to consumers (preamble).
• Privacy Policy. Section 7 now says where the data is stored and, separately, where it is worked on from, because remote administration is a transfer and naming only the company's country was incomplete.
• Data Processing Addendum. The same locations, in section 11.5 and Annex I, with a commitment to update them before anyone in a new country gets production access.
• Subprocessors. Says who administers the infrastructure and from where.
• Financial Services Addendum. New, optional, and applies only when an order form says so.
• Service Level Agreement. Unchanged except for one cross reference.

7 September 2026. First publication of the set.

#Contact

If you are an end user of a business that runs its markets on Clobber, we are not your counterparty and we hold no account for you. Your questions, your funds and your rights are with that business. See section 1 of the Privacy Policy.