Qwerty security overview

What stays on the Mac

You select the repositories and documents that Qwerty's Workbench and agents can use. Qwerty Engine runs the approved model on the same Mac through an authenticated loopback connection. In the restricted offline workflow, drafts, proposed actions and redacted audit records stay on the managed Mac.

Check optional connections

Cloud providers, connectors, downloads, updates and remote sessions each have their own permissions and data flows. Prepare the installer and model files before using Qwerty offline. Run the agreed tasks with the network disconnected, then inspect network activity to check the configuration you installed.

Control access and actions

• Limit file access and tools to what the task needs.
• Test an action that should be denied and an action that needs human approval.
• Use approved actor identities and require authenticated access for local clients.
• Keep secrets in Keychain-backed storage. Limit access to application files to their owner.
• Your organization manages macOS encryption, device management (MDM), identities and retention.

Inspect audit records and diagnostics

Check how records are redacted, how long they are kept, how their integrity is verified and who can export them. Qwerty does not collect product telemetry by default. Diagnostic exports are designed to leave out raw prompts, credentials, repository contents and audio by default. Inspect an export from the supplied package to check what it contains.

Keep the test records

1. Record the release, model source, file hashes, runtime, policy and Mac hardware.
2. Check signatures, notarization, the software bill of materials (SBOM), supply-chain records and model authorization records.
3. Save the results of offline tasks, denied actions and approval checks. Include audit integrity checks and redacted exports.
4. Try installation, an update, rollback and recovery.
5. Write down unresolved issues and your organization's acceptance decision.

What the July report shows

The July 17, 2026 engineering report recorded 57 checks: 44 passed and 13 were blocked, with no hard failures. It marked local implementation complete, but that build had not cleared production release checks. This guide does not grant FedRAMP authorization, an Authority to Operate (ATO) or SOC 2 certification.