Administration/Security
Hosting and backups
EU hosting regions for Clipido production data, and how database and infrastructure backups work.
Use this article to learn where Clipido stores production data geographically, and how automated backups protect against data loss.
Clipido's production environment is named "prod-main-eu" and is designed to keep customer data in European regions. This article covers hosting and backup. Encryption and access controls are described in "How Clipido stores and protects your data".
Where Clipido hosts production data
Clipido uses two primary cloud providers in Europe:
| Provider | Role | Region |
|---|---|---|
| "Google Cloud Platform" | Object storage, Cloud Run processing (upload, face detection, downloads), pipeline database, Kubernetes backup storage | "europe-west1" (Belgium) for compute and many buckets; multi-region "EU" for several storage buckets |
| "DigitalOcean" | Managed Kubernetes (API and web apps), primary PostgreSQL database, Redis job queues | "ams3" (Amsterdam) |
Object storage bucket names include "-eu-" in production (for example clipido-original-eu-prod-main-eu for originals and clipido-serve-eu-prod-main-eu on Cloudflare R2 for served previews).
What lives where in production
The table below maps common data types to their primary storage location in production.
| Data type | Primary location |
|---|---|
| "Account data" (email, name, preferences) | DigitalOcean Managed PostgreSQL in "ams3" |
| "File metadata" (galleries, tags, portals) | Same PostgreSQL cluster |
| "Original uploads" | Google Cloud Storage, "EU" region |
| "Previews and resized assets" | Cloudflare R2 ("WEUR") and Google Cloud Storage |
| "Temporary upload staging" | Google Cloud Storage, "EU" region (auto-deleted after "1 day") |
| "Temporary download zips and Find myself selfies" | Google Cloud Storage, "EU" region (auto-deleted after "28 days") |
| "Upload and face processing state" | Google Cloud SQL pipeline database in "europe-west1" (purged after "14 days" for completed jobs) |
Some third-party processors may process data in other regions when you use specific features (for example email delivery or video transcoding). See "Sub-processors and third-party services" for that list.
How Clipido backs up your data
Clipido maintains automated backups so data can be restored after infrastructure failure. Backups are encrypted and access is restricted to operations staff.
| Backup type | What it covers | Retention |
|---|---|---|
| "PostgreSQL (SimpleBackup)" | Full copy of the primary application database | Managed by SimpleBackup into a Clipido-owned Google Cloud Storage bucket |
| "Kubernetes (Velero)" | Cluster secrets and selected Kubernetes resources (for example custom domain certificates) | "14 days" rolling schedule |
| "Cloud SQL automated backups" | Pipeline processing database | Google Cloud SQL default rotation |
Backup copies may include personal data from your account and workspace. They are used for disaster recovery, not for routine browsing of customer content. When you request account erasure, backup copies expire on the schedule above rather than being restored for normal access.
What backups do not replace
Backups protect Clipido's infrastructure. They do not undo an archive or delete action you take inside the product. If you archive a file in Media, restore it from "Trash" before your workspace retention period ends. Archived file retention is configured under Settings → Storage and is separate from infrastructure backups.
Important
If you need confirmation of data residency for a contract or DPIA, contact hello@clipido.com for the current sub-processor register and region details.