FullbackGet started

You are handing us a write token. Here is what we do with it.

Fullback holds a copy of your content and a credential that can change it. Both are treated as the liability they are.

Token storage

Your Content Management API token is encrypted with AES-256-GCM before it ever reaches the database. The encryption key lives outside the database, is held in memory only for the length of a backup or restore job, and the token itself is never written to a log.

Writes

Nothing writes to your space except a restore you've explicitly confirmed. Scheduled backups only read — through Contentful's Sync API, at roughly 7 requests a second, comfortably inside Contentful's own rate limit.

Snapshot storage

Snapshot content — entries, content types, tags — is stored as encrypted objects in Cloudflare R2, not in our own database. Postgres holds only the metadata index: which snapshot exists, when, and how many entries it covers. Snapshots are deleted at the end of your plan's retention window, not archived elsewhere.

Access

Production access — the database, object storage, and the encryption key — is limited to the founder today. There's no support team with standing access to your content.

The short version

Encryption at restAES-256-GCM (tokens)
In transitTLS
Data regionUS (AWS us-east-2 + Cloudflare's network)
Retention3 / 7 / 60 days
SubprocessorsNeon, Cloudflare R2, Fly.io, Stripe, Resend
No SOC 2 report yet — it's on the roadmap. Ask and we'll send the current control list.