Encryption

In transit and at rest

Encryption protects data at two moments. In transit, while a file travels between your device and the server, a TLS connection keeps anyone along the way from reading it; that’s the padlock in your browser’s address bar. At rest, once the file is stored, it’s kept encrypted on disk, so the raw storage alone doesn’t reveal it. At Clivio, both apply: transfers go over TLS, and your documents and data are stored encrypted on Google Cloud, in the European Union.

Expiring links and two-factor sign-in

When you open a file in Clivio, it reaches you through a temporary link that expires quickly, so a copied link soon stops working. When you share a document, you choose how long the link lasts (1 hour, 24 hours, 3 days or 7 days), and you can hide amounts, IBANs, ID numbers and addresses before sending it. A shared document link isn’t password protected, so pick the shortest duration that works for you.

Encryption can’t stop someone who has your password: they would see your documents as you do. Two-factor authentication closes that gap. With a code from an authenticator app (TOTP) or by text message, a stolen password is no longer enough to get into your account.

Encryption and the AI analysis

Encryption protects your documents on the way and in storage. To do its job, reading a document when it arrives, filing it, translating it or answering your questions, Clivio’s AI sends the document’s text and images to the Google Gemini API, and the result comes back to your account. The Trust page shows exactly what is sent. Clivio doesn’t sell your data and doesn’t use it to train a model of its own.

Every service that searches, summarizes or files documents for you works this way, because it has to read them to do so. Encryption where only you hold the key is designed for storage that never reads your files.