Security

Keep your knowledge
in the right workspace.

Security starts with real controls and a clear view of their limits.

Implemented

Authentication

Passwords use Argon2id when supported, with a bcrypt fallback and unique salts. Sessions use hashed random tokens, HttpOnly cookies, expiry, CSRF tokens, and same-origin checks.

Implemented

Authorization

Every document, search, invitation, and membership request checks workspace access. Owners manage membership; editors manage documents; viewers read and search.

Implemented

Safe content handling

Parameterized SQL, bounded input, plain-text rendering, restrictive CSP, and private database storage. Source links are never fetched by the server.

What the operator must configure

Production requires HTTPS, a verified sending domain and SMTP credentials, a private MySQL database, backups, and monitoring. This release runs on PHP 8.3+ and shared hosting.

Uploaded content and embeddings are stored in MySQL through PDO. Database encryption at rest depends on the hosting provider. When AI is enabled, document text is sent to the selected provider to create embeddings, and retrieved excerpts plus questions are sent to generate answers.

Current limits

Members can access all documents in their workspace. This beta does not include per-document ACLs, SSO/SAML, a formal compliance certification, or an independent penetration test. Rate limits and provider quotas reduce usage; they are not a billing guarantee.

Do not describe Knowtiq as SOC 2 certified or already deployed on AWS unless that is independently true.

Report a concern

Use the Contact page with enough detail to reproduce the issue. Avoid sending passwords, tokens, or sensitive document contents.