Technical sheet · data processing
Where your documents are processed
SecureLocalSuite · securelocalsuite.com
Version 1.0
Facts checked against the code on 23 July 2026
A short document for professional firms that must justify the use of a software tool on client data. It states where processing happens, what leaves the device and what stays on it.
Tools covered
Every tool listed processes files entirely in the browser, on the user's own device. There is no server receiving, processing or storing the documents.
DocRazor (PDF)
merge, split, page organisation, redaction, signing, cropping, highlighting, rotation, numbering, watermark, compression, password protection, image conversion, image extraction, PDF ⇄ Markdown
Privacy Sanitizer
detection and masking of personal data in text, with a reversible dictionary
MindMap Extractor
text extraction from documents and mind-map building
Media Razor
trimming, compression and conversion of video and audio
What never leaves the device
- The document you open, in any form: not whole, not in pieces, not as a preview or thumbnail.
- The text extracted from the document, the personal data detected and the areas you choose to redact.
- The file name, its size, its metadata and any fingerprint identifying it.
- The passwords you set to protect a PDF.
What does leave, and when
The list is complete. None of these connections carries documents or their content.
| Data | When | Recipient |
|---|---|---|
| The contact form content | only if you fill in and submit the form | Formspree (form provider) |
| Visit statistics: page opened, referrer, country, device type and browser | on every page view | Vercel (hosting provider) |
What is stored on the device
In the browser, readable and erasable by whoever uses the tool. None of these values leaves the device.
dr.usage.v1count of today's operationsdr.premium.v1whether advanced features are unlocked in this browserdr.proClicks.v1how many times the PRO panel was openedslc_langthe chosen language (cookie, to carry it between tools)
What we are not able to do
These are not commitments: they follow from the architecture. A document that never reaches us cannot be processed by us in any way.
- We cannot read your documents: they never reach any server of ours, so there is nothing to read.
- We cannot hand them to a third party, not even on an authority's request: we do not have them.
- We cannot lose them in a data breach: an archive that does not exist cannot be breached.
- We cannot reconstruct who you are: there are no accounts, no sign-ups, no identifier following you.
How to verify it yourself
There is no need to trust this document. Open the browser developer tools (F12), Network tab, and use a tool on a file: no upload of the document appears. Alternatively, disconnect from the network after loading the page: the operations keep working.
Declared limits
- Processing happens on your device: the safety of the result also depends on your browser, its extensions and whoever has access to the machine.
- Automatic detection of personal data is an aid, not a guarantee: always review it before handing over a document.
- The PDF privacy check looks for recoverable redactions and comments in the first 50 pages; personal data and metadata are checked across the whole document. The actual coverage is stated in the report.
- The software is provided as is, free during launch. It does not replace the data controller's own assessment.
Informational document. It does not replace the data controller's own assessment or legal advice.