Tresorit

What Is Tresorit?

If you’re tired of “cloud storage” that turns into a privacy trade-off (provider-side scanning, weak sharing controls, or admins who can see everything), Tresorit is built for the opposite: put files in the cloud while keeping the provider locked out. Its core pitch is end-to-end encryption with a zero-knowledge model—your files are encrypted on your device and remain unreadable to Tresorit (and even the underlying cloud host) unless you explicitly share access.

This is for people and teams handling sensitive documents: client files, legal/finance records, regulated data, or simply anyone who wants “Dropbox-like sync” without giving the storage company the technical ability to read the contents. Tresorit also leans into business features (admin controls, compliance positioning, secure external collaboration) rather than being a cheap “infinite storage” play.

One distinctive detail that matters in practice: Tresorit is operated by a Swiss entity (jurisdiction: Switzerland), while using Microsoft Azure infrastructure for storage/hosting. The security model is designed so that even though the infrastructure is Azure-backed, the content remains end-to-end encrypted and unreadable to Tresorit/Microsoft.

Tresorit Features and Performance

Tresorit’s feature set centers on zero-knowledge, end-to-end encryption (E2EE). In plain terms: encryption happens client-side, and only the people you authorize have the keys needed to decrypt. Tresorit explicitly positions this as different from “encryption in transit” or “encryption at rest,” where the provider can still access plaintext under the hood.

On the collaboration side, Tresorit supports secure sharing and external collection workflows. A concrete example is File Requests: you can create a request link so outsiders can upload files into your folder, without being able to see or download anything already in that folder. That’s a practical feature for collecting sensitive intake documents (HR, tax docs, onboarding paperwork) without resorting to email attachments.

For developers and integrations, Tresorit documents an S3-compatible API approach that runs locally in your environment “to maintain Tresorit’s encryption model.” In other words, they’re trying to provide an integration surface that can work with S3-style tooling while preserving E2EE rather than turning encryption into a server-side feature.

Performance is the trade-off you should expect with any E2EE sync tool: encryption/decryption and metadata protections add overhead, and some workflows inherently feel slower than mainstream providers. TechRadar’s testing and general review coverage describe a fairly normal “sync client” experience, but user feedback and Tresorit’s own support positioning (and community discussions) consistently frame convenience/performance as something you sometimes give up to get true zero-knowledge storage.

A no-BS way to think about it: if your priority is fast collaborative editing in the browser, E2EE cloud storage is rarely the best tool. If your priority is storing and sharing sensitive files while keeping the provider out, this category exists for a reason—and Tresorit is one of the most established vendors in it.

Pricing and Plans

Tresorit is paid (pricing model: paid), but it also offers a Basic (free) tier and free trials for paid plans. Tresorit’s current personal pricing page shows paid tiers (e.g., “Personal Essential” and “Personal Pro”) with “Try for free,” and it states you can cancel and downgrade to Basic.

On refunds: Tresorit’s Knowledge Base describes a 14-day free trial, and a money-back guarantee flow that requires contacting support to claim a refund within 7 days from purchase in the described scenario. It also states that after the trial period you can cancel under their terms, but you will not receive a refund. That’s strict compared to many consumer SaaS tools—plan on “trial first, decide early.”

Plan structure is split into Individuals and Business, with Business offering standard tiers and an Enterprise/custom option (including sales contact for custom/volume pricing). Tresorit’s business pricing page explicitly references monthly vs yearly options and an Enterprise path.

Exact prices can vary by region, billing cadence, promotions, and currency. Tresorit’s own pages should be treated as the source of truth at purchase time; third-party price trackers can lag or reflect a snapshot. Still, independent pricing comparisons and documents do support the existence of: (1) a free Basic tier around a few GB of storage and (2) higher-priced paid personal tiers positioned at 1TB+ and above.

Privacy and Security Assessment

Jurisdiction: Switzerland. For privacy, that’s generally seen as a stronger baseline than many US-based SaaS providers, and Tresorit explicitly discusses being a Swiss company in its transparency reporting context. But jurisdiction isn’t magic: legal process can still compel cooperation, and your risk model should include where you (and your team) operate and what laws apply to you.

The most important technical point is access: Tresorit’s model is built around end-to-end encryption and “zero-knowledge,” meaning files are designed to remain unreadable to Tresorit (and it also states they remain unreadable to Microsoft Azure, given the encryption model). If implemented correctly, this sharply limits what can be produced in response to content requests—because the provider shouldn’t have the plaintext.

Audits/assessments: Tresorit publicly posts materials describing third-party security review work (including an EY memo-style document) and also states it holds ISO 27001 certification (notably ISO 27001:2022), audited annually. ISO 27001 is an information security management standard—it’s not a cryptographic proof of E2EE correctness, but it is meaningful evidence of mature security governance.

On transparency, Tresorit published a transparency report blog post describing how it handles government data requests and notes that (in the period it covered) it received an informal request and did not hand over data without an official decision. That’s dated, but it’s still useful as a statement of posture. Tresorit’s contact page also references downloading a “DSA Transparency Report,” indicating ongoing reporting exists (you should read the latest document directly if this matters to your threat model).

Open-source posture: Tresorit provides a detailed encryption whitepaper, but that’s not the same thing as open-source clients. If you require open-source apps for independent verification, you should treat Tresorit as a “documented, proprietary implementation” unless Tresorit explicitly states otherwise on its own site (and we did not find a clear statement that the core clients are open-source in the materials referenced here).

Strengths and Limitations

Strengths

• The security architecture is designed around client-side E2EE / zero-knowledge, explicitly positioning Tresorit so the provider can’t read your stored files.
• Strong business/security posture signals: published encryption whitepaper and publicly stated ISO 27001 certification.
• Practical secure collaboration features, including file requests that allow external uploads without exposing folder contents.
• S3-compatible API approach intended to preserve the encryption model via a local-running component (useful for certain integration scenarios).

Limitations

• Price: Tresorit is widely perceived (including by reviewers and user discussions) as a premium-priced option versus mainstream cloud storage. If you mainly want cheap capacity, this probably isn’t it.
• E2EE trade-offs: performance and convenience can be worse than non-E2EE tools in some workflows, because files must be downloaded and decrypted client-side for access.
• Refund posture is strict: trial exists, but after that Tresorit states you generally won’t receive refunds.

Who Should Use Tresorit?

Good fit if you are:

1. A freelancer/consultant handling client-sensitive documents and needing secure sharing + the ability to revoke access. Tresorit is explicitly built around E2EE sharing and controlled collaboration rather than “trust the provider.”
2. A small business that wants cloud file sync but with “provider can’t read it” as a baseline requirement, plus compliance posture (ISO 27001 and GDPR/HIPAA positioning).
3. Teams that frequently collect documents from outside parties and want a safer intake channel than email attachments (File Requests).

Not a great fit if you are:

1. Someone who mostly wants the cheapest large-capacity cloud drive. Tresorit’s market positioning (and typical user feedback) is premium security, premium price.
2. A team that lives inside browser-based co-editing and expects Google-Docs-style frictionless collaboration. E2EE storage tools can’t magically match that convenience without changing the security model.
3. A “must be open-source clients” purist who won’t accept proprietary apps + whitepaper documentation.