Trust & security

Your company stays yours

Each customer is a company. People, mail, files, domains, chats and history belong to that company. Cloudn't is built so one company cannot read another, including when Cloudn't is looking at a problem.

You approve the important parts

Cloudn't can look without asking. That is how it explains what you already have.

Routine, reversible work may run when it is already covered by what you approved. Changes that alter setup, people or cost wait for a yes. Destructive work needs a clear confirmation. You see the price before anything is created.

Secrets stay out of the chat

Cloudn't talks in ordinary words. Passwords, tokens and provider keys are not placed in that conversation. Cloudn't uses tools and references, not raw credentials. Card numbers never sit with Cloudn't. Stripe stores the payment method if you start Pro.

What Cloudn't actually runs

Mail and files live with Google or Microsoft, depending on what the company chose. Domains Cloudn't operates are registered or transferred so Cloudn't can write the records mail needs. Cloudn't watches that setup. On Pro, Cloudn't fixes safe problems and asks before the rest.

If Google or Microsoft is down

Those services host the inbox and the files. If they have an outage, Cloudn't cannot invent a second copy of Gmail or Outlook. Cloudn't will still tell you what it can see, and on Pro it will act on the parts Cloudn't can fix.

What Cloudn't does not claim

This page describes how Cloudn't is built and how it behaves. It is not a certificate, a penetration-test report or a promise that nothing can go wrong. If you found a weakness, use Report security concerns.