Privacy

Last updated: 2026-08-08

What we store

• Site files you upload (HTML, CSS, JS, images, and other allowed static assets) in Cloudflare R2.
• Site metadata in Cloudflare D1: slug, optional name, password hash, management token hash, size, timestamps, status.
• Optional account email and session data if you sign in.
• Hashed upload IP for abuse and rate-limit hygiene (HMAC, not raw IP).
• Aggregate usage metrics for hosted sites (views, bytes, coarse geography). No client analytics scripts are injected into your sites.
• Abuse reports you submit (slug, free-text reason, coarse reporter hash).

Why we store it

To host your sites, protect them with passwords, let you manage them with a token or account, enforce limits, fight abuse, and improve reliability.

Retention

Password-protected (private) sites that receive no views for 90 days are deleted, including files. Public sites (when accounts ship) do not expire under that rule. You may delete a site anytime with its management token or dashboard. Deleted content is removed from active storage; residual backups may linger briefly in infrastructure snapshots.

Cookies

• Hosted protected sites: a HttpOnly cookie after password entry (about 12 hours), scoped to that site subdomain only.
• App origin (drophost.ai): session cookies for sign-in, host-only (never shared with hosted site subdomains).

Third parties

Hosting runs on Cloudflare (Workers, R2, D1, edge network). Email (magic links and expiry notices) uses Resend when enabled. GitHub is used only if you choose GitHub sign-in. We do not sell personal data.

Contact

Privacy questions: use the abuse / contact form and mention privacy, or email the operator listed in your account notices when available.