Security

Manicou sends orders to your sites. Here is how those orders are protected, what Manicou cannot do, and where your data lives.

Order received by www.exemple-boutique.fr
webhook-id: msg_7GqY2…
webhook-timestamp: 1792590060
webhook-signature: v1a,3vXk9…

{
  "sonde": "snd_8KqT2…",
  "domaine": "www.exemple-boutique.fr",
  "niveau": "restreint",
  "numero": 12,
  "emisLe": "2026-10-21T13:41:00.000Z",
  "expireLe": "2026-10-21T13:51:00.000Z",
  "cle": "…",
  "essai": false
}
Signature verifiedRestrictedChecked by your recipe, with Manicou’s public key.

Only Manicou can give an order

  • Each order is signed with a key only Manicou holds, in Ed25519, in the Standard Webhooks format.
  • Your recipe applies it only if it was signed less than 5 minutes ago, targets your site, has not expired and is not older than the last one applied.
  • Manicou’s public keys are copied into the recipe’s settings, never read online. Someone who hijacked Manicou’s address could not slip in their own key.
  • A refused order, a Manicou outage or a cut network change nothing: your recipe keeps the last valid order.

Manicou has no hold on your site

  • No hosting key, no access to your server.
  • Your visitors’ traffic never goes through Manicou. Your recipe reads its order at most once a minute.
  • The code of each recipe is public, to read before you install it, and needs no package.
  • If you connect GitHub, Manicou can read your repository to know its software, and launch the update workflow you added there. Each access covers only that repository and that action.

Your sites’ vulnerabilities stay yours

  • Manicou names a vulnerability only on a site whose domain you have proven.
  • The free test, open to anyone, counts a site’s probable vulnerabilities by severity, without ever naming them.

Where your data lives

  • Manicou’s database and files are stored in Europe, with Cloudflare.
  • Payments go through Paddle, which keeps your card and your invoices. Manicou keeps only the state of your subscription.
  • No password. You sign in with a link sent by email, or with Google.
  • Sessions and API keys are stored hashed, your alert channel addresses encrypted.
  • You export your data whenever you like, and everything is erased 30 days after the account is closed, except the address of your protected sites, kept for a year so that a protection you forget keeps them open.

The details are in the data processing agreement, the privacy policy and the order format.

Read the recipes’ code