Security
Security you can inspect.
How Apertura handles credentials, updates, and AI requests, written against the shipped design and the privacy policy.
Credentials
Tokens belong in the system store.
macOS Keychain
Session tokens are stored in the macOS Keychain, not in a plain file.
Windows credential storage
Windows uses its encrypted credential storage for session tokens.
Secure Enclave binding
Where a Mac has a Secure Enclave, paid sessions are bound to that device; the private key never leaves it.
One-way fingerprints
Only a SHA-256 device fingerprint is sent, never the hardware values it was built from.
Updates
Signed before installed.
macOS
Sparkle checks update packages for valid signatures before installing.
Windows
electron-updater installs updates only after a passing signature check and does not silently downgrade.
AI requests
Visible paths only.
On-device
The conversation stays on your machine; the model file is signature-verified before use.
Relay-assisted
The visible conversation and attachments you add go to api.notch-os.com. Prompts and responses are not written to a database or log.
Admin access
Backend administration is one shared operator bearer secret, compared in constant time, with a per-IP lockout after repeated failures. Every admin route returns 503 when that secret is not configured, so a misconfigured deployment is closed rather than open. There are no per-person admin accounts and no password-based admin login, and we do not claim an audit trail of which person at our end used it.
Reporting
Report a vulnerability.
No dedicated security address is published yet, and we will not invent one. Use the contact page for the current route; do not include secrets in a report. No security guarantee is implied: no system is perfectly secure.