Skip to content

Security: Oil3/QLCodec

SECURITY.md

Security Policy

QLCodec

  • Is alway sandboxed and hardened
  • Is always signed and notarized
  • Uses only public API
  • Is codec-compliant
  • Cannot connect to the internet
  • Never asks for credentials
  • Does not run in the background
  • Never collects nor stores any private data
    • Even the custom ookmarks and the reume systems do not store filenames or filepaths: both use instead hashes to load timestamps. > - Hashes are truncated, timestamps are normalized 8 of November of 2025 - Panama City

There aren’t any published security advisories