Your documentation never leaves your perimeter.
Most documentation tools answer the residency question with a region selector and a list of subprocessors. DocuCommit answers it with architecture: the content is Markdown in a Git repository you own, served by a container you run. There is no vendor cloud holding your pages, because there is no vendor cloud in the path at all.
Every data flow, listed.
| Data | Where it lives | Leaves your network? |
|---|---|---|
| Documentation content Markdown pages, diagrams, attachments | Your Git repository and your server | No |
| Revision history Every commit, author, and message | Your Git repository | No |
| Comments and @mentions Sidecar JSON files | Your server's working directory — outside the Git repo, so back up the volume too | No |
| Accounts, follows, and notification state Reader accounts, subscriptions, outbox | Your server's working directory — outside the Git repo | No |
| Search index Full-text index and tags | Rebuilt from your files, on your server | No |
| Reader traffic Requests from people reading the published docs | Your server, inside your network — note the server has no built-in read restriction; anyone who can reach it can read it | No |
| Licence validation Licence key and a periodic check that the licence is still valid | Our licensing backend | Yes — licence metadata only, never document content |
| Update check One request for the latest version number at editor startup | docucommit.se | Yes — a version query, no content; can be switched off |
| Billing Payment and invoicing details | Stripe, as payment processor | Yes — handled by Stripe, not stored in the product |
| Product telemetry Usage tracking, analytics, crash reporting | Nowhere — the product collects none | No |
The three rows that leave are the honest ones. A licence check confirms a key is valid; it does not read, transmit, or index your documents. The update check asks for a version number and can be turned off. Payment details are handled by Stripe as processor and are never held inside the product. The complete call-by-call inventory, with the exact payloads, is in What actually leaves your network and the security model documentation. See the privacy notice for the formal detail.
Residency as a property, not a promise.
-
No region to choose, because there is no vendor region
Your documentation is wherever you put the repository and the server. If that is a machine in your own data centre, that is where the data resides — no configuration, no trust required.
-
No subprocessor chain for content
Content never reaches a third party, so there is no chain of processors to enumerate, audit, or re-approve when a vendor changes their infrastructure.
-
Nothing to delete on our side
A deletion request touches your systems, because we never held the material. The same is true of retention: you set it, because the files are yours.
-
An independent Swedish vendor
DocuCommit is an independent software vendor based in Sweden. There is no parent group, no acquisition roadmap, and no incentive to move your data somewhere more convenient for us.
Short answers to the usual questions.
- Where is our data stored?
- Wherever you host the Git repository and the server. We do not host it and cannot access it.
- Which subprocessors handle our content?
- None. Content does not leave your infrastructure.
- Does the product phone home?
- A periodic licence check confirms the key is still valid. It carries no document content and there is no usage telemetry or crash reporting.
- Can it run without internet access?
- Editing and publishing are local. The licence check requires periodic connectivity; fully air-gapped deployment is not supported today.
- What happens to our documentation if we stop paying?
- You keep it. It was never in our custody — it is Markdown in your repository, readable with any text editor.
- How do we get an export?
- There is nothing to export. Clone the repository, or use the built-in Markdown, HTML, and PDF export if a formatted copy is wanted.
This page describes how the software is built. It is not legal advice, and it is not a substitute for a data processing agreement — if you need one for the licensing relationship, get in touch at kontakt@docucommit.se.
Documentation inside your own perimeter.
Start a 14-day trial, no card required. Your pages stay in your repository, on your infrastructure, from the first commit.