Document Requests
A client's documents, photographed from their phone and received encrypted, without chasing attachments.


Opening a file, renewing a lease, checking eligibility: you need an identity document, a proof of address, a proof of income. They arrive by email, one at a time, blurry or incomplete, and then stay in an inbox.
A request brings together a client, the documents to provide, drawn from a catalogue you manage, a deadline and a note shown at the top of their page. It goes out by email or text message. The client needs no account and no password: the link they receive is their only key, and it only opens an upload.
On a phone, Take a photo opens the camera directly, one card per document; from a computer, they attach an image or a PDF. Files go straight from the browser to the storage, never through the server, and reach you through the transfer's secure link.
Retention is set per document: when a request mixes several, the shortest period wins. Reminders only name what is still missing. Past the deadline, the link stops working.
⚠️ Every step, from sending to each document uploaded, is written to the same hash-chained log as the transfer's accesses: the access certificate tells the whole story. The privacy bridges then record each destruction in the Law 25 register.
1 add-on module
Privacy (Law 25)Each expiry policy tied to the retention schedule, and a request's destruction named in the register.
The documents in a request are personal information, often sensitive. This bridge ties each expiry policy to a retention schedule rule, with its legal basis and destruction method; the policy form says whether the two periods agree, and corrects nothing on its own. Each document type declares the category of personal information it carries, and the destruction register entry names the request, the client and the documents destroyed. It destroys nothing itself.
Shall we look at your case together?
Tell us what you run today. We will tell you honestly whether Symbifox helps or not.
The catalog grows almost every month.
What gets added, what we learn deploying it, and nothing else. You leave whenever you want.
One confirmation email, and nothing before you follow its link. Then 10 welcome emails, one a week, then the updates. No tracker, no resale.