WivenLLM security
Security by architecture,
not by promise
WivenLLM is installed on your hardware. Your documents, conversations, and indexes remain where you put them. This page describes precisely what is in place, its scope, and what remains your responsibility.
It covers all three deployment formats. In the hosted format, each client has its own instance: no data, indexes, or databases are shared between organizations. What is shared are the hardware and costs, never the data.
What doesn't leave your home
The data is not protected by a contractual promise: it is simply not transmitted.
- Your data remains on your machine. Database, deposited documents, vector index and conversation history reside in the storage folder of the workstation or server you have chosen.
- No training on your data. WivenLLM does not include any model training or refinement mechanisms. Models are used for inference purposes only. Your documents do not contribute to any model, neither ours nor any third party's.
- No telemetry is active by default. Our default images and settings disable all usage data. Enabling this is an explicit choice on your part, never a setting to discover and then disable.
- Offline operation possible. Using local models and a local vector database, WivenLLM operates without any outbound connections. This is the preferred mode for isolated environments.
- Auditable open-source models. Mistral, LLaMA, Qwen, KIMI. You know what's playing on your machine.
Encryption
We prefer to be precise about the scope rather than writing "everything is encrypted".
- TLS 1.2 minimum, required. Exchanges between workstations and the server are encrypted, the minimum protocol version is explicitly set in the configuration, and clear text access is redirected to HTTPS.
- Secrets encrypted by the application. Provider API keys and unique authentication secrets are encrypted using AES-256, with a derived key specific to your installation.
- Full encryption of the medium, verified and certified. Volume encryption—LUKS, BitLocker, or FileVault, depending on the platform—is a prerequisite for installation. A check at startup will flag an unencrypted volume, and this will be noted in the delivery report you sign.
- Rotation of the tooled wrenches. A re-encryption script allows the application key to be changed without losing existing secrets. The session secret is rotating, with a double-acceptance window during the switchover. Secrets are moved from the environment file to restricted storage.
- Integrity of internal exchanges. The calls between the server and the document processing component are cryptographically signed, which prevents a third party from injecting them.
Access, roles and compartmentalization
Access is assigned by name, inherited from your directory, and the powers are separate.
Single sign-on by default
Multi-user mode with OpenID Connect authentication is the default configuration for all deployments. Local password-based login is disabled except for the backup account.
Double factor inherited from your directory
Because the connection goes through your identity provider, your own requirements apply — including the second factor, with no possibility of bypassing it via a local connection.
Short and revocable sessions
Session duration is limited. Changing your password, suspending it, or manually revoking it will immediately close all open sessions, including those on other devices.
Separation of powers
Technical administration—accounts, roles, connectors, configuration—is performed without access to the content of conversations. Access to the content is handled by a separate role and leaves an indelible trace.
Partitioned workspaces
A user only sees the spaces to which they are attached. Vectors are isolated by space, in separate namespaces.
Personal Second Brain
A user's working memory is unique to them. It is not visible to their colleagues or managers, and is not implicitly shared.
Audit log
A log that an administrator can delete proves nothing. Ours cannot be deleted from the application.
- Not deletable from the application. The journal is write-only. No manual deletion is possible; only the retention policy you set will cause entries to expire.
- Wide coverage. Connections and connection failures, disconnections, account creation and modification, document access and download, document queries, conversation exports, configuration modifications.
- Access to the content is itself tracked. If an authorized role exports a conversation, the operation is logged, and this logging cannot be disabled.
- Export to your SIEM. The log is continuously streamed to your monitoring system, either via syslog or webhook. Your correlation and retention rules apply.
- Content control. Rules for blocking, masking, or flagging based on terms or patterns, with a log of triggers. Only a truncated extract is kept, never the full message.
Supply chain
What you install must be verifiable before being executed.
Signed binaries
The installers are signed — Authenticode under Windows, Apple notarization under macOS — and published with their SHA-256 hash. No warning screen during installation.
Verifiable images
Server deployments use a versioned and signed image, accompanied by its software inventory and certificate of origin.
Check at each modification
Static code analysis and dependency checking at each change, blocking on high and critical vulnerabilities.
Monitoring and corrective actions
We monitor security advisories for the open-source components we integrate and report patches. Critical vulnerability: patch released within 7 days. High vulnerability: within 30 days. You are notified via mailing list and in-app banner.
Signed update
On the workstation side, the update is signed and verified before application.
Responsible Disclosure
A vulnerability is reported to security@wiven.ai. Acknowledgment within 72 hours, commitment to correction graduated according to severity, and no legal action taken against a researcher in good faith.
Who does what
Having AI installed in your home shifts part of the responsibility onto you. It's best to put that in writing.
| Individual workstation | Dedicated server | |
|---|---|---|
| Supply and configuration | Wiven | Wiven |
| Installation and setup | Wiven | Wiven |
| Media encryption | You, verified and attested by Wiven | You, verified and attested by Wiven |
| TLS and certificates | Not applicable locally | Wiven during installation, then you |
| Backups | YOU | YOU |
| Physical security | YOU | YOU |
| Firewall and network | Not applicable locally | YOU |
| Directory, accounts and roles | Not applicable | YOU |
| Security patches | Published and notified by Wiven, applied by you | Published and notified by Wiven, applied by you |
| Monitoring and SIEM | Not applicable | Wiven provides the feed. |
Deletion and reversibility
- Granular suppression. A document, workspace, or account is deleted from the interface; associated data, including vectors, is removed with it.
- Export your exchanges. The conversations are exported as JSON or CSV. Your source documents have never left your storage folder.
- After the contract, nothing remains with us. None of your data has ever passed through our infrastructure. Therefore, there is nothing to return or delete on our end.
Documents
Your purchasing and legal teams don't need a web page, they need documents. Here they are.
Subcontracting agreement
The DPA (Data Processing Agreement) governing the processing of personal data, to be attached to your contract.
Processing register
A description of the processing carried out by WivenLLM, its purposes and its legal basis.
Impact analysis
The AIPD, to be taken and adapted to your own deployment context.
Security policy
Our internal rules: access management, patches, secrets and environments.
Incident procedure
Who alerts whom, in what order and within what timeframe, with the applicable notification deadlines.
List of subcontractors
The list of names of third parties likely to be involved in the chain, and in what capacity.
Our position with regard to the nLPD and the GDPR is documented in this file. The entire file is available upon request, subject to a confidentiality agreement if your procedure requires it. info@wiven.ai
What we are not yet claiming
A security page is only valuable if it also says what is not being done.
- No ISO 27001 or SOC 2 certification to date. We do not claim this. WivenLLM carries the Swiss Made Software label, which attests to the origin of the development, not to a security audit.
- No independent penetration tests have yet been conducted. We will publish the service provider, the scope and the date when it has taken place.
- Application-level encryption of the database is on the roadmap. Today, only secrets are encrypted by the application; content is protected by full storage encryption, verified at installation.
- The second native factor has not yet been delivered. It is currently inherited from your identity provider, which covers the need in almost all cases. Integrated two-factor authentication, mandatory for administrators, will follow.
Talking to someone
Twenty minutes to examine your context, regulatory constraints, and the appropriate deployment format. Your technical and legal teams are welcome.
A security question, a supplier questionnaire, or a request for documents: info@wiven.ai