Security
Built for teams that care about privacy, isolation, and compliance readiness.
Dedicated Server
No Data Sharing
No SSH Access
HTTPS (E2E)
Quarterly Cert Updates
Content Safety Screening
Isolation
Dedicated Server, No Data Sharing
- Single-tenant deployment: your instance runs on its own server.
- No cross-organization data sharing: indices, uploads, and logs are not shared with other customers.
- No SSH access: shell access is disabled by default to reduce attack surface.
In transit
End-to-End Encryption (HTTPS)
- HTTPS enforced for the UI and agent endpoints.
- Certificates rotated quarterly (or sooner if needed).
- Modern TLS configuration for browser and API traffic.
Safety
Screening of Uploads & Queries
- Document screening: incoming PDFs are checked for harmful or disallowed content.
- Query screening: prompts are evaluated to reduce the risk of generating harmful outputs.
- Configurable policies: you can tighten defaults to meet internal standards.
Goal: align with emerging EU/US AI regulatory expectations around content safety controls.
Access
Credentials & Sessions
- bcrypt-hashed passwords — never stored in plain text.
- 3-device session cap to prevent zombie sessions after disconnects.
- Admin controls to replace the oldest active session if the cap is reached.
Security Checklist (at a glance)
| Area | Practice |
|---|---|
| Isolation | Single-tenant server; no org-to-org data sharing |
| Remote Access | No SSH access (disabled by default) |
| Transport | HTTPS/TLS enforced end-to-end |
| Certificates | Quarterly rotation; early rotation if issues arise |
| Credentials | bcrypt hashing for passwords; change defaults on first login |
| Sessions | Max 3 active; “Replace Oldest” recovery |
| Content Safety | Screening of uploads and queries; configurable policies |
| Data Control | Delete documents and their vector indices at any time |
Note: This page outlines product behaviors and guardrails. It is not a legal attestation of compliance. For audits, request a tailored security brief.
Security FAQ
Do you mix or train on our data?
No. Your uploads and indices remain within your dedicated server. We do not pool data across organizations.
Is SSH available for troubleshooting?
SSH access is disabled by default. This reduces exposure. If you require a break-glass process, contact support for a controlled, time-boxed procedure.
How is traffic secured?
All browser and agent traffic is served over HTTPS/TLS. Certificates are rotated quarterly (or earlier if needed).
What about harmful content in documents or prompts?
We screen both uploads and user queries for harmful or disallowed content. Policies are configurable so you can align with internal standards and emerging regulations.
How are passwords stored?
Passwords are hashed with bcrypt. Change the default credentials on first login and store them securely.
What happens if three devices are already active?
You’ll be prompted to Replace Oldest (recommended in 99%+ of cases) or Recheck sessions. This prevents zombie sessions from consuming resources.
How do we remove sensitive data?
Use Delete a Document to remove a file and its vector index from the server. Keep a local backup if needed—deletions are irreversible.