← LinkedIn demo

AILANG×tuta.com

AI privacy generated 2026-05-14
agent-ready privacy portable

tuta.com scored 6/10 on privacy.

The radar shows AILANG-readiness across three commercial concerns. High means tuta.com is already strong there; low means AILANG could meaningfully help.

Why privacy scored 6/10
  • Page mentions end-to-end encryption, E2EE, zero-knowledge, or client-side encryption — data is sealed before leaving the client.
  • Page mentions SOC 2, ISO 27001, GDPR, HIPAA, or CCPA — formal commitments to data-handling practice.
  • Page mentions "we do not sell", "no third-party sharing", "privacy-first", "data minimization", or "purpose limitation" — explicit constraints on data flow.
  • Fewer than 5 distinct external script/image domains — indicates fewer third-party data flows.
  • Page mentions EU hosting, data residency, on-premises deployment, or sovereign cloud.

Full breakdown ↓ · View rubric ↗

Individuals and businesses seeking a secure, private email and communication service that protects sensitive data from tracking and unauthorized access.

Tuta provides a secure, end-to-end encrypted email service for private users and businesses. It emphasizes a 'security first' approach, utilizing open-source technology and self-built infrastructure to ensure privacy, prevent tracking, and protect user data across emails, calendars, and contacts. All data is encrypted by default, including a local search index.
End-to-end encryption Open source Quantum-safe cryptography Secure email service Encrypted mailbox Local search index

What AILANG Parse sees on tuta.com

Structural extraction — the same content an AI agent would consume from this page.

16 headings0 images4 lists0 tables1 linksHTML parsing by AILANG Parse

7 sections — page skeleton

1 main 1 article 5 sections

16 headings

Secure emails at the tip of your finger Security and privacy go hand-in-hand Control of the software stack Security End-to-end encryption TLS encryption

4 list items

**Who pays for it?** The users or the advertisers? If the answer is "the advertisers", th… **Who controls the tech stack?** This is a very technical but crucially important questio… **What data is encrypted end-to-end (E2E)?** Many providers claim that their service prov… We do not use PGP, but a slightly different implementation (initially based on AES 256 an… We do not search through your data on the server because it is encrypted there. Instead T… We do not offer IMAP as it would only work if we sent **decrypted** data to your device. … Tuta is based on the data privacy principles of "data minimization" and "privacy by desig… All user data is stored end-to-end encrypted in Tuta (except for metadata such as email a… We have technical and organizational measures in place which protect your data to the max… Tuta provides an Order Processing Agreement with legally binding data protection guarante… Tuta blocks images by default. No external content is loaded when you open an email unles… Tuta strips all header information (IP address) from emails sent to protect your privacy.
Show the full extract — what AILANG Parse pulled from this page
# Security at Tuta | Tuta


[Login](https://app.tuta.com/)[Sign up](https://app.tuta.com/signup?websiteLang=en)Products[Download](/#download)[Pricing](/pricing)[Business](/business)Why Tuta
[Security](/security)[Privacy Guide](/privacy)[Sustainability](/sustainability)[Encryption](/encryption)[Team](/team)[Open Source](/open-source)[Community](/community)[Email comparison](/email-comparison)[Discount](/discount)[Blog](/blog)[Jobs](/jobs)[Support](/support)
[Login](https://app.tuta.com)[Sign up](https://app.tuta.com/signup?websiteLang=en)

Secure email made for you 
Tuta: The most secure email service, and the easiest to use.[ Create free account   ](https://app.tuta.com/signup?websiteLang=en)

## Secure emails at the tip of your finger

All-round encryption, no tracking, open source - there are lots of factors that make Tuta the most secure email provider in the world. Explore Tuta's security features in detail and learn how its various security measures protect your sensitive data.

### Security and privacy go hand-in-hand

When evaluating the security and privacy of any online service, always ask yourself the following questions:

1. **Who pays for it?** The users or the advertisers? If the answer is "the advertisers", the service can never offer a truly secure and private solution. Its top priority is the advertisers’ interest by helping them to identify target audiences based on users’ data and to serve them ads.  Protecting users' privacy always comes second with such a business model.
2. **Who controls the tech stack?** This is a very technical but crucially important question. If a service uses third-party 'tech' such as Dovecot, Roundcube, Google reCaptcha or Google Push, you know for sure that security and privacy cannot be its core priority as the provider knowingly leaks information to others - without warning the users about this. This is another reason why you should choose a service that is open source and doesn’t rely on integrations with closed-source software.
3. **What data is encrypted end-to-end (E2E)?** Many providers claim that their service provides secure email and that the data stored with them is 'encrypted'. What makes this question so important is **how is the data encrypted?** Because only when data is encrypted end-to-end, it is truly inaccessible to the online service as well as to other third parties. Only then the service can be considered as offering **secure email**. That's why simply "encrypting" data is not sufficient, the data must be **encrypted end-to-end**.

### Control of the software stack

Many email services, even secure ones, use third-party tech like Dovecot, Roundcube and others to build their own products. Every time a so called secure service uses third-party applications, it becomes more difficult to secure said service. The reason is simple: Every service included in the code executes code. Any services' security can't get better than that of its dependencies. Every dependency to third party code must be maintained and security updates need to be applied immediately. In addition, every third-party service can potentially track the users, send data to its own servers etc. That’s why we at Tuta only use open source code that we have vested ourselves before using it. This way we make sure ourselves that the [open source tools Tuta does use](https://tuta.com/blog/love-free-software-day) are secure: We regularly run security reviews of these tools as well as of our own clients, for instance when we pushed our desktop clients [out of beta](https://tuta.com/blog/desktop-clients-end-beta).

Of course, we at Tuta can't re-invent the wheel either. But we have built our entire clients - web, Android, iOS, and all desktop clients - on our own. Plus, we have a strong focus on security in our whole development workflow. All developers share the same DNA: privacy and security first.

**One main differentiation of Tuta is that we build all major parts of Tuta ourselves, even outside of the core email functionality such as our captcha, our push notification service on Android and more.**

Only with open source - of our own clients and of the software that Tuta depends on - tech-savvy people can audit the code and verify that Tuta is doing what we promise: Securing your private emails to the maximum.

*Check here [why we recommend to choose our secure desktop clients](https://tuta.com/blog/desktop-clients-tutanota) for Linux, Windows and macOS and [why it is so important that we have built our own open source captcha as well as an alternative to Google Push on Android](https://tuta.com/blog/open-source-email).*

### Security

**We follow the concept of “security first”.**

When offering a secure email service, people trust that your security is bullet-proof. To us, this means that there can never be a compromise when it comes to security. **Security must be baked into the code so that you can easily add usability on top of that - not the other way around.**

This concept of "security first" has led to several development decisions that today guarantee the top-notch security of Tuta:

- We do not use PGP, but a slightly different implementation (initially based on AES 256 and RSA 2048), which lets us encrypt much more data (subject lines) as well as encrypt all other features that we add to Tuta such as contacts and calendars - which are all 100% encrypted. We have replaced RSA with ECDH (x25519) Kyber-1024 to release [quantum-safe cryptography](https://tuta.com/blog/post-quantum-cryptography) to all Tuta users. In the future, we plan to also support forward secrecy.
- We do not search through your data on the server because it is encrypted there. Instead Tuta builds an encrypted search index, which is stored locally on your device or in your browser  and searched there. This enables you to search through your entire emails (sender, recipient, subject line, body, attachment) locally while protecting your privacy.
- We do not offer IMAP as it would only work if we sent **decrypted** data to your device. Instead we have built our own [open source desktop clients](https://tuta.com/blog/desktop-clients), which store your data encrypted. The desktop clients are also signed so that everyone can [verify](https://tuta.com/support#verify-desktop) that the client is running exactly the same code as the code published on GitHub.

**When you create a secure email address with Tuta, you can be sure that your data is kept secure.**

## End-to-end encryption

**Encrypted mailbox, calendar, contacts.**

From the start, we at Tuta made sure that as much data as possible is E2E encrypted. **Tuta was the world's first end-to-end encrypted email provider and, to this day, it is the email service that encrypts more data than any other.**

Tuta encrypts all data by default: Email, calendars, contacts. The end-to-end encryption provided by Tuta ensures that your data is secure and private, even if it falls into the wrong hands.

**Tuta's servers only store the encrypted data**, and the decryption key is only available to the user. This ensures that even if your internet connection was intercepted or in the extremely unlikely scenario that someone were to hack our servers, your data remains secure.

With its built-in encryption Tuta makes security easily accessible to private users and [businesses](https://tuta.com/business) all over the world. To decrypt your data, you simply login to your secure email address with your password, that’s it. You can easily login via a web browser, via the Tuta apps for Android and iOS, or via the Tuta desktop clients for Windows, macOS and Linux.

**How to send a secure email to anyone.**

Tuta lets you send secure emails (E2E encrypted) to anyone with a shared password. This means that the message is encrypted on the sender's device and can only be decrypted by the recipient's device. You can easily exchange sensitive conversations or files online, knowing that all data sent via Tuta is securely encrypted end-to-end. You can easily send encrypted emails to external recipients by defining a password. The password is valid for all emails that you exchange with this person, there’s no need to define a new password for each email like with other secure providers.

**Zero-knowledge calendar.**

Tuta comes with an end-to-end encrypted [calendar](https://tuta.com/calendar) that lets you schedule and store all your appointments confidentially. Our calendar is an outstanding achievement because not only all data is encrypted, but also the reminders are E2E encrypted. Even the time when a notification is sent to the user is obscured from our servers so that we remain in the dark about all our users’ appointments.

### TLS encryption

**Securing the email protocol**

When sending emails with Tuta, you have clearly chosen the most secure option as Tuta allows to automatically encrypt emails end-to-end.

However, sometimes you might want to send and receive unencrypted emails to and from contacts that don’t use Tuta, when sharing a password with them would be inconvenient. It is much harder to secure these emails because in such a case the email provider can only encrypt the transmission - not the data itself. Besides that, other services are involved, like the recipient’s email provider, which need to make sure that the transmission is completed securely.

To secure unencrypted emails as well as possible, we adhere to the highest possible standards of the SMTP email protocol.

**Tuta supports MTA-STS. This standard should be supported by all email services by now because it is to an email what strict HTTPS is to a website: It enforces transport encryption (TLS) whenever TLS is possible.**

Tuta also supports SPF, DKIM and DMARC. These three protocols are necessary to harden the infrastructure against intrusion from phishing and spam emails.

Tuta uses strict CSP (Content Security Policy), an HTML sanitizer for showing unknown content (in emails) to prevent XSS-attacks, and, by default, does not load external content from other servers (pictures and videos in emails). The user can choose to have external content shown with a single click or tap, if they trust the sender.

Check here to see how well Tuta scores on [Securityheaders.io](https://securityheaders.com/?q=https%3A%2F%2Fapp.tuta.com%2F).

### Maximum login protection

**Tuta never transmits your password to the server.**

When you login to your secure mailbox, Tuta hashes and salts your password before transmitting the hash to our servers. It is impossible to derive the actual password from this hash, so no one can know your password, not even we at Tuta. To protect your password, we use Argon2 and SHA256.

Tuta also provides [two-factor authentication (2FA)](https://tuta.com/blog/why-u2f-is-important) to add an extra layer of security. To secure your login credentials, you can use TOTP or U2F. We recommend using U2F with a security device as this is the most secure form of two-factor authentication. This ensures that only the authorized user can access their account.

*Check out our [online security guide on how to keep your emails safe from hackers](https://tuta.com/blog/email-security-guide-online).*

### Zero-knowledge Architecture

Tuta uses a zero-knowledge architecture, which means that the user's data is never stored in plain text on Tuta's servers. **Tuta's servers only store the encrypted data**, and the decryption key is only available to the user. This ensures that even if Tuta's servers are hacked, the data remains secure.

### GDPR-compliant

The European GDPR requires companies to secure emails containing sensitive data of EU citizens. Businesses are required to safeguard personal data, even when in transit.

You can now save time and money by hosting all your business emails encrypted on Tuta's secure servers. With Tuta, there is no need to use a plugin or a complicated encryption software on top of a bloated enterprise email solution that used to be a good fit for 
page preview · the URL we fetched https://tuta.com/security ↗
Screenshot of tuta.com

Couldn't render a preview for this site. Open the URL in a new tab ↗

Screenshot via thum.io

tuta.com scored 6/10 on privacy. AILANG opportunity is therefore 4/10. Here's where it would land first.

Information-flow labels on customer data

Mark fields containing PII at the type level. The compiler refuses to let a labelled value reach a public sink without an explicit Declassify boundary. Privacy by type, not by code review.

type Customer = {
  email:    string<pii>,
  postcode: string<pii>,
  signupDate: string
}
-- assigning customer.email to a log line is a type error.
→ AILANG docs

Capability scoping

A function declares the network endpoints, file paths, and AI providers it touches. Anything outside the declaration is rejected by the runtime. "This part of the system can talk to Stripe; it cannot talk to anyone else" is enforced.

func chargeCard(c: Card) -> Result[Receipt, Error]
  ! {Net @endpoint="api.stripe.com", AI @limit=0}
→ AILANG docs

Three-runtime deploy

The same module runs in the browser via WASM, on Cloud Run, and as a native binary. Sensitive workflows can stay in the user's tab — no server ever sees the data.

-- Browser: load AILANG WASM, run the module in the user's tab.
-- Cloud Run: same .ail file packaged as a container.
-- Native CLI: same .ail file, ailang run.
→ AILANG docs

How this page was made

func sketchSite(url: string<pii>, topic: Topic) -> Sketch
  ! {Net @limit=1, AI @limit=5, FS @limit=4, Process, Declassify}
SignalTopicResultPointsAILANG primitive
agent.json referencedagent-ready0/1ailang serve-api generates A2A agent cards automatically — bonus if you're an early adopter
openapi.json referencedagent-ready0/2ailang serve-api generates OpenAPI 3.1 from Hindley-Milner type signatures
MCP endpoint referencedagent-ready0/2ailang serve-api --mcp-http exposes typed functions as MCP tools
Public API docs linkedagent-ready0/2ailang serve-api hosts Swagger + ReDoc at /api/_meta/ by default
Webhooks documentedagent-ready0/2ailang serve-api handles webhooks as typed handler functions with effect-tracked side effects
Rate limits documentedagent-ready2/2Capability budgets — Net @limit=N is the symmetric server-side primitive for what agents see as rate limits
Streaming / SSE endpointagent-ready0/2std/stream — ssePost and Stream effect handle event-source endpoints with typed event types
Sandbox / test environment offeredagent-ready0/2ailang --ai-stub plus mock effect handlers — deterministic, capability-scoped fakes for any effect, including Net and AI
Authentication documentedagent-ready0/2std/jwt for verification, IFC labels (string / string) to keep credentials out of public sinks at the type level
Idempotency keys documentedagent-ready0/2Pure functions are idempotent by construction; requires/ensures contracts express idempotence as a static guarantee
AG-UI streaming protocolagent-ready0/1std/stream — the AG-UI event lifecycle (RUN_STARTED → TEXT_MESSAGE_CONTENT → TOOL_CALL_RESULT → RUN_FINISHED) is a textbook sum type. ADTs + exhaustive pattern matching make every event-type branch a compile error to skip.
HTTP 402 agent payments (x402 / pay-per-crawl)agent-ready0/1Net @endpoint-scoped capability budgets bound payment destinations; requires { amount <= budget } gates the payload; IFC labels keep the signed payment key out of public sinks. Same primitives cover x402 payload signing and Cloudflare's crawler-price negotiation.
AP2 Agent Payments Protocolagent-ready0/1Mandates ARE contracts. requires { intent.price <= mandate.maxPrice } + ensures { cart.total <= intent.price } is a one-to-one translation of an Intent/Cart Mandate into AILANG. Z3 can verify the bounds at compile time.
UTCP tool-calling protocolagent-ready0/1Typed function signatures are the manifest. ailang serve-api emits the same metadata as a UTCPManual (name, input/output schema, native endpoint) — direct-call discovery without a proxy server.
End-to-end encryption documentedprivacy2/2IFC labels (string) force decryption to flow through a typed boundary; the compiler refuses to publish sealed values without explicit declassification
Compliance certifications citedprivacy2/2requires/ensures contracts express machine-verifiable claims; capability budgets bound audit-trail effects; effect rows leave nothing un-declared
Data minimisation languageprivacy2/2Capability scoping — each Net call declares its endpoint in the effect row, so "doesn't sell" becomes a type-system-enforceable claim, not a marketing one
Third-party domains restrainedprivacy0/2Capability scoping — each Net call declares its endpoint in the effect row
Data residency / on-prem languageprivacy0/2Three-runtime deploy — same module runs in WASM (browser), Cloud Run, and native CLI
Single-vendor LLM languageportable2/2std/ai multi-provider — switch from Anthropic to Gemini to OpenAI without rewriting
Multiple AI providers citedportable0/2std/ai — one Step API across Anthropic, OpenAI, Gemini, OpenRouter, Ollama, and custom-package providers
Cross-runtime / deployment portabilityportable0/2Effect handlers as runtime adapters — same .ail runs as WASM in the browser, a Cloud Run container, and a native CLI; only the handlers change
BYO key / model-agnosticportable0/2AILANG WASM — the full interpreter ships as a browser bundle, so caller-held keys (BYOK), offline apps, and embedded demos all work client-side