Last updated: 15 August 2026
SOP Maker is a browser-based tool for building, controlling and printing Standard Operating Procedures. This policy explains how it handles information.
SOP Maker is a browser-based tool. Everything you enter — SOP text, document-control details, images — is processed and stored locally in your browser, and, when you connect a data folder, written to that folder on your own computer or shared drive. We do not collect, transmit, or store your SOP data on any server. The tool makes no AI calls and no external network requests with your content.
One thing worth stating plainly, because it involves a person's name: when you save an SOP, SOP Maker writes a history entry into a 07_Log folder inside your data folder. That entry records the date and time, the name and role you signed in with, the action and the save's own revision counter, and the SOP's id, number, version, revision number, status and title, together with the version of SOP Maker that wrote it. That is the whole record. The title is the only part of the document itself that is recorded — no procedure text and no images. It is written so that an auditor can be shown who changed a controlled procedure and when. It stays in your folder like everything else — it is not transmitted anywhere — but if your data folder is a shared drive, the people who can read that folder can read those names. Nothing prunes the history: entries are added and never removed, so it is kept for as long as you keep the folder and clearing out old entries is yours to do.
The name you sign in with is also recorded as each SOP's author, so it appears on the printed document and travels with any procedure you export and send on. If you would rather not record individuals, the sign-in name is free text and can be a role — "Line 3 supervisor" — instead of a person.
SOP Maker uses your browser's local storage to remember your settings and signed-in name, and your browser's IndexedDB to remember your connected folder handle and an unsaved-draft safety copy between sessions — entirely on your own device. No tracking cookies are used. No third-party analytics are installed.
The page may be hosted on Netlify. Netlify may collect standard server logs (IP address, browser type, pages visited) as part of its hosting service. See Netlify's Privacy Policy for details. The tool can also be run directly from a file or local server with no hosting provider at all.
SOP Maker bundles all of its code locally. The library it uses for ZIP export (JSZip) is included in the page itself — it is not loaded from any third-party CDN, so no requests are made to external library providers.
Since we do not collect or store personal data, there is nothing to request access to, correct, or delete. Your SOP data lives in your browser and, if you connect one, in your own data folder — you can clear the browser copy at any time by clearing the site's browser data (IndexedDB), and the folder copy is yours to keep or delete.
For questions about this tool or policy, contact the site owner via Rimek.uk (https://rimek.uk).
A technical companion to this policy, written for IT and information security staff, is at SOP Maker for IT: the permission the browser is asked for, every network request the tool makes, the response headers it is served with, and how to check each of those yourself.
About SOP Maker · Open the app · Manual · Example SOP · For IT departments