This page says what the programs are built to enforce, how, and where their protection ends. They are not released; what is written here is the design they are being built and tested to. We would rather you knew the limits from us than found them yourself.
Every capture stays on your computer. Anything that would send it anywhere is a feature you turn on, named for what it does, and off until then.
| Setting | Default | Why |
|---|---|---|
| Upload or sharing | Does not exist | There is no account and no cloud in either program. |
| Telemetry and analytics | Does not exist | Any future analytics would be opt-in and specified separately, in public. |
| Keyboard recording | Off | Keystrokes are recorded only when you switch it on for a recording. Never by default. |
| Local control pipe | Current user only | The two programs talk over a named pipe restricted to your account. No TCP listener, ever, by default. |
| Artifact permissions | Your account | Captures inherit your user's private permissions; a cancelled capture is cleaned up. |
| Remote AI | Does not exist | OCR and smart redaction are designed to run locally. A remote adapter, if ever, is opt-in with full disclosure. |
Blur and pixelate are visual effects: the pixels are still in the document. Secure redaction is different in kind. At export the covered pixels are flattened and removed, and the export is tested by trying to recover them from the file and from the document package.
Capture and editing are separate programs. A fault in the editor does not stop a capture, and a failing capture backend cannot corrupt a document. Native handles and GPU surfaces are treated as unsafe boundaries and kept in small, audited modules.
A release is trusted through its signature and through nothing else. The manifest is signed with ECDSA P-256; the public half of the release key is compiled into both programs. The installer is then checked against the size and SHA-256 in that signed manifest before it runs.
People at Exprezoe can sign in with Exprezoe Identity in place of a license key. It goes through the identity provider in your own browser: authorization code with PKCE, a challenge this site issued to that installation, a second factor checked where it belongs. Neither program ever sees a password.
Neither program has analytics or usage tracking. They talk to this site for these things only.
| To this site | What |
|---|---|
| The update channel | The installation's entitlement, which program it is and its version. The answer is the signed manifest. |
| The license service | The license key once, at activation, with the program, the computer's name, the platform, the version, and a hash of an identifier made for that installation. |
| Staff sign-in | For Exprezoe staff: the proof of sign-in from Exprezoe Identity, once, in place of a license key. |
Never a capture, a frame, a line of recognised text, a window title or a file name. Diagnostics stay on your computer and are written so as not to contain captured content.
Tell us before you tell anyone else, and give us the chance to fix it. Every report is read by the people who build Quikap.
Report through your contact at Exprezoe. A public address for reports will be published here and in /.well-known/security.txt.
Please include which program and its version (Help › About), what you did, what happened, and what you expected. Please do not include real captures of anything confidential.
Nothing is released yet, and this site will say so until a release is published. Licenses are issued to teams we can support well while the products take shape; one license covers both programs.