Terms of service

What a seat is

A seat is a prepaid, non-transferable licence for one person to use one API key on one machine, for 36 months of that machine's uptime. You pay once, at the start, and nothing after.

A seat is not equity, not a share, not a security, not a loan, and not a stake in hardware. You will never own the machine or any part of it. Nothing here gives you a claim on the company's assets, its revenue, or its decisions, and no clause in this document should be read as promising you a financial return.

Two things buyers sometimes expect from a project like this and do not get here: control over how the company is run, and a profit. What you get is compute, for three years, at a price that cannot move, plus the rebate in section 13, whose whole purpose is to send the machine's leftover value back to the people who paid for its working life.

The rebate and every refund in this document are capped, together, at what you paid for your seat. There is no combination of events in which a seat pays you back more than it cost. That cap is deliberate and it is the reason a seat is a prepaid service rather than an investment. If you are here because you think the machine will be worth a lot in 2030, buy a machine instead.

Words used here

Company

Entity name pending, registered in jurisdiction pending. We, us, our.

Node

The single NVIDIA DGX B300 the company buys and runs, plus the gateway software in front of it.

Seat

One licence, one key, one person. 1,500 exist and no more will be created on this node.

Member

The person who holds a seat. You.

Launch

The day the node begins serving members generally, announced in writing to every member, to the day. The term starts here, not at the pledge.

Term

36 months of node uptime from launch, as measured in section 04.

CU

Compute unit. The counter the fair-usage system spends. At launch, 1 CU covers 10 tokens.

Active session

A key with a request in flight or with fewer than 30 seconds since its last one.

Good standing

A seat that has not been terminated for breach under section 08, and whose member we can reach at the email address on the account.

Who can buy one

1. You are 18 or older and buying for yourself, not for a company to hand around.
2. One seat per person at launch. If you need coverage for a team, ask us about team seats rather than sharing a key. Team seats are priced separately and are not part of the 1,500.
3. You are not on a sanctions list, and you are not in a country we are barred from serving. We check this once, at purchase.
4. You accept that the machine sits in one country, named before the campaign opens, and that your traffic reaches it there.
5. Export control. Compute and model weights are controlled goods in several countries. You will not use your seat from a country under comprehensive export restrictions, will not make the endpoint reachable from one, and will not use the service to develop weapons of any kind. If a change in export law makes serving you unlawful, section 20 applies rather than us simply going quiet.
6. You buy in your own name, with details we can reach you at. Section 24 explains why the email address is load bearing.

The 36 months

The term is 36 months of the node serving, not 36 months on a calendar and not 36 months of your usage. Read the three parts together, because taken separately each one misleads.

1. The clock starts at launch, on a date we state in writing to every member. It does not start when you pledge or when the money clears.
2. Outage days are added back to the end, for all 1,500 members at once. If the node is down for a week in year two, everyone's last day moves a week later. Time lost is repaid in time.
3. Your own idle time is spent time. If you do not touch the key for three months while the node was serving normally, you do not earn three extra months. The machine was up, powered, and reserved for you, and that is what you bought.
4. The term belongs to the node, not to you individually. Every member's term ends on the same day, which is what makes the end-of-term sale in section 13 possible at all.

Your key

One key, one human at the keyboard. That is the entire rule, and the reason for it is arithmetic: the price works because 1,500 people share the machine, and it stops working the moment a key becomes a product someone else resells.

Fine, and never a problem

• Your own work, your employer's work, and your side projects, all on the same key
• Running many agents at once from your own machines
• Pointing Claude Code, Codex CLI, Cline, Aider, or anything else OpenAI-compatible at the endpoint
• Building and shipping a product whose code you wrote with the model

Not allowed

• Giving, lending, or selling your key to another person
• Putting the endpoint behind a product, service, or bot that other people call
• Proxying the key for your team, your company, or your Discord
• Selling capacity in any form, including free tiers that are paid for elsewhere

Seats are non-transferable. You cannot sell yours, and there is no secondary market for us to police. If you no longer want your seat, tell us and it lapses.

Fair usage and the three modes

There is no billing meter and there are no weekly caps. What exists is a pacing system that only engages when enough people are online at once, because one machine cannot serve unlimited concurrent 1M token contexts and no honest document would claim otherwise.

1. The stamina numbers at launch: a tank ceiling of 5,000,000 CU, refilling at 90 CU per second, continuously, around the clock. That is roughly 7.8M CU a day, and a 15 minute break restores about 81,000 CU.
2. You are never locked out. An empty tank is not a ban and there is no 24 hour penalty box. The refill never stops, so the worst case is that you wait a few minutes.
3. Expect Protection mode during business hours. We sell 1,500 seats on a machine rated for 240 concurrent-comfortable users, and we say so on the landing page. Nights and weekends run wide open.
4. The CU numbers are calibration variables, and this clause is the only place we are allowed to change them. The ceiling, the refill rate, and the token exchange rate are tuned during the 30 day beta against real traffic. After that, a change needs published data, 14 days of notice, and a typical member no worse off than before. We will never change them to make room for seats 401 and up, because those seats do not exist.
5. The status page is public. Current mode, active users, queue depth, node health. Your own dashboard shows your tank.

Acceptable use

We cannot read your prompts, so this section is about conduct, not subject matter. We are not going to start filtering what you ask the model, and there is no topic list here.

Do not use your seat for any of this:

• Anything illegal where you are, or where the machine is
• Sexual material involving children, in any form, generated or otherwise
• Attacks on the node, the gateway, other members, or third parties, including intrusion attempts, denial of service, credential stuffing, and mass spam
• Selling, sublicensing, or brokering the capacity you were sold, which section 05 already covers
• Deliberate attempts to defeat the stamina ledger or the active-session count

What you build with the model is your responsibility, including whether it is legal where you ship it.

How we enforce it

1. No key is ever terminated by a script. The gateway flags patterns. A person reviews every flag.
2. You hear from us before anything happens, at the email on your account, with what we saw and what we think it means. You have seven days to answer, and you can ask for the flag data behind the decision.
3. Confirmed resale ends the seat, with no refund and no rebate. This is the one breach with no second chance, because it is the one that takes capacity from the other 399.
4. Everything else escalates. We ask you to stop, we suspend if you do not, and we terminate only if it is unresolved after suspension.
5. We publish the count, never the names. Monthly transparency posts say how many keys were flagged, reviewed, and terminated. Who they belonged to is nobody's business.

The model, and the one vote

The node runs Kimi K3 at launch. Members vote on exactly one question, for the whole three years: whether to move to a newer open-weights model when one appears.

1. A candidate has to clear three bars before it goes to a vote: it fits the node in FP8, its licence permits commercial serving, and it beats the incumbent on a published coding-weighted evaluation set that we run ourselves and show the workings for.
2. Simple majority of seats, seven day window. We publish the tally and then we implement it.
3. We can veto a candidate on three grounds only, in writing, with reasons: its licence forbids what we would be doing, a lawyer says no, or it does not fit the hardware. Never because we prefer a different model.
4. There is no vote on anything else. Not price, not the budget, not staffing, not hardware, not the sale at the end. Keeping governance this narrow is what keeps a seat a service licence rather than something a regulator would call a security.

Uptime and service days

1. The target is 99.0% a month, measured at the public endpoint by an outside monitor whose data we publish.
2. Every missed percentage point adds three service days to the end of the term, for all 1,500 members, automatically, without anyone filing a claim.
3. Planned maintenance is announced 72 hours ahead, capped at eight hours a quarter, and does not count against the target.
4. If one GPU fails, we serve a smaller model at full availability rather than the flagship at reduced capacity. Members pick between the two in a status page poll.
5. If the node is down for more than 48 hours, service bridges to rented GPUs behind the same zero-retention gateway, paid from the hardware reserve, until it is back.
6. Service days are what downtime buys you. Added days, the bridge to rented GPUs, and the wind-down in section 14 are the remedies for the node not serving. Downtime does not generate a cash payment on its own, for the reason set out in the refund policy: cash for a bad afternoon comes out of the reserve that backs the real promise, and it comes out for all 400 people. Where the law where you live gives you a remedy on top of this, you keep it.
7. Some outages are nobody's fault. Section 20 says which ones, what still gets repaid, and the point at which an unfixable stop becomes section 14 instead.

The price

$5,300, once, for the whole term. The first 60 seats in the campaign's opening 48 hours are $4,995 and are otherwise identical. There is no renewal charge, no overage, no per-token billing, and no upsell you have to accept to keep what you bought.

We cannot raise the price during the term. Not for inflation, not for power costs, not if the machine turns out to be more popular than expected. If we ever offer paid extras, they will be genuinely optional and your seat will not get worse for skipping them.

1. Tax. The price is quoted in US dollars. Where the law where you live requires a consumer price to include sales tax or VAT, the figure you are shown at checkout is the figure you pay, tax included, and the invoice breaks it out. Where tax is charged on top, the checkout page says so before you pay, never after.
2. How you pay. Once, by card, through Kickstarter during the campaign. We never see your card number. There is no stored card, no subscription, and nothing to cancel later.
3. What the price does not include. Your own bandwidth, your own tooling, and any tax you owe where you live on what you build. There are no other fees attached to a seat, and if that ever stops being true we will have changed these terms under section 17 and you will have the exit it gives you.

Your prompts, your outputs

1. Everything you send and everything the model sends back is yours. We claim no licence in any of it, and we could not exercise one if we did, because none of it is kept. The privacy notice spells out the architecture.
2. We do not train on your traffic, and we will not start without asking you first.
3. The model weights belong to whoever released them, under their own licence. We publish the current model's licence terms and you have to comply with them when you use the output. Where a licence is unclear, that is a reason we might veto a candidate under section 09.
4. The model is wrong sometimes. Checking its output is your job, and section 16 says the same thing in colder language.
5. Model output is not unique to you. Ask the same question as another member and you may get the same answer, and neither of you did anything wrong. Whether text a model produces can be owned at all is unsettled in several countries, so we do not claim it is yours in a way we cannot deliver. What we promise is the part we control: we take no licence in it, we keep no copy of it, and we do not give it to anyone else.

The completion rebate

When the 36 months have been delivered, the machine is sold and every dollar of the net sale price is divided equally among the members. The company keeps none of it.

1. When. The sale runs within 90 days of the last day of the term. At month 33 we publish the timeline and the broker before the term ends, so you can watch it happen.
2. How. Broker or public listing, with a published listing period and a minimum number of bids before we accept one. The process is mechanical and written down in advance. Nobody at the company decides who buys it or for how much.
3. What net means. Gross sale price minus a closed list of costs: broker commission or listing fee, crating, freight and transit insurance, decommissioning and certified data destruction, the escrow agent's fee, and any tax on the sale itself. Nothing else is deductible, and the total is capped at 8% of gross. Our staff time is not a deduction. There is no management fee.
4. Who is eligible. Every member in good standing on the last day of the term, as defined in section 02. A seat terminated for resale under section 08 is not eligible.
5. Where the money sits. Sale proceeds go straight to an attorney-held escrow account and pay out from there. They never pass through the operating account.
6. What gets published before anyone is paid: the listing, the bids with buyer identities redacted, the executed price, the itemised deductions, the per-member figure, and the certificate confirming the machine was wiped.
7. The cap. No member's rebate can exceed $5,300, the price of a seat. A payout that cannot exceed what you paid is not a profit, which is the point of the cap. Anything above it stays with the company. For that to ever happen the machine would have to sell for more than the entire campaign raised, so treat the cap as a legal backstop rather than a live scenario, and note that we are not going to publish a projection of what the machine will fetch.
8. What it is worth. We do not know. It is whatever a three year old DGX B300 sells for in 2030, and we expect it to be materially less than the seat price. Anyone telling you otherwise, including us, would be guessing.
9. The rebate cannot be assigned, sold, or pledged to anyone else, and neither can a seat. Nobody should be buying a seat as a bet on this clause.
10. No vote on the sale. We may run a non-binding poll on timing or method. The decision is the company's, and members never control it.
11. Unclaimed shares. If we cannot reach you after 12 months of documented attempts, your share goes to named nonprofit pending, an open-source organisation named before the campaign opens. It does not come back to us. We will publish what we tried.
12. If the machine is kept instead of sold, because a second cohort renews on it, members are paid the identical formula against an independent appraisal. Keeping it can never mean you get nothing.
13. Who holds the money. The escrow agent is escrow agent pending, a licensed third party named before the campaign opens, engaged under a written instruction that we cannot vary alone. When we say escrow on this site we mean money held by someone who is not us and who is not free to hand it back to us. If that ever stops being literally true, this clause is where we will have to say so.
14. One cap across everything. The rebate under this section, any refund under section 14, and any refund under section 17 cannot together pay you more than the price you paid for your seat. Whatever the machine sells for, a seat is not capable of returning a gain, and that is the design rather than an accident of the numbers.

If the service ends early

If the node cannot be repaired or kept running and we are forced to sell it mid-term, the machine is sold and the money it raises is what comes back to you. The refund is not a fraction of the seat price. It is the sale.

1. Only when there is no way to continue. This section is for a stop with no repair and no path forward. Everything short of that is repaid in service days under section 10, and a long outage bridges to rented GPUs before it ever reaches here.
2. The machine is sold on the section 13 process, unchanged: mechanical sale, enumerated deductions capped at 8% of gross, proceeds straight to attorney escrow, full dossier published before anyone is paid.
3. The refund escrow is added to the pot, not spent separately. Whatever remains in it on the day we stop goes into the same escrow account and is distributed with the sale money.
4. Split equally, not by months remaining. Every member in good standing on the day service stops receives the same amount. A member who lost 4 months and a member who lost 20 both bought the same seat on the same machine, and dividing the wreckage by how far each of them happened to get through the term would take money from the people who joined the queue earliest.
5. Capped at what you paid, on the same terms as section 13. No refund exceeds $5,300.
6. What we are not promising. A dollar figure. The refund is whatever a used DGX B300 fetches on that date, divided 1,500 ways, and anyone who quotes you a number today is guessing. What is promised is the mechanism: forced sale, published process, published price, attorney escrow, equal split.
7. You hear it within seven days of any decision to wind down, before suppliers and before the press.
8. Runbooks, credentials, and the colocation contract sit in escrow with a named backup operator, so a bus does not end the service the week it hits.

The refund policy works the same ground in more detail, including what it means for the escrow balance we publish every month.

Refunds

The refund policy is part of these terms and reads as if it were printed here. In short: the deposit comes back whenever you ask, the campaign charges nobody unless it funds, you get everything back if the node is not live within six months of the campaign closing, and if the service is forced to stop for good you get an equal share of the machine's sale under section 14.

Separately from all of that, section 19 gives you 14 days from the day you buy to change your mind for no reason at all. That one is a statutory right in the EU and the UK and we extend it to everyone.

What we do not promise

1. Beyond the commitments written in this document, the service comes as it is. We do not promise it fits your particular purpose, and we do not promise the model's output is correct, safe, or original.
2. Published performance figures are measurements, not guarantees. Real throughput moves with what everyone else is doing at that moment, which is the honest cost of sharing one machine.
3. Our total liability to you is capped at what you paid for your seat. We are not liable for lost profits, lost data you did not back up, or business you did not win.
4. The model is somebody else's product. We run it, we did not build it, and we cannot fix it. We do not warrant that its output is accurate, current, safe, lawful where you are, or free of anyone else's rights, and a licence change by whoever released the weights is handled under section 09 rather than pretended away here.
5. Nothing the model tells you is professional advice, and we are not giving any by running it. Medical, legal, financial, and safety questions need a person who is accountable for the answer.
6. Do not put this service anywhere a failure hurts someone. It is one machine, in one building, with a public status page and a 99.0% target. That is honest infrastructure for building software and it is not infrastructure for life support, vehicle control, industrial safety, or anything else where an outage or a wrong answer is a physical risk.
7. None of that limits liability for fraud, for death or personal injury caused by us, or for anything the law where you live does not let us limit. If a clause here is unenforceable where you are, it is severed and the rest stands.

Changes to these terms

1. A material change needs 30 days of notice by email, in plain language, with the old and new text side by side.
2. If a change makes the service materially worse for you and you do not accept it, you get a pro-rata refund for the rest of your term, paid from the refund escrow. That is the check on this clause, and it is deliberate. This is an individual exit while the node keeps running for everyone else, which is why it is priced against the seat and section 14 is not.
3. Three things cannot change at all while your term runs: the price, the length of the term, and the zero-retention architecture.
4. A change the law forces on us takes effect when the law says it does, and we give you as much notice as we are given. We will say which law and show you the text, so you can check that we are not using the word law to smuggle something through.
5. Every version stays online with its date.

Law and disputes

Claims under this agreement are settled by arbitration, one member at a time, rather than in court. That is the standard clause in this industry and we are using it. Read this section instead of skimming it, because you can opt out of the whole thing in 30 days and keep everything else about your seat.

1. Governing law. These terms are governed by the law of jurisdiction pending.
2. Talk to us first. Before either of us files anything, email contact@nodemmunity.com with what happened and what you want done about it. We commit to 30 days of a real attempt at resolution, with a named person on our side rather than a queue. Almost everything that goes wrong should end here.
3. Then arbitration. If those 30 days fail, the claim goes to binding individual arbitration before arbitration provider pending under its consumer rules. Both of us give up a court hearing and a jury for that claim. The arbitrator can award you anything a court could have awarded you individually, including costs where the law provides for them, and the award is enforceable in any court.
4. One member at a time. You bring claims on your own behalf. No class action, no collective or consolidated proceeding, no representative claim, and no arbitration brought for anyone else. This is the part that costs you something, and we are not going to dress it up as a feature. A single-founder company holding 36 months of prepaid money cannot absorb the cost of defending a 400-person action, and the cost lands whether the claim has merit or not.
5. Your 30-day opt-out. Email contact@nodemmunity.com with the words "opt out" and your order reference within 30 days of paying for your seat, and this whole section stops applying to you. Your seat, your price, and every other clause stay exactly as they are, and we confirm the opt-out in writing. The monthly transparency post carries the count of opt-outs. Never the names.
6. Small claims stays open. Either of us can take an individual claim to small claims court instead, for as long as it stays in that court and stays individual.
7. We pay for it. We pay the filing, administration, and arbitrator fees above what filing in your local court would have cost you, unless the arbitrator finds the claim was frivolous. Hearings run on documents or by video unless you ask to be heard in person, and then it happens where you are, not where we are.
8. If many of you file at once. Where 25 or more similar claims are filed within 60 days, they are grouped into batches of 25 or fewer. One arbitrator and one set of fees per batch, with the first two batches decided before the rest go forward, and every deadline paused while that runs. This keeps filing together possible for you and survivable for us.
9. What is carved out. Either of us can go straight to court for an injunction over misuse of the service, of your key, or of intellectual property.
10. If the one-at-a-time rule falls. If a court holds it unenforceable for a claim, this entire arbitration agreement drops away for that claim and it is heard in court. Class arbitration does not happen under this document.
11. Consumer law wins. Consumer protection law where you live applies on top of this document and beats it wherever the two conflict. Where that law makes an arbitration agreement or a class waiver signed before a dispute unenforceable against consumers, which is the position across much of Europe and the United Kingdom, this section does not apply to you at all and your local courts keep jurisdiction.
12. Nothing here touches a claim of fraud, a claim for death or personal injury caused by us, or any right the law where you live does not let you sign away.

Your rights as a consumer

Consumer law where you live sits on top of this document and beats it wherever the two disagree. If a clause above appears to take away a right the law gives you, the clause loses. That is not generosity, it is how the law works, and a contract that pretends otherwise is telling you something about the people who wrote it.

1. Fourteen days to change your mind. You can cancel your seat for any reason within 14 days of buying it, without explaining yourself. In the EU and the UK this is a statutory right on a distance sale. Everywhere else we give you the same window on the same terms, because running two rules for one product would be worse than the cost of the rule.
2. If nothing has been delivered yet, you get all of it back. During the campaign and before launch there is nothing to deduct, so a cancellation inside the window returns the full price, including the $1.88.
3. If you asked us to start first. If the node is already serving you and you cancel inside the window, we keep only what was actually delivered: the price divided by 1,095 days, times the days served, rounded down. On a $5,300 seat that is about $4.84 a day. We do not charge a cancellation fee on top, because there is nothing for one to pay for.
4. How to use it. Email contact@nodemmunity.com and say you are cancelling. Any clear wording does it. A cancellation form is on the refund page if you prefer one, and you are not required to use it. Money goes back within 14 days of us hearing from you, by the route it arrived.
5. What it is not. It is a cooling-off right, not a rolling exit. After 14 days the refund policy is what governs, and it is deliberately specific about which situations pay and which do not.
6. Statutory rights we cannot write away. Rights about description, quality, and fitness, the right to a remedy when a service is not delivered as described, and the protections your law gives on unfair contract terms all survive this document intact. Section 16 limits what we promise beyond them. It does not reach them.
7. Where to complain other than to us. Your national consumer authority is open to you at any point and does not need our permission. Once the company is registered we will name an approved dispute scheme at ADR scheme pending and publish how to reach it. Section 18 covers what happens between us before anyone gets that far.

Things outside our control

Some failures are nobody's fault, and a contract that refuses to say so ends up being read as one that will blame the buyer. This section says which failures those are, and it is deliberately short on excuses.

1. What counts. War or civil emergency, natural disaster, fire or flood in the datacenter, a national power or network failure, a government order, an export control change that makes serving you unlawful, a law that makes running the model unlawful, or the collapse of a supplier we could not reasonably have replaced in time.
2. What does not count. Running out of money through ordinary mismanagement. Failing to plan for a lead time we knew about. Picking a cheap supplier and being let down by them. A fault we could have fixed and did not. None of those become acts of God because they were expensive.
3. What happens. The days are added back. An event under this section is repaid in service days on the same mechanism as an outage under section 10, for all 1,500 members at once, and we tell you what happened within seven days rather than letting the status page speak for us.
4. If it does not resolve. If an event under this section stops the node for more than 120 consecutive days with no realistic route back, section 14 takes over: the machine is sold and the proceeds come back in equal shares. We do not get to keep prepaid money for a service we cannot deliver, whoever was at fault for the stop.
5. This clause excuses delay, never the refund. Nothing here suspends section 14, section 19, or a statutory right.

Ending a seat early

1. You can walk away at any time. Tell us and we close the seat. Outside the 14 days in section 19, closing it does not by itself produce a refund, because the machine was bought outright on the strength of 1,500 people saying they wanted it. The refund policy lists every case where money does come back, and there are five of them.
2. A closed seat stays one of the 1,500. We may offer it to the waitlist at the same price. What we will not do is grow the number, because the whole capacity argument on the landing page is arithmetic against 1,500.
3. If you die or lose capacity. A seat cannot be inherited, because it is one key for one person. Your estate can close it on evidence, and the unused part of the term is refunded pro rata from the refund escrow, on the same basis as an exit under section 17. We would rather write this clause now than improvise it on the day.
4. If we end your seat for breach, section 08 governs how, and the refund policy says what it costs you. Confirmed resale is the only breach that costs you everything.
5. What survives. Sections 12, 13, 16, 18, 22 and 25 keep working after a seat ends, for as long as they need to.

What you are responsible for

1. Your key. Keep it secret. Tell us within 72 hours if it leaks. Usage on your key counts as yours until you tell us, and stops counting as yours the moment you do. We will not treat a reported leak as a resale, and we will not bill you for traffic after the report.
2. What you build. Whether what you build is lawful, safe, and properly licensed where you ship it is your call. We do not review it, we cannot see it, and section 07 is about conduct rather than subject matter for exactly that reason.
3. If someone brings a claim against us because of what you did. Where a third party comes after us because you deliberately broke section 07 or did something unlawful with your seat, you cover our reasonable direct costs of dealing with it. The limits on that are real: we have to tell you promptly, we cannot settle without asking you, only costs actually incurred count, ordinary mistakes are not covered, and it never goes further than the law where you live allows a consumer to be held. This is here to cover the member who runs an attack from their key, not the member who ships a bug.
4. Your details. The email on your account is how every notice reaches you, including the ones about money and the ones with deadlines attached. Keeping it current is on you, and section 24 explains what we do when it bounces.

If the company changes hands

1. You cannot transfer your seat. Section 05 gives the reason and it has not changed.
2. We can transfer this agreement only with the machine, and only whole. If the company is sold or merged, or the node passes to someone else, your seat moves across with its price, its term, its rebate, and its escrow untouched. A buyer who will not take all of it does not get any of it.
3. You hear 30 days before. Who is taking over, what they have committed to, and in writing. If the buyer wants the terms changed, that is a material change and section 17 gives you the exit and the refund that comes with it.
4. If we become insolvent. The refund escrow is held by a third party under an instruction we cannot vary alone, so it should sit outside the company's estate. We write should rather than will because insolvency law decides that question and we do not. What we can control we have: the runbooks, credentials, and the colocation contract already sit with a named backup operator under section 14, so the node can keep serving while the rest is sorted out.
5. No quiet handover. If the operator changes, the monthly transparency post says so in the month it happens.

Notices

1. To you. Email to the address on your account, and for anything that affects all 1,500, a post on the public status page as well. A notice counts as given on the day we send it.
2. If your email bounces. We try twice more over 14 days and post the notice publicly. A dead address does not pause a deadline, which is why section 22 asks you to keep it current, but it also does not cost you your rebate: section 13 gives unreachable members 12 months and a documented search before anything moves.
3. To us. contact@nodemmunity.com, which one person reads. We acknowledge within two business days. From incorporation the registered postal address is published at registered address pending and anything formal can go there instead.
4. Language. This agreement is in English. If we publish a translation and it disagrees with the English, the English governs and we fix the translation.

How the three documents fit

1. Three documents, one agreement. These terms, the refund policy, and the privacy notice are the agreement between us. If something we said somewhere else contradicts them, in a post, an email, a campaign page, or a conversation, tell us: we will either fix the document or correct the statement. We do not get to use this clause to escape something we plainly told you in order to sell you a seat, and nothing here limits our responsibility for a statement we made to get your money.
2. Which document wins. The refund policy governs refunds, the privacy notice governs data, these terms govern everything else. Where two say the same thing in different words, the reading better for you applies.
3. Kickstarter. Until the money reaches us, your pledge lives under Kickstarter's terms, which we did not write and cannot change. From the moment funds arrive and a seat exists, this agreement governs. Section 03 of the refund policy covers the handover.
4. Severability. If a clause is unenforceable where you live, it is cut out and everything else stands.
5. No waiver. If we do not enforce something once, we have not given it up. If we choose not to enforce it repeatedly, we should probably delete the clause, and you can ask us to.
6. Nobody else can enforce this. The agreement runs between you and the company. No third party takes rights under it.
7. Every version stays online, dated, with a note of what changed. Nothing gets edited quietly.

The status of this draft

This is a draft, published early on purpose. No company exists yet, no seat has been sold, and nothing here binds you or us today. The reservation deposit is covered by the refund policy and creates no obligation beyond that $1.88.

Draft 2, published 31 July 2026, adds sections 19 to 25 and tightens sections 01, 03, 10, 11, 12, 13, 16 and 17. The additions are the ordinary furniture of a service contract that draft 1 was missing: a cooling-off right, force majeure, what happens when a seat or a company ends, who is responsible for what, how notices work, and which of the three documents wins when they disagree. Nothing in the commercial deal moved. The price, the term, the fair-usage numbers, the rebate, and the refund triggers are the same as they were.

Before the campaign opens, a lawyer reviews the whole document and a securities lawyer signs off on section 13 specifically, because sharing sale proceeds sits closer to the regulatory line than a fixed rebate would. If that review changes the deal, we will say what changed and why, rather than quietly swapping the text.

Read something here that seems unfair or unclear? Write to contact@nodemmunity.com. Fixing it now costs a paragraph. Fixing it in year two costs trust.