A deliberately limited public surface.

Nardux uses a static-first website, minimal public data collection and a separate readiness gate before any engagement receives access to sensitive client systems or content.

Current safeguards around a small attack surface.

Status applies only to the named control and environment. Staging evidence does not establish production or client-data readiness.

IMPLEMENTED

Static public pages

  • No public client database
  • No public account or login
  • No public file upload
  • No payment collection
  • Minimal website dependencies
IMPLEMENTED

Source and release controls

  • Private Git repository
  • Pinned dependency lockfile
  • Reproducible static build
  • Navigation and content checks
  • Browser evidence retained
VERIFIED IN STAGING

Edge delivery

  • TLS and canonical redirects
  • Security and cache headers
  • Protected staging access
  • Controlled release artifacts
  • Rollback procedure exercised

Controls must be configured and evidenced before they become claims.

IDENTITY

Accounts and access

Company-controlled accounts, strong MFA, separate recovery, least privilege, access review and prompt revocation.

ENDPOINTS

Devices and work practices

Supported software, encryption, screen lock, approved tools and no unapproved client-data sync or AI use.

WEB

Hosting and form protection

HTTPS, security headers, strict server validation, bot controls, rate limits, safe failures and minimized logs.

DATA

Client separation and retention

Necessary access only, approved storage and transfer, per-client boundaries, documented retention and deletion evidence.

MONITORING

Detection and response

Configuration alerts, safe operational logs, delivery reconciliation, incident records and accountable escalation.

RECOVERY

Continuity and rollback

Configuration exports, tested backups, immutable releases, service fallbacks and restoration exercises.

Public-site controls do not authorize moderation data.

Nardux will not treat the public website, ordinary email or a generic file-sharing link as an approved route for user-generated content, case evidence or restricted client-system data.

Before that work begins, the engagement requires appropriate contracts, managed devices and identities, approved workspace and vendors, client separation, access review, retention and deletion, incident handling, reviewer safeguards and tested operating controls.

Do not send passwords, access tokens, user content, case evidence or sensitive incident details through the public enquiry form.

No tool is approved by popularity alone.

A vendor decision considers data categories, purpose, permissions, subprocessing, location, retention, deletion, security, incident duties, export, recovery and contract terms.

Business owner and backupData-flow and necessityRoles and permissionsContract and privacy reviewRetention and deletion testLogging and support accessIncident notification pathExit and export capability

Use a minimal first message.

Email admin@nardux.com with a plain-language summary, the affected public page or system, approximate time and a safe way to contact you.

Do not include exploit code, credentials, personal information, user content or sensitive evidence in the first email. Nardux does not currently operate a public bug-bounty program or promise a response-time SLA.

Current-state questions.

What evidence can procurement request?

For a qualified opportunity, Nardux can provide current website, release, access, privacy and operating information appropriate to the proposed scope. Sensitive evidence may require an NDA and approved exchange method.

Can we send sample moderation cases by email?

Not before an approved data-sharing method and engagement controls exist. Use synthetic or redacted context during early qualification and do not send user content through the public form.

Does Nardux have a client portal?

No. Avoiding a public portal keeps the current attack surface smaller. Approved business tools can be selected only after access, privacy, security and operational review.

How are security claims qualified?

Each answer identifies the relevant environment, evidence and limits. A website or staging control is not presented as proof that every future client workflow uses the same control.

Ask for the evidence relevant to your proposed scope.

Begin with the system, data category and control question without attaching sensitive material.

Email Security