Securing Company Knowledge with Workspace Isolation

When organisations adopt AI tools for internal knowledge, data privacy is the first concern. Who can see our documents? Are our chat histories shared across companies? Can the AI accidentally learn from one tenant and reveal it to another?

Rekall-IQ addresses these questions with workspace isolation. Each organisation operates inside its own private boundary within the platform.

What Workspace Isolation Means

Every piece of data in Rekall-IQ is tagged with a workspace ID. This includes uploaded documents, text chunks, vector embeddings, chat messages, and user profiles. Every database query, vector search, and API call enforces this boundary at the application level.

When a user asks a question, the system retrieves context only from that user’s workspace. Documents from Company A never appear in search results for Company B, even if both use the same AI model.

Platform Admin Privacy Boundary

Rekall-IQ operators with the platform admin role can manage workspaces, view metadata, and monitor system health. By default, they do not read uploaded document text or browse private chat conversations. This boundary is by design, not by convention.

Why This Matters

Workspace isolation means compliance teams can approve Rekall-IQ for internal use without worrying about cross-tenant data leakage. It also means IT leaders can roll out AI-powered knowledge search with confidence.