Administration/Security
Data protection
How Clipido encrypts data, controls access, and keeps account and media files secure in production.
Use this article to understand how Clipido stores your account data and uploaded media, and which security controls protect that data in production.
Clipido processes account details, authentication data, and the photos and files you upload. This article covers storage and protection at a high level. Hosting regions and backup copies are covered separately in the Security and Privacy collection.
Encryption in transit and at rest
All traffic between your browser and Clipido uses TLS over HTTPS. Clipido terminates TLS at load balancers and ingress before requests reach application services.
Data at rest is encrypted by the cloud providers Clipido uses:
| Layer | Protection |
|---|---|
| "Object storage" (original uploads, previews, temporary files) | Google Cloud Storage and Cloudflare R2 use provider-managed encryption (AES-256 by default) |
| "Application database" | DigitalOcean Managed PostgreSQL uses encryption at rest |
| "Pipeline database" | Google Cloud SQL uses encryption at rest |
Clipido does not expose your primary database to the public internet. The PostgreSQL cluster accepts connections only from Clipido's Kubernetes cluster and approved backup services, with SSL required.
How Clipido stores your files and metadata
When you upload media, Clipido stores:
- "File metadata" (gallery membership, tags, uploader reference, timestamps) in PostgreSQL
- "Original files" in a private Google Cloud Storage bucket with public access blocked
- "Processed previews and served assets" in Cloudflare R2 and Google Cloud Storage buckets that are not publicly writable
Temporary staging buckets (uploads in progress, download zips, selfie uploads for Find myself) have automatic lifecycle rules that delete objects after a fixed period.
Authentication and session security
Clipido signs you in with short-lived JSON Web Token (JWT) cookies stored as httpOnly cookies in your browser. Typical limits:
| Token type | Default lifetime |
|---|---|
| "Access token" | "15 minutes" |
| "Refresh token / session" | "14 days" (club admins can configure up to "30 days" under session settings) |
| "Email login code" | "15 minutes" |
| "OAuth or SAML sign-in handoff" | "10 minutes" |
Refresh tokens cannot be read by page JavaScript because they use httpOnly cookies. Production signing keys and database passwords are stored in a secrets manager and injected into services at runtime, not in source code.
Access controls inside Clipido
Inside the product, access to your workspace follows group membership and portal authentication settings. Uploaded files are not public on the internet by default. Only people you invite, or recipients you publish a shared gallery or workspace link to, can reach files you choose to share.
Clipido engineering and operations staff access production infrastructure through authenticated cloud consoles with role-based, least-privilege permissions. Customer content is not used for model training.
What this article does not cover
This article describes platform-level protection. It does not replace your own access choices inside Clipido (who you invite, which galleries you publish, or whether a workspace requires sign-in). For face recognition data specifically, see the Security and Privacy article on "Face recognition and biometric data".