Information Security Policy
Version 1.0, adopted 9 November 2026 by the Managing Director of METIS SAS. Reviewed at least once a year and after any significant change to the service.
This policy sets out how METIS SAS protects the information processed by DPP-Tool: the data our customers enter (products, passports, documents), the personal data of their users, and our own systems. It describes measures that are in place today. Where something is planned rather than done, it is labelled as such in section 13.
1. Scope and responsibilities
- Scope: the DPP-Tool application (dpp-tool.com and customer subdomains or custom domains), its database, uploaded files, API, backups, and the providers listed on our subprocessors page.
- METIS SAS is a small company. The Managing Director is the information security owner and the data protection lead, approves this policy, decides on risk treatment, handles incidents and is the contact for customers and authorities.
- Contact for security matters: [email protected]. Vulnerability reports are welcome; see security.txt.
2. Information classification
- Public: published passport pages and documents a customer chooses to make public.
- Confidential: account data, unpublished product data, private documents, API keys, invoices.
- Secret: credentials of our infrastructure, database dumps, backup decryption key.
Confidential and secret information is only accessible to authenticated users entitled to it, and is never published, logged in clear text or sent to analytics tools.
3. Access control
- Customer accounts: passwords hashed with bcrypt (cost 12); optional TOTP two-factor authentication on every plan, with single-use recovery codes; sign-in attempts capped per account (5) and per network (25) over 15 minutes; account creation capped per network; password reset links valid one hour, single use, consumed only on submission.
- Every customer record is scoped to its owner: queries on products, passports, documents and API keys always filter on the owning account. Team members are invited by the account owner.
- API keys are stored as SHA-256 hashes, shown once, can be read-only or read-write, and can be revoked by the customer at any time. Passing keys in URLs is deprecated and will be refused from 31 December 2026.
- Administrative access to production (hosting control panel, file transfer, database, DNS) is limited to the Managing Director. Automated jobs use dedicated, restricted accounts: the backup transfer account can only read the backup folder.
- Infrastructure credentials are not stored in public code repositories or in the web root.
4. Cryptography
- In transit: TLS on every page and API call (TLS 1.3 negotiated by default), HSTS with preload. Transfers of backups between servers use encrypted channels.
- At rest: passwords (bcrypt), API keys, password reset tokens and two-factor recovery codes are stored only as one-way hashes. Off-site backups are encrypted with OpenPGP (RSA-4096) before leaving our infrastructure; the private key is stored separately from the backups and from the servers that create them.
- Integrity: every published passport version is hash-chained (SHA-256). Any later alteration of a stored version is detectable, and anyone can verify a passport's chain through the public integrity endpoint.
5. Application security
- Prepared statements for all database queries (SQL injection prevention); CSRF tokens on every form, checked before any authentication logic runs.
- Strict Content-Security-Policy with a per-request nonce (no inline scripts), plus frame-ancestors, base-uri and object-src restrictions, X-Content-Type-Options, Referrer-Policy and Permissions-Policy headers.
- Uploaded documents are stored outside the web root and served only after an ownership or publication check. Sensitive directories (application code, configuration, templates, data) are refused by the web server.
- Redirects after sign-in are validated against an allow-list; forwarded client IP headers are honoured only when the request really comes from Cloudflare.
- Per-plan API rate limits and idempotency keys protect against abuse and duplicate writes.
6. Change management
- Source code is kept under version control. Each production change is prepared and tested on a working copy, the production file is backed up before replacement, and the change is verified on the live site after deployment.
- Changes that touch authentication, payments or data are tested end to end with dedicated test accounts, which are removed afterwards.
7. Infrastructure and network security
- All traffic reaches the application through Cloudflare (DNS, DDoS mitigation, web application firewall, TLS).
- The hosting provider (o2switch, France) operates the servers, applies operating-system and web-server security updates, and runs its own web application firewall and malware scanning.
- Email sent from our domain is authenticated with SPF and DKIM, and DMARC is published.
8. Logging and monitoring
- Security events (repeated failed sign-ins, blocked attempts, abnormal activity) are recorded by the application and raised as alerts to our internal monitoring journal, with IP addresses truncated before they leave our server.
- Automated checks alert us if the site stops responding, if the nightly backup is missing or too old, or if the off-site copy fails. An alarm that depends on the job it watches is not accepted: these checks run independently of the backup job.
- Web server logs are kept for 12 months and then deleted.
9. Backup and business continuity
- The database and uploaded files are backed up every night. Each dump is verified (size and presence of the core tables) before it is accepted, and kept 14 days on the hosting server, outside the web root.
- Every night, a separate server in Germany retrieves the backups over an encrypted channel, checks them, encrypts them with OpenPGP and stores them off-site for 30 days.
- A full restoration exercise was carried out on 20 October 2026 following our written restoration procedure; decryption of the encrypted off-site copy was tested on 9 November 2026.
- If our server becomes unreachable, public passport pages and public documents continue to be served from a copy on Cloudflare's network, so printed QR codes keep working.
- Objectives: no more than 24 hours of data loss (recovery point), and service restored within one business day of a major incident (recovery time), in addition to the public-passport fallback above.
10. Incident response
An incident is any event that compromises, or could compromise, the confidentiality, integrity or availability of customer data or of the service.
- Detect and record. Alerts, customer reports and reports sent to [email protected] are logged in the incident register with date, time and source.
- Assess. Determine what is affected, whether personal data is involved, and the likely risk for the people concerned.
- Contain. Block the source (network blocks, account suspension, key revocation, taking a function offline), preserve logs and evidence.
- Eradicate and recover. Fix the cause, rotate any exposed credential, restore from verified backups when needed, and confirm normal operation.
- Notify. Affected business customers are informed without undue delay, and at the latest 72 hours after we become aware of a personal data breach affecting their data, with the information required by Article 33(3) GDPR as it becomes available. Where METIS SAS is the controller, the CNIL is notified within 72 hours unless the breach is unlikely to result in a risk, and individuals are informed when the risk is high (Articles 33 and 34 GDPR).
- Learn. Each incident is closed with a short review of its cause and the measures taken. The register, including incidents that did not require notification, is kept for five years.
11. Suppliers
- Providers are chosen with preference for EU hosting and published security commitments. Each provider that processes customer personal data is bound by a data processing agreement and appears on our subprocessors page.
- Data sent to a provider is minimised: for example, our security alerting receives no name, email address or full IP address, and off-site backups are encrypted before upload.
12. Data protection
- Personal data is processed in accordance with the GDPR and our privacy policy: data minimisation, documented legal bases and retention periods, and a Data Processing Agreement for business customers.
- Customers can close their account themselves; their data is then permanently deleted from our live database after 30 days, and the last copies disappear from backups when those backups expire, at most 30 days later.
- Anyone who joins METIS SAS or works on DPP-Tool as a contractor is bound by confidentiality before receiving any access, and access is removed the day the engagement ends.
13. Planned improvements
We publish what is not done yet rather than overstate what is:
- Evaluating a move from shared hosting to a dedicated server with documented redundancy.
- Alignment with the information security requirements expected for Digital Product Passport service providers under Regulation (EU) 2024/1781 (ESPR), once the delegated act is adopted.
- DPP-Tool does not hold an ISO 27001 or SOC 2 certification at this stage.