DPP Cloud™ Backup: Mandatory Backup Hosting

Under the ESPR DPP Service Provider framework, every operator placing batteries on the EU market must maintain a certified backup of their Digital Product Passport data with an independent, certified provider. DPP Cloud Backup is that provider.

What mandatory backup means

The ESPR DPP Service Provider certification scheme (delegated act Ares(2024)8031852) will establish requirements for companies acting as DPP Service Providers — including obligations around data retention, backup procedures, and restore capabilities.

The scheme has not yet been formally adopted. No provider on the market is currently certified. DPP Cloud is on the certification pathway and will be certified when the scheme opens, expected around 2028.

The commercial case for starting now: operators who establish a backup subscription today build a continuous backup record from day one. When certification becomes mandatory, no migration is required — your record is already in place.

Two ways to use DPP Cloud Backup

Segment 1: Existing DPP Cloud operators

If you use DPP Cloud as your primary passport platform, your data is already in our infrastructure. Backup hosting is a contractual guarantee of:

• A separate encrypted backup copy of your passport data held independently of the primary Supabase instance.
• A 10-year retention period (matching the expected battery lifetime).
• A defined restore procedure and SLA.
• A daily backup timestamp visible in your dashboard.
• Proof of backup obligation compliance.

You do not need to push any data — backup is automatic once your subscription is active.

Segment 2: Self-hosting operators

Large manufacturers or enterprises running their own DPP infrastructure can use DPP Cloud purely as their certified backup recipient. Your primary system is unchanged — DPP Cloud stores a copy of what you push.

To push passport data, use the backup API endpoint:

POST https://dppcloud.co.uk/api/v1/backup/passports
Authorization: Bearer dpp_live_your_api_key
Content-Type: application/json
Body: Single passport object or array of passport objects.
Required field: external_passport_id (your system's identifier).
Optional fields: gtin, battery_type, plus any passport data fields.

On success, the endpoint returns:

{ "backed_up": 1, "total_backed_up": 47 }

The dashboard shows your total backed-up passport count and the last received timestamp.

Pricing

Billed monthly. The backup subscription is separate from the platform fee and per-passport activation billing. Self-hosting operators pay the same pricing tiers without the platform fee.

How the daily backup works (Segment 1)

Every day at 03:00 UTC, a complete encrypted snapshot of your passport data and linked records (supply chain actors, documents, carbon footprint declarations) is taken and stored securely. The backup timestamp in your dashboard updates after each successful run.

If a backup fails, the timestamp will not update — giving you immediate visibility. Contact support@dppcloud.co.uk if you see a stale timestamp.

On-demand export

At any time, you can request a complete data export from the Backup section of your dashboard. The export is generated in JSON (full Annex XIII structure) and delivered to you by email as a download link. Links expire after 7 days.

Activating backup hosting

Go to Dashboard → Backup. If your backup subscription is not active, the page shows the three pricing tiers. Click Activate on the Starter or Business tier to start the Stripe checkout. Enterprise enquiries: support@dppcloud.co.uk.

Self-hosting operators: request a demo account at dppcloud.co.uk/demo/request to get access to the dashboard and API key management. No platform fee is required.