Privacy
Last updated: June 5, 2026
What we collect
- Email + name — from Google when you sign in. Used to identify your account.
- Uploaded content — files you choose to pin. Stored on Cloudflare R2.
- Metadata — filenames, sizes, upload timestamps, CIDs. Stored in our database.
- Billing info — handled by Stripe, never touches our servers.
What we don't collect
- No analytics or tracking pixels (see cookies)
- No IP address logs beyond what's needed for abuse prevention (purged after 30 days)
- No browser fingerprints
- No third-party data sharing
Public IPFS network
Files you upload are content-addressed and announced to the public IPFS DHT so they're discoverable by any IPFS client. Don't upload anything you don't want public. CIDs cannot be made private after upload — that's how IPFS works.
Deleting your data
You can delete individual pins from your dashboard. To delete your entire account + all pins, email [email protected]. We process deletion requests within 7 days.
Note: deleting a pin removes it from our infrastructure, but if other IPFS nodes have copied the content (which is the whole point of IPFS), they retain their copies. We cannot delete content from other people's nodes.
Where data lives
- User records + auth sessions — SQLite database on a Hetzner VPS in Nuremberg, Germany. The DB file is encrypted at rest via Hetzner's disk encryption. Sessions are tied to a server-side ID; only an opaque session token lives in your browser's session cookie.
- Uploaded files (IPFS blocks) — Cloudflare R2, EU region (Frankfurt). Content is content-addressed, so the bytes are public on IPFS by design — the "privacy" angle here is purely about pinning durability, not secrecy.
- Billing — Stripe (PCI-compliant). We never see or store your card number; Stripe handles the entire payment flow and we receive only a customer ID and subscription state.
- Analytics (only if you accepted the cookie banner) — Google Analytics 4, with IP anonymisation enabled. See the cookies page to change your preference at any time.
Contact
Privacy questions: [email protected]