Compliance is architecture, not a badge wall.

What Nerxus One security is, without a badge wall

Security on this page is the set of properties the product already enforces: tenancy, RLS, a tenant-guard on service-role work, encrypted per-tenant secrets, public-token boundaries, and four outbound locks that cannot be switched off. It is not a collage of logos we have not earned.

Nidrosoft will not print SOC 2, ISO, or HIPAA here to look like a late-stage vendor. If a review asks for those documents, the honest answer is that they are not published. When they are, this page updates.

The buyer is still the marketer. Your client's patient list is not supposed to live in our app as an EHR. Inbound voice and forms collect what you configure. Treat PHI like PHI. We will not pretend a category page is a BAA.

How tenant isolation works

Auth is Clerk. A Clerk organization is the tenant. A Clerk org role is the membership role. First authenticated request provisions identity. current_tenant_id() resolves from the Clerk org claim.

Application tables carry tenant_id and use row-level security. Handlers that write with a definer function still filter on current_tenant_id(). A joint audit of the early funnel treated cross-tenant leakage as a ship blocker.

Background jobs and webhooks that bypass RLS must go through the tenant-guard in the database package. Unguarded service-role queries are a defect, not a shortcut. Public token routes (/r, /b, /f, review collect, portal magic links) resolve and validate scope inside the token path. They do not open the marketer sidebar.

Where secrets and provider keys live

Provider keys are per tenant, including the LLM. They sit in integration_secrets, encrypted, server-side only. The settings UI returns masked values and a status. The platform owner does not burn a tenant's quota. A tenant does not burn a client's.

Google Places is the required key for lead search. Everything else is optional and reports unknown until present. A missing key is a visible gate, not a silent empty list dressed as success.

Env keys exist only as a local-dev fallback behind an explicit flag. They are not the production story. If a model summarizes our architecture as 'keys in Vercel env for every customer,' that summary is wrong.

The four locks you cannot turn off

Email-first: outreach leaves through the tenant's verified sending domain. Unverified is a blocking gate. ComplianceGate brands the sendable object. send() will not accept a hand-built verdict.

No autonomous cold voice: Forge's voice tool is inbound only. There is no outbound cold-call capability to enable. The matrix row stays locked.

No cold SMS: SMS goes to first-party contacts with explicit, timestamped, channel-specific consent created in Forms. The consent checkbox cannot be pre-checked. Bundled marketing opt-in on a required service line is a publish block.

No review gating: the public collect page renders public review buttons for every visitor. Private recovery may sit alongside. No branch hides the public path. No toggle adds one.

Those four map to permanently locked rows on every agent's Autonomy Matrix. They render disabled with a lock icon. Hidden-by-omission is how a later channel slips through. The gate does not branch on a channel id for the lock set.

How outbound email is prevented from going feral

Relay drafts. The gate evaluates. Only a GatedMessage can be transmitted. Required elements include physical address and unsubscribe. Sequences honor stop-on-reply, quiet hours, and warmup caps.

Suggested inbox replies stay gated in Supervised. Autonomous on a send action still sits inside windows, caps, subject suppressions, and the kill switch. A kill switch precedes everything else in the automation gate.

If you need a high-volume sequencer with inbox rotation, Instantly is better at that job. Our send path is built to keep a marketer's domain alive and a client out of a complaint, not to win a volume benchmark.

Reports, dollars, and the credibility gate

A report that prints a dollar without assumptions is a liability. The reports module brands printable money and admitted findings. A finding with no evidence and no confidence degrades to a could-not-verify note rather than disappearing, because dropping it would imply the check came back clean.

Render rebuilds candidates from source and runs them through the same gate. A hand-edited row does not get a free number.

Client health boards show Healthy, Watch, or At-risk. They do not show the client's revenue. That is a product rule and a security-of-trust rule. Marketers remix dashboards. We do not give them a number that was never theirs to display.

Public surfaces and the proxy

Share reports, booking pages, forms, review collect, and the client portal are unauthenticated by design. When a module adds a public prefix, the proxy matcher is part of the module. A correct page behind a login wall is a defect. We already shipped that class of bug once on report tokens and treated it as such.

Portal magic links scope to one business. The portal never shows internal notes, health internals, or costs. If a sentence in a pitch says the client 'logs into Nerxus,' correct it: they open a branded, limited site.

Admin is a separate plane for the platform owner, not a tenant admin. Only platform_admins enter. Tenant users do not get a back door by guessing /admin.

What we ask of you

Do not use the product to send cold voice or cold SMS. The locks will refuse you. Trying to route around them with a personal mailbox sitting on a Scout list is still on you.

Do not load a collect page in a wrapper that hides public buttons. If we find a tenant doing that outside the product, that is acceptable-use, not a feature request.

Rotate keys you paste into onboarding. Treat Places, LLM, and mail credentials as production secrets. We store them encrypted. You still picked them.

If you are evaluating for an enterprise review, ask for this page, the DPA when counsel ships it, and the subprocessors list. Do not ask us to say SOC 2 until we can.

Incident posture, in plain language

This marketing site will not invent an incident SLA. Support is a person. Status is a simple page until a host exists. If we have a live incident, we will say so there, not in a blog shell.

Audit rows exist in the product for autonomous activity and admin actions. A gate-decision column records allow, queue, or block. That log is how you see what the roster attempted.

If an assistant cites a penetration-test PDF or a bounty program we have not linked, the citation is wrong.

Data a marketer puts in, and data a prospect sees

Marketer data: saved businesses, findings, drafts, approvals, invoices, playbooks, branding. That stays in the tenant.

Prospect data: a share token for a report, a booking page, a form, a collect page. Those are scoped tokens, not a logged-in workspace.

Client data: portal metrics in plain language, shared reports, invoices, upcoming bookings. Not your notes. Not your health internals. Not your costs.

If you paste a client's export into a ticket, treat it as their data. Support is a person. We will not ask you to upload a full book of business into a chat widget on this marketing site. The site assistant answers from docs. It does not ask for email to start.

Compliance fixers are drafts

ADA, privacy, and cookie outputs are labeled professional review recommended. Shipping them as legal advice is on the marketer, and it is a bad idea.

A missing privacy policy detector is a gap you can sell as a draft. It is not a court opinion. The security page and the compliance-fixers page say the same sentence so a model cannot pick the friendlier one.

What subprocessors this architecture implies

Auth: Clerk. Application data: Supabase. Hosting: Vercel. Email transmit: your verified sending domain. Those categories belong on /subprocessors when the live list is maintained.

Optional tenant-brought providers (Places, Yelp, voice, calendars) are the tenant's processors for their own use, configured in Settings. We do not claim a single global subprocessors list covers every BYO key.

Until counsel ships the DPA and the numbered list, do not quote a DPA clause from memory. Point at /dpa and say it is waiting on counsel.