Every file, organized automatically
Files that arrive as email attachments end up wherever the person who opened them put them. Uploads here land in a folder per request, grouped by recipient, with the metadata you need to find them again.
Foldered as it arrives, not filed afterwards
There is no filing step. A file uploaded against a request is already in that request's folder, under the recipient who provided it, with its name, size, type, and upload date recorded.
- Auto-organized folders per request
- Grouped by recipient with full file metadata
- Uploads capped at 10 MB per file
- Accepted types: PDF, ZIP, XLSX, DOCX, JPEG, PNG, WebP, CSV, and TXT
DOC-2024-014
Acme Holdings · 4 files
Nadia Okafor
nadia@acme.co
incorporation.pdf
Jul 1 · uploaded
ownership-chart.png
Jul 1 · uploaded
Liam Chen
liam@acme.co
bank-statement-q1.pdf
Jul 2 · uploaded
revenue-2024.xlsx
A bundle someone else can open
Exporting a request produces a ZIP with a folder per recipient. Each folder holds that recipient's uploaded files plus a generated archive PDF of their completed form, so the answers and the evidence travel together.
- One folder per recipient, with an archive PDF of the completed form
- Self-describing months later: what was asked, answered, and supplied
- Google Drive integration on every plan
- Webhooks with delivery logs and Zapier on Growth and Scale
One folder per recipient, each with their uploaded files and a generated archive PDF of the completed form.
Scanned before it is stored, encrypted once it is
Every uploaded file is scanned for malware before it reaches storage, using an antivirus engine running on our own infrastructure — the file itself is never sent to a third-party scanning service. A file that fails is rejected at upload.
- Malware scanning on our own infrastructure, fail-closed at upload
- AES-256-GCM encryption at rest for files and sensitive answers
- Scanning detects known malware and is not a guarantee that a file is safe
Upload pipeline
Every file, every time
Scanned
Checked for malware on our own infrastructure
Encrypted
AES-256-GCM before it touches disk
Stored
Bunny.net's London zone, encrypted with our key
invoice-final.pdf
Refused at upload — never reached storage
Files are never sent to an outside scanning service. Anything that fails is refused at upload.
Hosted in the UK, or in your own bucket
Your requests, answers and uploaded files are stored in the United Kingdom — account data on our own servers in Erith, uploaded files in Bunny.net's London storage region, encrypted with our own key before they leave our servers. Nothing is replicated outside the UK.
- UK hosting on every plan
- Bring your own S3 bucket on the Scale plan
- Storage quota scales with your plan, with 25 GB packs available on any plan
Erith, United Kingdom
Our servers — files in Bunny.net's London zone
Add 25 GB packs on any plan
Your own S3 bucket
Point ClientGather at storage you control