Security & Compliance

This page describes how CommandEditor protects documents and is intended to help security and procurement teams evaluate the product. The short version: because your files are processed entirely inside your browser and are never uploaded, most of the usual risk surface simply does not exist.

1. Architecture — everything runs on your device

CommandEditor is a client-side application. Merging, editing, converting, OCR, signing, redaction, encryption and every other operation execute in your browser using JavaScript and WebAssembly. The website is served as static files from a CDN; there is no server that receives, processes, or stores your documents. The optional desktop app (Windows, macOS, Linux) runs the same engine fully offline.

2. Data handling — no uploads, verifiable

Your documents are never transmitted to CommandEditor. To let you confirm this rather than take it on trust, the built-in "Proof of No Upload" tool monitors the page's outgoing network activity so you can see that your file bytes never leave the device. Small preferences (such as dark mode and recent file names) are kept only in your browser's local storage and can be cleared at any time.

3. Cryptography

Security features use standard, audited primitives provided by the browser's Web Crypto API: AES-256-GCM for encryption, PBKDF2 for password-based key derivation, ECDSA on the P-256 curve for e-signatures, and SHA-256 for integrity hashing. Blockchain notarization uses the open OpenTimestamps standard, where only a SHA-256 hash — never the document — is anchored.

4. Application & transport security

The site is served exclusively over HTTPS with HSTS (preloaded). It ships a strict Content-Security-Policy, sets X-Frame-Options: DENY and frame-ancestors 'none' (clickjacking protection), X-Content-Type-Options: nosniff, a restrictive Permissions-Policy, and object-src 'none'. Untrusted HTML (for example, files you convert or AI output) is sanitized before rendering to prevent script injection. There are no advertising scripts and no cross-site tracking cookies; the only analytics used is privacy-friendly, cookieless and aggregate (see section 8).

5. Data protection & GDPR

CommandEditor collects no personal data on any server, has no user accounts, and performs no server-side logging of your files. Because processing is local, the product supports data-minimization and purpose-limitation principles by design. Standard technical request metadata (such as IP address) may be logged by the static host for reliability and security, and is never linked to document content, which never reaches the server.

6. Healthcare (HIPAA) posture

Protected health information (PHI) placed into CommandEditor is processed on your device and is never received by CommandEditor. Practically, this means a Business Associate Agreement is not applicable, because CommandEditor is a client-side utility rather than a business associate that handles your data on your behalf. CommandEditor is not itself a certified or covered entity; whether a given workflow is HIPAA-compliant depends on your own environment and controls. We are glad to support security questionnaires with the details on this page.

7. Enterprise controls (no cloud account required)

For regulated and enterprise use, CommandEditor provides on-device controls that need no backend: configurable policy presets, a chain-of-custody log, per-recipient document fingerprinting for leak attribution, tamper-evident seals, and a downloadable cryptographic audit trail for signatures. These operate entirely within your browser or the desktop app.

8. What CommandEditor deliberately does not do

No advertising, no cross-site tracking, no account requirement, no server-side copies of your files, and no transmission of document content to any third party (including for AI, which runs locally). For product insight we use privacy-friendly, cookieless, aggregate web analytics that count only anonymous page views and app installs — never your files, never personal data, set no cookies, and nothing fires during document processing (you can confirm this yourself with the Proof of No Upload tool).

9. Vulnerability disclosure

We welcome responsible disclosure of security issues. Please email hello@commandeditor.com with details and steps to reproduce; please avoid publicly disclosing an unpatched issue. A summary security policy is also published in the project repository.

10. Contact

Security and compliance questions can be sent to hello@commandeditor.com.

This document describes the product's design and controls for transparency and does not constitute legal or compliance advice or a warranty.