This page says exactly what Uploaditz does and does not do with your data. No marketing language — every claim here is enforced by code and can be verified in your own storage logs.
File bytes move directly between the user’s browser and your storage. Uploaditz issues a short-lived signed link and records the result. It never receives, caches or proxies file contents.
Files are uploaded in parts. Each part’s SHA-256 hash is computed in the browser and bound into its signed link, so the storage itself rejects any part whose bytes differ. Downloads are verified against the same hashes.
Upload links are valid for 15 minutes, download links for 5. A link can only be used for the exact object, size and hash it was signed for.
Every upload, download, request, invite, archive and refusal is written with who, when, from where and how many bytes. The audit table cannot be updated or deleted by the application. It is exportable and kept for the life of the account.
Uploaditz has no code path that destroys a file. Cleanup archives the record and gives your storage admin the object keys. Deletion in your storage is your act, or a lifecycle rule you set.
Managed storage is a dedicated bucket per customer in the region you choose: US East (N. Virginia), US West (Oregon), EU (Frankfurt) or EU (Ireland). Data does not leave that region.
| Data | Stored by Uploaditz | Where it lives |
|---|---|---|
| File contents | Never | Your storage only |
| File names, sizes, folders, hashes | Yes | Uploaditz catalogue (encrypted at rest) |
| Users, roles, sites, clients | Yes | Uploaditz catalogue |
| Audit events | Yes, append-only | Uploaditz catalogue |
| Your storage credentials | Never in the database | Encrypted secret store, used only to sign links |
| Passwords | Never in plain text | Identity provider (hashed), or Google sign-in / magic link |
All traffic is TLS 1.2 or higher. Managed storage buckets are encrypted at rest with AES-256 by default, versioned, and blocked from any public access at the account level. Bring-your-own storage keeps whatever encryption you have configured; Uploaditz does not weaken it.
Four roles: Admin (organisation-wide), Manager (one per site), Team (members of a site) and Client (a customer or supplier company). A client sees only its own files and files your team uploads for it. A team member sees the clients of their site. Sites are invisible to each other. Outsiders can only be invited by someone inside your organisation, and every invitation is audited.
Each managed customer gets their own bucket — not a folder inside a shared bucket. Buckets are created with public access blocked, bucket-owner-enforced ownership, default encryption, versioning, and a lifecycle rule that aborts abandoned multipart uploads after two days. The credentials that provision customer buckets cannot delete a bucket; that permission is explicitly denied.
Because Uploaditz never holds file contents, it cannot scan them. Scanning belongs where the bytes are: AWS GuardDuty Malware Protection for S3 or Microsoft Defender for Storage on your side. We document the setup for each storage option. This is a deliberate trade — a service that can scan your files is a service that has your files.
The upload and download path is exercised end to end every night against real storage — a 1 GB file up and down with per-part verification, resume after interruption and tamper rejection. A failed run is treated as an incident.
Found something? Email uploaditz@grandfieldmedia.com. We answer within two business days and credit reporters who wish to be named.
Uploaditz is operated by Grandfield Media Private Limited. We follow GDPR principles for EU customers (data minimisation, residency, right to export and erasure of catalogue data) and will sign a data processing agreement on request. We do not yet hold a SOC 2 or ISO 27001 certificate; we say so rather than imply otherwise.