← Back to Refueler Share

Service Status

Checking…

Loading…
Incidents

Fetching status…

How it works
Technical: AES-256-GCM · RFC 3986 fragment
✓ Encrypted in your browser
Your file is encrypted before it leaves your device. The key lives only in the share link — we never see it, and neither does anyone who handles the transfer in transit.
Technical: Cashu NUT-00 blind signatures · NUT-07 double-spend ledger
✓ Transfers can't be linked to you
No account. No email. Uploads are authorised by an anonymous credential — the server grants access without learning who you are.
Technical: BLAKE3 WASM · server-side chunk verification
✓ Files arrive intact
Each chunk is hashed before upload and verified by the server on receipt. Any corruption or tampering in transit is caught and rejected automatically.
Technical: SHA-256 passphrase hash · NUT-11 Mode 1
✓ Optional passphrase lock
You can protect a share link with a passphrase. The passphrase never travels the wire — only its hash is stored, and the server checks it before issuing a download token.
Technical: Cloudflare R2 lifecycle rules · 92-day hard cap
✓ Files delete themselves
Every transfer has an expiry. When it passes, the file is deleted automatically by Cloudflare's storage layer — no manual intervention, no exceptions, no lingering copies.
Technical: rate limiting · UUID-bound credentials · Turnstile
✓ Abuse prevention
Each upload credential is cryptographically bound to a single transfer. Rate limits and bot detection prevent the service being used as a relay for bulk abuse.