About Gidocs
Open source PDF and document tools that keep sensitive documents out of public storage.
Why this project exists
Many PDF tools ask you to upload a contract, a payslip, a national ID, a medical record, or a signed contract to somebody else's server, then keep it. A file that lands in a public bucket can leak through a bug, a misconfigured setting, or an employee with a bad day.
Gidocs takes the opposite position. The project is built so that your document is the least interesting thing about it: it is processed, handed back to you, and forgotten.
How your files are protected
No database. Gidocs has no database and no permanent file storage. Nothing you upload becomes a record that can be browsed later.
No accounts. There is no sign-up, no login, no history, and no file library. Without an account, there is nothing for a stranger to browse and nothing to leak.
Temporary processing only. Every request gets its own temporary working folder. When the response is sent, that folder is deleted. Background jobs (Office conversion, PDF to images, OCR) expire on a timer as well, and a cleaner removes anything left behind.
Files are treated as hostile input. Uploads are accepted based on their real file signature, not the name or the browser supplied type. Your original file name is never used as a path, and neither file contents nor original names are written to the logs.
No third-party tracking. There are no analytics scripts and no trackers following you across the web.
Preview stays on your device. When a tool needs to show you a page, for example the Sign PDF preview, that rendering happens in your own browser. The preview is never uploaded.
What Gidocs deliberately does not do
No accounts and no billing. No saved history. No shareable links. No long-term storage of your documents. These are not features waiting to be unlocked later; they are the reason the project is built this way.
Honest limits
To convert a file, the file does pass through the server that runs the tool. That is unavoidable for PDF conversion: the work happens on a machine. What we guarantee is how short that stay is and what is left behind afterwards.
If your documents are sensitive enough that even a brief server visit is not acceptable, self-host Gidocs and run it where you control the machine. The whole project is open source precisely so you can do that.
Open source
Read the source, run it yourself, or help improve it on GitHub. Gidocs is released under the AGPL-3.0 license.