Your data, and our proof

Two things on this page. First a summary of what we do with your data, with a link to the full policy. Then a list of every claim on this site's five presentation pages (home, features, MCP, data, FAQ), and what proves it — because a site that claims without showing is asking to be taken at its word. The Privacy and Legal Notice pages make plenty of claims too; those are legal documents that cite their own sources internally, not this table.

Three cookies, all necessary, no tracker: that's why there's no banner. Your password is never stored, your IP address is not written to the server log, and you export or delete your account with one button — and we then say exactly what leaves and what stays. A written procedure exists for a data breach. Your data is stored in the European Union — in France with OVH, our host, and in Paris with Scaleway, for mail and for backup copies, encrypted before they leave the server. Those are our two sub-processors, under contract, and nobody else processes your data for us. One reservation, stated in the policy: our host can access the server remotely from Canada and the United Kingdom, two countries the European Commission recognises as adequate.

The full detail is in the privacy policy: privacy policy →

What we don't claim. PalmaPlan isn't "GDPR certified": that label only exists at the end of a costly process we haven't started. What we've built is the file an auditing body would ask for — the record of processing activities, the retention periods, the breach procedure, the list of sub-processors. We call that certifiability, and we don't call it anything else. The database isn't encrypted at rest, and we say so here rather than leave it to guesswork.

Every claim, its proof

A claim on the site that isn't an opinion gets a row here, with its proof — an end-to-end recipe (marked R), a test, a document in the repository.

58 claims, covering the site's five presentation pages (home, features, MCP, data, FAQ) — not the two legal pages (privacy, legal notice), which cite their own sources within the document. Most of the 58 are backed by an end-to-end recipe (marked R); the rest by a measured benchmark or figure, a documented real-world trial, or a legal document written against the code that implements it.

Certifiable, not yet certified

What we've built is the file an auditing body would ask for: the record of processing activities, retention periods proven by code that runs, a breach procedure, a list of sub-processors, a privacy policy, and access, portability and erasure rights, exercisable in the product without a ticket or support request — export in one click, erasure behind typing your email and two confirmations. We call that certifiability.

What we don't have, and don't claim to have: no certification, no label, no third-party attestation. A certification — Europrivacy, for instance — covers an organization as much as a product, costs anywhere from a few thousand to tens of thousands of euros, and only makes sense once there's a commercial activity to protect. That's a decision for Xavier Baril, after commercialization.