Small attack surface
Static pages plus one lead form are easier to defend than a rushed dashboard, payment portal, or public decryption service.
Security model
A controlled public surface with private implementation depth.
The public website is intentionally restrained: no signups, no file uploads, no public encryption API, no exposed customer portal. Serious security work happens in controlled customer environments.
Website security
Public website hardening
The domain is deployed as a mostly static site with a narrow PHP enquiry endpoint, strong response headers, no directory browsing, and no public upload path.
Security headers
The deployment uses content security policy, frame protection, content-type protection, referrer policy, permissions policy, and HTTPS redirection where supported.
Controlled enquiry handler
The form includes honeypot friction, a human challenge, rate limiting, input limits, header-injection controls, and no file attachments.
No secret intake
Visitors are told not to submit passwords, classified data, private keys, or sensitive files through the public website.
Customer controls
Implementation security controls
Customer deployments can be built around stronger controls than a public marketing site can safely expose.
HSM and KMS integration
Hardware security modules, cloud KMS, offline root keys, split roles, key ceremonies, emergency recovery, and key rotation can be included.
Identity and approval workflows
Role-based access, privileged-user approval, device posture, MFA, break-glass policy, and dual control reduce misuse.
Tamper-evident logs
Hash records, provenance metadata, signature records, quantum evidence references, and immutable log storage can support investigations.
Post-quantum readiness
A crypto-agility roadmap can plan for NIST post-quantum algorithms, hybrid key exchange, inventory, migration, and long-term confidentiality.
Credibility
Assurance boundary
QuantumEncryption1 uses quantum-cloud evidence as part of the audit workflow while keeping file confidentiality grounded in vetted cryptographic engineering.
No unbreakable claim
The service focuses on risk reduction, high assurance, and controlled implementation rather than absolute security promises.
IonQ evidence role
An IonQ job ID proves provider acceptance of a circuit job and supports a seal record. File confidentiality remains a cryptographic engineering matter.
No public secret handling
Secrets belong in controlled customer systems, not a marketing form or generic public portal.
Crypto-agile architecture
Algorithms, vendors, and key-management systems should be able to change as standards and requirements evolve.
Confidential introduction
Review the security model for your organisation.
Approved organisations can request a threat-model workshop and implementation plan.