Cloudn't is on the way.

Cloudn't

Report security concerns

If you found a weakness in Cloudn't, tell Cloudn't privately. Do not post it in public first. Do not test it against another customer’s company.

Last updated 8 September 2026

What to send

  • What you saw, where you saw it, and how to repeat it if you know.
  • Dates and times. The product you were using (this website, or the signed-in app).
  • Screenshots only if they do not contain passwords, keys or another company’s data.

What not to send

  • Passwords, session cookies, backup codes, or copies of keys.
  • Destructive tests against live companies. That is not a report. That is Platform rules.

How to send it

Sign in and tell Cloudn't that this is a security report. If you cannot sign in, use Press & media and say it is a security report, not a story. Cloudn't will look before anything is said in public.

What happens next

Cloudn't will confirm that the report arrived, look at it, and tell you when the weakness is closed if you left a way to reply. There is no public bug-bounty programme on this page. A report still matters. Do not ask for payment as a condition of sending it.