GGrowthAdminsTerms of Service
Placeholder — no version has been published yet.
This is a placeholder, not a legal document.
Nothing on this page has been drafted or reviewed by a lawyer, and none of it is binding on anyone. It exists so the route, the layout and the links are real before launch, and so the outline below can be handed to counsel. Do not rely on it.
The decisions a real agreement has to make. Written as open questions on purpose — a plausible-looking contract that nobody drafted is a liability, not a placeholder.
Who is agreeing
- Qluw contracts with the Brand Runner's organisation, not with individual seats. Everyone else — House Crew, Hired Guns, Shoppers, Suppliers, Matchmakers — reaches the product through that organisation or through a portal link, and needs its own short terms.
- Access is invite-only. There is no self-signup route in the product, so there is no click-through moment at signup; where acceptance happens has to be decided.
- Recording acceptance needs a column that does not exist yet: which version of these terms a person accepted, and when. Until it does, no acceptance is provable — which is a reason to settle the wording before the mechanism, not after.
What is promised
- Availability: what, if anything, is committed. Today the answer is nothing — the production database is single-AZ by a deliberate cost ruling, so an unplanned failure means a restore measured in tens of minutes. Promising uptime before that changes would be promising something the architecture does not do.
- Support response times, and the hours behind them.
- How and when the product may change, including removing a feature.
What the customer promises
- That imported source data was lawfully obtained and may be processed and emailed — this is the one that matters most, because outbound sending is the product.
- Acceptable use, and the consequences of a suspension.
- That anyone they invite is authorised to see what their role can see.
Money
- Plan, metering and credits: what a credit is, when it is consumed by an AI pass, whether it expires and whether it refunds.
- Billing cadence, failed payments, and what happens to data during a lapse.
- Payouts to Matchmakers and Suppliers, which flow through this product and therefore need their own terms.
- Ruled: Source Mining is metered on success, not rationed. 21¢ a verified contact with catch-alls unbilled, 11¢ a matched permit row, registry filings free. There is no platform ceiling — the Runner sets their own spend cap as a guardrail against a surprise invoice.
Ending it
- Notice on both sides.
- Export on the way out: what is provided, in what format, for how long it stays available.
- What survives termination — confidentiality, payment owed, suppression state.
- Ruled: records already delivered remain yours. Revoking Source Mining stops future passes; it never purges what an account already holds, and never freezes it read-only.
The usual, still required
- Limitation of liability and its cap.
- Indemnities, especially around customer-supplied source data.
- Governing law and dispute resolution.