Protect the people who
protect the internet.

Moderator safety is the discipline of protecting content reviewers from the psychological toll of their work. ZYX+ is the safety gear on the job: we transform distressing content in real time into a neuro-tolerant form, so each moderator can see and decide without stress.

None. No installs, no brain implants, no wearables, no cameras, no biometric sensors, and no extra capex. ZYX+ slots in as a plug-and-play layer that respects each platform’s governance and workplace rules, with no change to your existing review tool (e.g., Software Review Tool, any internal stack). Content is transformed, ready to be reviewed by moderators. Ain’t it simple?

With explicit consent from both the moderator and the platform, ZYX+ captures telemetry to improve each moderator’s neuro-tolerance calibration. Supervisors only see aggregates such as team-level tolerance shifts and content-transformation volume. What an employer gets is proof the team is being protected, plus improvements in SLAs, decision quality, and moderator feedback. ZYX+ never captures any PII, PHI, or biometric data.

Current solutions don’t fix the root cause: affective content. They rely on recurring moderator backfills (~80% turnover) and patchy Employee Assistance Programs (EAPs) that reach only 7% of moderators. The adverse impact still reaches 100% of moderators — and the harm stays in memory.

ZYX+ goes at the root cause head-on — calibrates affective content to each moderator’s neuro-tolerance, neutralizes harmful impact at every view.

EAPs live in the wellness budget. ZYX+ lives in operational expenditure — because protecting moderators isn’t a perk, it’s safety equipment.

“Shell shock” is the operational reality moderators describe and rate quantitatively. We use the term and the ratings plainly — but we treat the underlying claim as something to prove through neuroscience-based research, not assert.

To build that proof, we are:

• Collaborating with the Wharton Neuroscience Initiative on an ongoing research study validating the neurological impact of content transformation on reviewer strain. Findings are not yet published, and we won’t market preliminary results.
• Designing the operational evidence framework — tolerance calibration over time, SLA adherence, and decision quality under load — to be validated in the first pilots with founding platform partners.

Our pilot standard: until the research lands we remain data-conservative, and we’ll publish the findings when it does. The only numbers we’ll show you are the ones generated by your own workforce in pilot.

ZYX+ is pre-launch. The product is working end-to-end as an API-first transformation layer that sits in front of any review queue — moderators’ existing consoles don’t change. The research backbone is in place through our collaboration with the Wharton Neuroscience Initiative. What we’re doing now is choosing our founding platform partners — the first one or two trust-and-safety teams to pilot ZYX+ in production, with the first-mover advantage that carries.

If your platform has a moderation workload today and you’re open to piloting — and shaping — a safety layer like this in production, that’s the conversation we want to have. Founding partners get:

• Hands-on engineering from us on the integration
• Direct influence over the product roadmap
• Preferred commercial terms for the life of the contract
• Co-authorship visibility on any published operational findings, subject to their preference on disclosure

Integration details — deployment pattern, data residency, latency targets, failure-mode posture, SLAs — are defined together with each founding partner. We’d rather get that right for one platform than write a glossy connector list we can’t yet stand behind.

Pricing is usage-based and shaped around the levers that actually drive both our cost and your safety value. We’re deliberately not publishing a standard rate card while we’re in the founding-partner phase — the first one or two contracts set the benchmarks everything else is priced against, and we’d rather price honestly per partner than publish a number we’d later contort around.

Pricing is built on five levers:

• Content volume — number of items transformed per month (videos, images, text, audio)
• Latency tier — real-time (synchronous, in the reviewer’s flow) vs. batch (asynchronous queue processing). Real-time carries more compute and more cost.
• Auto-decisioning — whether ZYX+ returns every transformed item for unassisted moderator decision, or auto-reasons policy-clear cases and routes them to a moderator for approval or override (faster per-item decisions, audit-clean human-in-the-loop)
• Deployment shape — shared multi-tenant, dedicated cloud region, or data-residency-constrained deployment
• Coverage & service tier — content types covered, SLA target, and level of integration hands-on support

Founding partners lock in their contract rate for three years, starting at 50–100 moderators and scaling upward from that floor over the term. Seats move with you across internal teams, sites, or BPO vendors, and the contract transfers through M&A or corporate restructuring — no re-negotiation when the work or the entity changes hands. ZYX+ is designed for platform-scale moderation workloads, not individual teams.

Numbers live in the conversation. Contact us for a quote scoped to your content mix, review volume, and deployment constraints.

ZYX+ is pre-certification — and deliberately so at this stage. SOC 2 Type II and ISO 27001 audits require an observation period that runs against live production traffic at contracted scale. We will pursue them alongside our first founding-partner production deployment, not before — because an audit report without production workload behind it is a marketing document, not a proof point.

What we’ve built instead is an integrity-driven compliance posture that matches where ZYX+ actually is today:

What founding partners get today:

• A bilateral Data Processing Agreement (DPA) on contract
• Custom infosec review with the partner’s security team before go-live

For a specific regulation or audit framework not listed here, ask. We’d rather tell you “not yet” than claim coverage we don’t have.