A Microsoft 365 toolkit the vendor can't decrypt — Argon2id, XChaCha20-Poly1305, X25519, Ed25519, BIP39 — plus an honest list of what the server sees.
Frequently asked questions
What does "zero-knowledge" mean for GTools.pro?
The encryption key is derived from your passphrase via Argon2id and never leaves your machine. The server stores ciphertext and metadata only. Vault contents, OAuth client secrets, exports and backup data are all encrypted with this key.
OAuth handshake parameters, license JWTs, scheduled-report orchestration metadata, billing data and operational telemetry — documented at gtools.pro/security-overview.
Where can I report a security vulnerability?
security@gtools.pro. See gtools.pro/trust for the responsible-disclosure policy.
Threat-model limitations — what zero-knowledge is not for
Zero-knowledge means the GTools.pro server never sees plaintext vault contents, OAuth refresh tokens, or backup payloads. It does not mean immunity to operator-side compromise: a malicious browser extension, a keylogger on the operator workstation, or a stolen recovery passphrase still grants full access to the data the operator can see. The desktop edition raises the bar (vault sits inside the OS keychain / Stronghold), but the operator endpoint remains in scope for the threat model.
Server-side metadata that GTools.pro must process — billing identifiers, schedule timestamps, audit-log entries — is documented in docs/SECURITY.md. We log enough to invoice, schedule, and debug; we do not log tenant contents. Anything outside that boundary is intentionally out of scope.