Security
How your plan is protected
You are handing over budgets, family details and a multi-year plan. These are the controls that keep them yours, and the NIS2 control areas we use as our internal baseline.
Last updated 7 August 2026
Your rights in your country
GDPR (Regulation (EU) 2016/679) · Detected country
Wherever you use Plan Our Life from, we apply one standard: full export and one-click deletion from Settings, per-account data isolation, no sale or sharing of personal data, and no advertising profiling. If your country has a data protection authority, you can complain to it at any time.
- Access a copy of your data
- Rectify inaccurate data
- Erasure (be forgotten)
- Data portability in a machine-readable format
- Object to, or restrict, processing
- Lodge a complaint with your supervisory authority
Data protection worldwide: your local data protection authority
Controls in place today
Access control by default
Every table carries row-level security tied to your account. There is no query path — internal or external — that returns another household's answers.
Least-privilege roles
Administrative views are gated behind a separate roles table checked server-side, never on values the browser can edit.
Immutable audit log
Creates, updates and deletes on your records are written to an append-only log. You can read your own entries under Settings; nobody can rewrite them.
Anomaly alerting
Repeated denied requests from the same account or address raise an alert automatically, with severity escalating on volume.
Encryption in transit and at rest
All traffic runs over TLS, and the managed database and backups are encrypted at rest by the hosting platform.
Secrets never reach the browser
Privileged keys and webhook secrets live only in the server environment. Automated jobs authenticate with their own dedicated secret.
Continuous security testing
An automated suite verifies data isolation across every table on each change, alongside a static policy scan and dependency audit.
Data minimisation
We ask for ranges rather than exact figures, never request identity documents or exact addresses, and store no payment details.
Our NIS2-aligned baseline
NIS2 sets out the cyber-risk management measures European organisations are expected to run. We use its control areas as our own checklist — risk management, incident handling, business continuity, supply-chain security, access control, cryptography and logging — because they are a sound baseline, not because we are designating ourselves an essential or important entity under the directive.
- Access is denied by default and granted per account, enforced in the database itself.
- Administrative capability is a separate, server-verified role — never a client flag.
- Security-relevant events are logged append-only and reviewed for anomalies.
- Third-party providers are listed publicly and kept to the minimum needed.
- Dependencies are audited automatically and patched when advisories appear.
If something goes wrong
We investigate suspected incidents immediately, contain first, and keep a written record of what happened and what changed as a result. Where a personal-data breach is likely to affect you, we notify the relevant supervisory authority within 72 hours of becoming aware and tell affected users directly when the risk to them is high.
Reporting a vulnerability
Email security@plantourlife.com with steps to reproduce. We acknowledge within three working days and keep you updated until it is closed. Please test only against your own account, avoid anything that degrades the service or touches other people's data, and give us reasonable time to fix an issue before publishing it. Good-faith research reported this way will not be met with legal action.
See also the data protection worldwide page and the subprocessor list.