IncomiQ Logo INCOMIQ SecureDoc Free Windows Release
Free Public Release

SecureDoc is now
free to download.

SecureDoc is IncomiQ's own security-focused Windows plain-text editor. This free release is built to keep sensitive text inside SecureDoc by default, reduce readable plaintext exposure in memory, save only encrypted document data, and avoid handing normal in-app copy/paste to the Windows clipboard.

By default, SecureDoc keeps the open document encrypted in memory while you edit it. Normal in-app copy and paste stays inside SecureDoc through its own encrypted clipboard, and other applications running with normal user privileges are blocked from directly opening SecureDoc's process memory for reading.
Download Free → View Technical Details

Your text stays inside SecureDoc by default. It can leave SecureDoc when you deliberately use a lower-security action, such as copying to the Windows system clipboard or pasting into another application.

IncomiQ SecureDoc main application screen
Free SecureDoc release No subscription is required for this release. SecureDoc is IncomiQ's own editor — not a wrapper around Notepad, Word, or another text editor.
Free Release

Download IncomiQ SecureDoc for Windows.

SecureDoc is being released as a free Windows application. The release page keeps the technical details and threat model visible so users can understand both what SecureDoc protects and where its protection stops.

Free Release

SecureDoc for Windows

IncomiQ's own plain-text editor with a default leak-free editing mode, encrypted file storage, internal encrypted copy/paste, idle shielding, screen-capture exclusion and same-user process hardening.

Price Free
Platform Windows
Version VERSION
Release Date RELEASE DATE
License Apache-2.0
Status Prototype Release
SHA-256 SHA256_HASH
Download SecureDoc — Free

The download button opens the official SecureDoc GitHub repository. Publish the version, release date and SHA-256 hash with each release. If the executable is code-signed, publish the signer/publisher name here too.

What you get

SecureDoc is intentionally focused. It is a local, single-user editor for sensitive text rather than a cloud document suite.

Security Features View → Protection Screenshots View → Technical Implementation View → Honest Security Limits Read → Full Threat Model Open →
The Core Idea

Your document should exist in as few places, for as little time, as the operating system allows.

Most editors leak by default. They can autosave plaintext, leave copies in memory, hand text to the normal clipboard, allow paging, or write process memory to crash dumps. SecureDoc deliberately closes those paths where Windows allows it.

SecureDoc is the editor.

You type directly into SecureDoc's own editor. The default leak-free mode holds the document as ciphertext while it is open and uses its own rendering and editing path.

It is not an encryption wrapper.

SecureDoc does not open your secret text in Notepad, Word, a browser editor, or another application behind the scenes. The document stays in SecureDoc unless you intentionally send content outside it.

What It Actually Does

Security built into the editor, memory model and file format.

SecureDoc is designed so the same protections apply while you type, save, copy, lock and return to an idle document.

◫

Leak-Free Editor

By default the open document is held as XChaCha20 ciphertext while you edit it. SecureDoc draws one decrypted glyph at a time and edits in place instead of keeping the whole document in a normal plaintext String.

Default Mode
⌁

Protected Memory

Sensitive text uses VirtualAlloc'd pages, guard pages and VirtualLock so document and key pages stay out of the normal pagefile when memory locking succeeds.

Pagefile Resistance
⌫

Zeroized Cleanup

Sensitive buffers are zeroed on edits, lock and exit. A zeroizing global allocator also scrubs freed heap blocks, including copies made by dependencies.

Heap Cleanup
⌛

Idle Shielding

After a short idle period, the open document is additionally protected with CryptProtectMemory and the editor blanks until you return.

OS-Bound Protection
•••

Veiled Passphrase Field

The passphrase is never decrypted just to display it. The field renders dots, stays veiled while you type and is unveiled only for the instant Argon2id needs it.

Passphrase Protection
⊘

Process Hardening

SecureDoc rewrites its process DACL so normal same-user applications cannot open it with PROCESS_VM_READ. Selected DLL-injection paths are disabled and crash dumps are suppressed.

Same-User Boundary
▣

No Plaintext Save Path

Saving produces XChaCha20-Poly1305 ciphertext under an Argon2id-derived key. Even the save temp file is ciphertext.

Encrypted On Disk
✂

Internal Encrypted Clipboard

In-app copy and paste uses SecureDoc's own encrypted clipboard and does not touch the normal Windows clipboard. Copying to the system clipboard is a separate, deliberately lower-security action.

Stays Inside SecureDoc
◉

Screen-Capture Exclusion

On supported Windows versions, the SecureDoc window is excluded from common screenshot and screen-recording paths while remaining visible to the person using it.

Does Not Stop Cameras
↺

Secure Locking

Locking wipes the text, derived key, undo history and internal clipboard from memory. It is a real cleanup operation, not just a visual screen change.

Wipes Sensitive State
✓

Memory Leak Audit

tests/memory_leak_audit.rs scans SecureDoc's own memory for runtime canaries across editing, locking, passphrase, clipboard and undo paths.

Verified Paths
🔒

Offline By Design

SecureDoc does not require an account, collaboration service or cloud sync. It is designed as a single-user, single-machine editor.

Zero-Telemetry Direction
Prototype Screenshots

See the protections being tested.

These captures show current prototype behavior: memory scanning, passphrase-strength feedback, encrypted file contents and screen-capture exclusion.

SecureDoc and a memory scanner searching for visible document text
Leak-free editor: a memory scanner searches for the visible phrase and does not find the readable document text.
SecureDoc passphrase screen showing weak password feedback
Passphrase protection: SecureDoc can evaluate strength while the actual passphrase field remains rendered as dots.
Encrypted SecureDoc file shown in a hex editor
Encrypted on disk: the SECUREDC header is visible, while the document body is stored as ciphertext.
SecureDoc excluded from a desktop capture while other windows remain visible
Capture exclusion: SecureDoc is omitted from the captured desktop while the surrounding windows remain visible.
What It's For

Designed for sensitive local writing.

SecureDoc is intentionally narrow: it focuses on keeping sensitive text local, encrypted and contained instead of trying to be a collaborative document suite.

A good fit for

  • Writing secrets you do not want touching normal plaintext disk or cloud paths, such as recovery phrases, API keys, passwords and security answers.
  • Drafting sensitive notes on a shared or possibly infostealer-infected machine where the attacker does not have administrator or kernel control.
  • Personal records you want encrypted at rest with no account requirement, such as journals, medical notes or legal notes.

Not the right tool for

  • Collaboration, cloud sync or sharing. SecureDoc is single-user, single-machine and offline by design.
  • Defending against an attacker who already has administrator, SYSTEM or kernel control.
  • Replacing full-disk encryption, endpoint protection or a trustworthy operating system.
Honest Limits

SecureDoc reduces exposure. It does not make a compromised machine trustworthy.

These limits are part of the product description, not hidden fine print.

Administrator or kernel malware defeats it. The normal process protections are for other programs running under your user account. Administrator/SYSTEM access, SeDebugPrivilege, a kernel driver or rootkit can bypass them.
What is on screen can still be reconstructed. Displayed glyphs become pixels in GPU memory. A normal CPU string scan does not see those pixels, but in-process code, OCR or a camera can still capture what is visible.
The in-memory veil has a key. The default editor defeats simple memory scanning by storing ciphertext instead of readable document text. Code executing inside SecureDoc can still obtain the key or hook the render/edit path.
No recovery. If you forget the passphrase, the encrypted document cannot be reset through a SecureDoc back door because there is no back door.
The Windows system clipboard is a weak point. Normal in-app copy/paste stays encrypted inside SecureDoc. If you deliberately copy to the system clipboard, one plaintext copy is handed to Windows and may be read by other software while it exists there.
Early editor limitations remain. The current prototype does not yet have click-and-drag selection, and very large files need additional word-wrap/performance tuning.
Why Rust

Memory control is part of the security model.

SecureDoc uses Rust because a garbage-collected editor runtime can make hidden copies of sensitive strings and relocate them around the heap. Rust allows SecureDoc to control where sensitive buffers live and wipe memory explicitly without choosing handwritten C for the whole application.

Why not Electron or C#?

Garbage-collected runtimes may copy and move strings invisibly. If the application cannot locate every plaintext copy, it cannot reliably erase every plaintext copy.

Why not handwritten C?

C gives manual memory control, but it also increases memory-safety risk. Rust provides explicit allocation control while avoiding many classes of buffer-overflow and use-after-free bugs.

File Format

A small authenticated encrypted container.

The file header stores the version, algorithms, KDF parameters, salt and nonce. The entire 80-byte header is authenticated as associated data.

offset size field 0 8 magic "SECUREDC" 8 2 format version 10 1 KDF id (1 = Argon2id) 11 1 AEAD id (1 = XChaCha20-Poly1305) 12 12 Argon2 m_cost / t_cost / p_cost 24 32 salt 56 24 nonce 80 N ciphertext + 16-byte Poly1305 tag
✓

KDF parameters are authenticated.

If someone edits the stored Argon2 parameters to try to make password cracking cheaper, authentication fails instead of silently opening the document under weakened settings.

Technical Details

How the free release works under the hood.

The security primitives are implemented and tested. SecureDoc remains a prototype while editor usability and large-file behavior continue to improve.

Area Implementation
Platform Windows
Language Rust with a Windows/MSVC toolchain.
Open Document Default leak-free editor stores the document veiled with XChaCha20 while open.
File Encryption XChaCha20-Poly1305 authenticated encryption.
Password KDF Argon2id. Documented default: 256 MiB memory, t=3, p=4.
Idle Protection CryptProtectMemory(SAME_PROCESS) with a blanked editor while shielded.
Memory Cleanup VirtualAlloc/VirtualLock, explicit wipes and a zeroizing global allocator.
Process Protection Restricted DACL for normal same-user process access plus selected injection mitigations.
Verification tests/memory_leak_audit.rs checks UTF-8 and UTF-16 canaries across multiple sensitive paths.
License Apache-2.0.
IncomiQ | SecureDoc — free Windows release built by IncomiQ.
Your text stays inside SecureDoc by default. Deliberately exporting it to another application ends SecureDoc's protection for that exported copy.