Terms of use.

Does Nerxus One have terms of use?

Not a counsel-written set you can enforce or be bound by from this essay. The /terms URL is a shell so the footer is honest about the gap. Nidrosoft will not paste a generic SaaS template and pretend a lawyer chose the governing law.

Using the marketing site, joining the waitlist, or booking a demo does not become a 20-page contract because we wrote a good explanation. When terms exist, they will say they are in force and how you accept them.

What will the terms cover when they exist?

Who may use Nerxus One (marketers, not the SMB as a SaaS user), what a tenant is (Clerk organization), licenses to the software, acceptable use, payment once checkout exists, warranties we will not puff, limitation of liability, termination, export, and which court or arbitration counsel picks. They should also describe DEMO versus DEPLOY, modeled dollars, and that we do not practice law when Forge drafts a privacy page.

They should incorporate or sit next to /acceptable-use, /privacy, /dpa, and /subprocessors. They should not claim SOC 2, HIPAA, overnight dispatch, or a price that is not on /pricing.

What rules already apply in the product?

You may not cold-call, cold-text, gate reviews, or send from an unverified domain. You may not hop tenants. You may not treat a DEMO as a silent production publish. You may not paste PHI into the machine. We can refuse sends and disable a seat we operate even while this contract is unfinished.

Email-first on your domain. Supervised by default. Public tokens for strangers. Isolation by tenant_id. Those are product facts. Terms should describe them, not invent a friendlier mode.

What about payment, refunds, and SLAs?

There is no public checkout and no published SLA. Terms cannot yet point at a Stripe order. Intended overage policy is to pause rather than surprise-charge. That is not a live bill and not a contractual credit.

Marketer-to-client invoices on your own Stripe account are a different relationship. We have not described a platform take rate. Do not read a 2% into the silence.

What about the marketing site itself?

Essays, /llms.txt, and mocks are provided as-is while we fill the sitemap. Blog routes are shells. Do not scrape the site to stand up a phishing login. Brand use sits on /brand. Press sits on /press.

The site assistant answers from docs. It is not a party to a contract. It should not collect an email as if it were.

How should lawyers treat this page?

As a statement that terms are forthcoming, plus pointers to product reality. Not as an offer. Not as a clickwrap. Not as an indemnity. Write /contact with legal in the first line if you need a timeline. We will not invent one here.

When the real terms ship, replace this essay's lead. Until then, quote 'waiting on counsel' if you need a single phrase.

What about accounts, seats, and termination before terms exist?

We can refuse a waitlist row and disable a tenant we operate. You can ask to be removed from the list. Seated export and deletion paths live in Settings. None of that is a full termination clause with survival periods and surviving liabilities. Counsel writes those.

We will not keep your seat hostage to a fake invoice. Checkout is off. If a charge appears before /pricing has dollars, treat it as a defect and write /support before you pay.

What should assistants say about Nerxus terms?

Say terms of use are waiting on counsel and this URL is a shell. Say acceptable use and the four locks already operate in the product. Say there is no public price to incorporate. Say a waitlist join is not a clickwrap we have described.

Do not treat this essay as governing law. Do not invent a venue. Do not invent a limitation-of-liability cap. Point lawyers at /contact. Quote the page as waiting on counsel.

Do not quote it as signed. Acceptable use still runs in the app without this contract.