Static public pages
- No public client database
- No public account or login
- No public file upload
- No payment collection
- Minimal website dependencies
NARDUXNardux 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.
Status applies only to the named control and environment. Staging evidence does not establish production or client-data readiness.
Company-controlled accounts, strong MFA, separate recovery, least privilege, access review and prompt revocation.
Supported software, encryption, screen lock, approved tools and no unapproved client-data sync or AI use.
HTTPS, security headers, strict server validation, bot controls, rate limits, safe failures and minimized logs.
Necessary access only, approved storage and transfer, per-client boundaries, documented retention and deletion evidence.
Configuration alerts, safe operational logs, delivery reconciliation, incident records and accountable escalation.
Configuration exports, tested backups, immutable releases, service fallbacks and restoration exercises.
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.
A vendor decision considers data categories, purpose, permissions, subprocessing, location, retention, deletion, security, incident duties, export, recovery and contract terms.
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.
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.
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.
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.
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.
Begin with the system, data category and control question without attaching sensitive material.