Built for information that should remain controlled

Alusia assumes your documents are confidential by default. These are the concrete mechanisms, not slogans.

Architecture

  • Private storage buckets; documents are never publicly addressable.
  • Organization isolation enforced by row-level security in the database - every query, not just the UI.
  • Role-based access control: owner, administrator, member, viewer, with server-side enforcement of every change.
  • Restricted collections are filtered before retrieval; restricted content never enters another user’s answers.
  • All AI requests originate server-side. Browsers never hold AI provider keys and never talk to AI providers directly.
  • Retrieved document text is treated as untrusted data - instructions embedded in documents are never followed.
  • Two-factor authentication (TOTP authenticator apps) with recovery codes; an administrator can require it for all members of the organization, enforced server-side.

Data handling

  • Your documents, extracted text, search indexes and conversations are stored at rest in the EU (Frankfurt, Germany). AI processing (embeddings and answers) is performed by OpenAI on every plan and may run outside the EU. AI processing only within the EU is planned.
  • Your documents and questions are never used to train AI models - ours or our providers’.
  • Document text is sent to the AI provider only to index your documents and answer your questions, under API terms that prohibit training on it; the provider may keep it for up to 30 days to detect abuse of its service, and then deletes it.
  • Full organization export and deletion, including indexed content, on request.
  • Audit events record security-relevant actions with actor and time.

Operational practice

  • Secrets live in server-side secret stores; they are never shipped to browsers or logged.
  • Automated checks watch the processing workers and queues every 5 minutes and load the public site in a real browser several times a day, and alert us when something fails.
  • There is no support access to your documents: our admin console shows organizations, plans, usage and the titles and error codes of documents that failed to process, never document content, questions or answers.

Certifications

Certifications are listed here only once attained. We publish our current compliance status honestly rather than claiming badges early.

Reporting a vulnerability

Security reports are welcome at security@alusia.net; we acknowledge within two business days.

security@alusia.net