Modulo — IT Security & Data Privacy Overview

For a PDF copy of the below please Click Here

Summary

Does document content leave the machine? No, never

Does Modulo collect telemetry or analytics? No

What data is transmitted externally? Hardware hash + computer name + license key only, over HTTPS

Does it require admin privileges? No

Can it run fully offline? Yes, for extended period between license checks

Where is data stored locally? App Data (user-scoped) and optionally a network folder you control

Overview

What is Modulo?
‍Modulo is a desktop application for Windows that helps teams generate customised documents from master templates using Microsoft Word. It runs entirely on the local machine, no cloud processing, no document uploads, no browser-based editor.
‍
‍Data That Leaves the Machine
‍Modulo makes outbound HTTPS requests to our licensing server for license activation and periodic validationonly. The data transmitted is limited to:
‍
- A one-way SHA256 hash of hardware identifiers (CPU ID, motherboard serial, system UUID, and Windows installation ID), used to bind the license to the machine. This hash cannot be reversed to identify the hardware.
‍
- The computer name (e.g. "ENGINEER-PC"), used for device identification in license management.
‍
- The license key entered during activation.
‍
- A timestamp of the last successful validation check.

That is the complete list. No other data is transmitted externally.
‍
‍Data That Never Leaves the Machine
- Document content, all processing happens locally using the OpenXML SDK and Microsoft Word's COM interface. No document content is transmitted externally
‍
- Document filenames and file paths
‍
- Document structure or headings
‍
- User selections or preset configurations
‍
- Usage statistics
‍
- Any personally identifiable information beyond the hardware hash described above

‍Local Storage
‍Modulo stores the following onthe local machine:
‍
- An encrypted license file in %LocalAppData%\Modulo\ and a backup in the user-level Windows Registry (HKCU\Software\Modulo\License), contains license key, expiry date, and machine hash only
‍
- Document structure caches in %LocalAppData%\Modulo\Cache\ stores heading structures, preset configurations, and a local working copy of the master document to enable offline use and improve performance. All cached data remains on the local machine and is never transmitted externally.

- User preferences (preset mode, display settings) in %AppData%\Modulo\settings.json

All local data is scoped to thecurrent Windows user account.
‍
‍Shared/Network Storage (Optional)
‍In team configurations, Modulo can optionally read and write preset files to a shared network folder chosen by the organisation. This is entirely within your own network infrastructure; presets are never routed through Modulo's servers. The organisation retains full control over this folder's location and access permissions.
‍
‍System Access
‍Microsoft Word COM Interop — required for document processing (reading headings, generating output documents)

‍WMI queries — reads CPU ID, motherboard serial number, and system UUID for license binding. Also reads the computer name for device identification.
‍
‍Windows Registry (HKCU and HKLM read-only) — user-level storage for license data; reads a Windows installation identifier from HKLM for license binding (no write access to HKLM required)
‍
‍Temp folder — temporary working copies are created during document generation and cleaned up afterward Modulo does not require administrator privileges to install or run.
‍
‍Network Requirements
‍Modulo connects to a single external endpoint for license validation over HTTPS (port 443). The application can operate offline for an extended period between validation checks. No other external connections are made.If your environment restricts outbound connections, only the licensing endpoint needs to be whitelisted. Contact us for the specific domain.