Cloudflare edge and response protection
Cloudflare delivers the site with HTTPS and edge protection, while restrictive content, framing, referrer, capability, and cross-origin policies reduce browser-side exposure.
Security
Security for the website, licensing, and software updates
Eigenexis Systems protects this public website with Cloudflare edge controls, restrictive response policies, server-side validation, and private application storage reserved for a separately gated early-access workflow. The unreleased desktop product has its own planned security model for licensing and updates: signed entitlements, device-bound activation, and signed, hash-verified packages. That model is designed and implemented in the Eigenexis licensing platform and must still pass product qualification before release.
01
Context
Security for the production website and protected intake
The production site uses HTTPS, DNSSEC, restrictive content and framing policies, same-origin boundaries, and security headers across pages, assets, redirects, API responses, and errors. It sets no cookies and loads nothing from third-party origins.
The gated early-access path was qualified with synthetic data: requests are bounded and validated on the server, with replay and abuse controls, scheduled retention cleanup, structured operational events, and rollback procedures. Real applicant intake remains disabled.
No system can be guaranteed impossible to compromise. These safeguards reduce defined risks and require continuing verification as the service changes.
02
Workflow
How website information is protected
- 01
When the separate intake gate is enabled, the endpoint will accept only approved same-origin JSON requests with the expected method, fields, consent version, and bounded values. Unexpected or malformed requests receive generic responses.
- 02
When registration reopens, accepted records will use private server-side application storage. The browser receives no database credentials or record-reading authority, and the application record excludes payment information, browser fingerprints, forwarding headers, and IP addresses.
- 03
Expired application data and short-lived protection state are removed by a deployed schedule. Structured security events and tested recovery procedures support operational review without logging applicant fields or secrets.
03
Scope
Verified website security layers
Gated intake and data protection
When enabled through a separate operational gate, same-origin controls, bounded inputs, schema validation, consent, replay resistance, abuse controls, private storage, and generic errors protect the request path.
Monitoring and recovery
Structured events, scheduled cleanup, dependency checks, deployment verification, and tested rollback procedures support maintenance and recovery without claiming continuous human monitoring.
04
Licensing and updates
The planned licensing and update security model
This model is designed and implemented in the Eigenexis licensing platform and application client library. It has not shipped in a released product and has not been independently audited, so it is described here as planned product behaviour.
Signed entitlements verified with public keys
Licences reach the application as entitlements signed by the licensing service. The application verifies them with public keys delivered through a root-signed keyring; it can cache an entitlement but can never create or widen one.
Private keys never ship in the application
Signing keys exist only in the licensing service's secret store or in offline custody. No private signing key is included in the application, the installer, or any package.
Device-bound activation
Each activation is bound to a key generated on the device, hardware-protected where Windows supports it, so copied licence state does not carry the licence to another machine.
Signed and hash-verified packages
Every package is listed in a signed release manifest and described by its own signed statement. Downloads are checked against their declared size and SHA-256 hash and are never run before verification.
Updates verified before install
Release manifests carry increasing serial numbers and expiry times to resist rollback and freeze attacks, and installation is transactional, so an interrupted update is rolled back.
Licensing never holds documents hostage
Viewing, rendering, navigation, search, selection, printing, and saving never require a licence. If licensing fails, editing features pause while documents remain accessible.
05
Who it is for
- Future customers reviewing how licensing, updates, and documents will be protected
- Security researchers seeking a responsible reporting path
- Engineering organizations assessing current website controls and unreleased product boundaries
06
What is not claimed
No system can be guaranteed impossible to compromise. Controls reduce defined risks, require maintenance, and must be revalidated when infrastructure or product behaviour changes.
A monitored security mailbox is not yet operational, so the disclosure policy remains an interim reporting boundary and real applicant intake remains disabled. Website safeguards and the planned licensing design are not evidence of released-product security.
07
Questions
Questions about security
No. Implemented controls reduce defined risks, but security requires continuing maintenance, monitoring, testing, and accurate disclosure of residual risk.
The planned design prevents that: entitlements are signed by the licensing service, verified with public keys, and bound to a device key, and the signing keys never leave Eigenexis custody.
Read the vulnerability-disclosure page and follow its current reporting boundary. A monitored private mailbox is still being commissioned, so do not transmit non-public vulnerability details until that page and security.txt publish a verified reporting address.
Own the PDF editor you use every day.
One price, once: a perpetual licence for a local-first PDF editor on Windows. The price is published now; purchasing opens at launch.
See pricing