You’re trusting us with policies, contracts and know-how,
so here is exactly what stays and what disappears.
The original sits on our server only for as long as conversion takes.
Open the server disk and there’s nothing to read. It’s decrypted in memory only at the moment of search.
This is the exact storage format seen in our production database.
Press delete and every linked piece of data disappears together. There is no retention grace period.
The one exception: if a team admin has enabled the audit log, a record of who uploaded and deleted what
remains visible to admins only — for corporate audit and compliance needs.
Private brains are readable only by members and AI holding a personal access key. Who used it, and when, is recorded.
Documents uploaded for conversion are deleted from the server the moment text extraction finishes. Originals never accumulate anywhere on our servers. (Images and logos you upload directly to a site are kept, since they’re for display.)
All data lives only on servers in Korea, and every connection with browsers and AI tools is encrypted with HTTPS (TLS). Search chunks are stored with AES-256-GCM encryption.
Most services send your documents to an overseas embedding API. Wisdombase runs its embedding model on GPU infrastructure in Korea that AI3 owns and operates. Document chunks never leave the country.
An embedding vector is a sentence turned into an array of numbers — not the original text on its own — but we don’t stop there: the vectors themselves are stored AES-256-GCM encrypted, decrypted in memory only at the moment of search.
Delete a page or site and its text, search index, embeddings, version history and attachments are all removed at once, immediately. If a team admin enabled the audit log, only the admin-only (encrypted) record remains.
Customer documents are never used to train any AI model. Conversion, analysis and embedding run only through model providers with published no-training policies.
Private brains can be read only by team members and AI holding a personal access key. When someone leaves, revoke that one key immediately. Who used it, and when, is logged.
Allow or block MCP/AI access, force everything private, block search engine indexing, keep an audit log (including deleted documents), restrict upload file types, and auto-filter uploads (PII masking, security classification and more) — all switchable in the team admin console.
For security questions, use the contact channel in the admin console.