Run in the EU.
Sealed on your device.
An Austrian company operates Encloq on servers in the European Union. Your files and messages are encrypted on your device before they leave it, so the systems we run store your work without being able to read it.
- Encrypted on your deviceBefore anything leaves itOn your device
- Encrypted in transitOn every connection to EncloqIn transit
- Stored in the EUServers and storageIn the EU
- Under EU lawEncloq GmbH, AustriaUnder EU law
Stored by us.
Readable by you.
Encryption happens in the app, on your device. Our servers receive sealed content and the few details needed to deliver it.
Sealed before upload
Files and their names, messages, conversation titles, contacts and signatures are encrypted on your devices, readable for you and the people you share them with. Previews, search and text recognition are created there too.
What the service sees
Your e-mail address, the devices you sign in with, sizes and times, who takes part in which conversation, and whether a message was delivered and read. The service needs these details to work.
No ads, no profiles
No advertising, tracking or behavioural profiles, and no permanent access logs. Push notifications and e-mails carry no message content, and your content never trains AI models.
What nobody can restore
If every passkey, device and recovery method is lost, the content cannot be opened again, not even by us. So set up a second way in.
Passkeys guide
In the EU.
Under EU law.
EU
Servers, storage and delivery
The servers that run Encloq, the storage that holds your encrypted content and the delivery of this website are located in the European Union.
Infrastructure and jurisdictionProviders bound to the EU
Our hosting and storage providers are based in the EU and contractually bound to process data on our instructions and within the EU.
Sub-processorsRequests from outside the EU
We respond to official requests from other countries no further than EU or Austrian law permits. Your content stays encrypted either way.
Protection against third-country access
As long as needed.
Then deleted.
How long each thing lasts, counted from the moment it starts. The periods come from our privacy information.
At once
- Asking to delete your account signs out every device.
14 days
- Your account is erased with its content, unless you sign in again before then.
- Anything you deleted is gone from our backups too.
- A prepared data export expires.
30 days
- What’s in the trash is deleted for good.
- An invitation nobody accepted expires, and the invited address is removed.
90 days
- A sign-in session ends, however active it is.
1–120 months
- Automatic deletion removes files and messages older than the period you choose.
Years
- Free accounts unused for three years: we e-mail first and delete no sooner than 30 days later.
- Invoices stay as long as tax law requires.
What stays after deletion. Invoices and contract records the law requires, and your public keys, so the messages you sent remain verifiable. Copies you already sent stay with their recipients, who then see “Deleted account” instead of your name.
Every period in our privacy informationPromises you can
hold us to.
- Art. 28
Data processing agreement
Built into our Terms: confidentiality, security measures, your right to audit, and notice of a data breach without undue delay.
Annex III - 30 days
Notice before a new sub-processor
You can object within 14 days, and end the contract if we go ahead regardless.
Annex III, section 4 - €0
To export or switch provider
Export your files and data whenever you like, decrypted on your device. No notice period, no fee.
Provider switching
99.5%
Availability on paid plans
Measured every billing month and written into our Terms. If we fall short, part of your fee comes back.
Terms, section 5The code you run.
Accounted for.
Encloq runs in your browser, so what reaches it matters: where the code comes from, what it may do and how each release is made.
This page, checked by your browser
- ConnectionHow this page reached you
- –
- Requests to other sitesTrackers, fonts or scripts from elsewhere
- –
- CookiesSet by this website
- –
- Stored on this deviceBy this website, in your browser
- –
Read by your browser for this page. Its developer tools show the same.
Encrypted connections, always
The website and the app instruct browsers to connect over encrypted connections and never to fall back to unencrypted ones.
Nothing injected
A strict content security policy lets browsers run the code we ship and block inline and third-party scripts. The app also enforces Trusted Types.
Altered files are refused
The app’s code bundles and our own WebAssembly modules carry integrity hashes. If a file changes on the way, it does not run.
Kept apart
The app runs at its own address, separate from this website, and cannot be embedded in other pages. This website is static, with no sign-in.
Signed releases
The app, the server and this website are released once every check has passed, signed, and shipped with a list of every component they contain.
Dependencies under watch
Updates to our dependencies are checked daily, and our code is scanned for known vulnerabilities, exposed secrets and licence conflicts.
What a security review
usually asks for.
Pass these on to whoever assesses new providers in your firm.
- Data processing agreementAnnex III of our Terms
- Sub-processorsWho processes data for us, and how changes are announced
- Privacy informationWhat we process, why, and for how long
- Export and provider switchingFormats, timelines and how to leave
- Security architectureHow encryption and passkeys protect your content
- Data-centre certificationsInformation security (ISO 27001, SOC 2, SOC 3, PCI DSS), quality, environmental and energy management (ISO 9001, ISO 14001, ISO 50001)
Found a weakness?
Tell us first.
Please report it privately to security@encloq.com, with the affected feature and steps to reproduce it.