Backups and security

Backups. Every night we copy the platform database, the databases of apps and the files of every paid site to storage in the Netherlands, with a copy at Cloudflare stored under EU jurisdiction. We keep those copies for ninety days. Each copy is checked after it is made: if it is missing or suspiciously small, that is reported the same night instead of quietly rotting for three months. Restoring has been tested, not just described.

For a trial site, the files you published are the backup: you keep the source in your own tool or repository, and republishing takes seconds. For a Website you put back one of your earlier publications yourself in the portal (we keep the last five, the current one included), and you request a restore of a database to an earlier day. Need a paid site back as it was on an earlier day? Ask support.

Encryption. Everything runs over HTTPS with a certificate we arrange and renew automatically. Traffic to the platform and to your own domain is never plain. Stored data sits on encrypted disks.

Access. Only the owner has administrative access to the platform. Passwords are stored as hashes, never readable, and logging in is throttled after five failures for the same address and email address.

Headers. Every page is served with the usual protective headers: no content sniffing, no embedding in a frame elsewhere, a strict referrer policy, and HTTP Strict Transport Security.

What you are responsible for. The content of your own site and app, and the strength of your own password. If your app talks to a database, keep secrets out of the source and put them in the environment variables in the portal.

Found something wrong? Report it through support with the word security in the subject. We look at it as soon as we can, and we never hold it against the reporter.