Section 1: End-User Summary
Where is my data stored?
When you use offline.wims.org.uk, all of your records, forms, and data live exclusively inside your device's web browser using a localized storage technology called IndexedDB.
Think of it like a local desktop software application (such as Microsoft Word or Notepad):
- Your device is your vault: Data is written directly to your phone, tablet, or computer's internal storage.
- No automatic cloud uploading: Simply entering data into the app does not send it across the internet or upload it to any remote servers.
- Full offline capability: Once installed as a Progressive Web App (PWA), the app runs 100% offline. You do not need an active internet connection to create, edit, or view your records.
How does my data leave my device?
Your data remains entirely isolated on your local hardware unless you explicitly initiate an action:
- Manual Data Export: If you choose to export your data (e.g., as a backup file or spreadsheet), the file is generated locally on your device and saved directly to your local downloads folder.
- Cloud Synchronization: If you choose to use the online sync feature with
wims.org.uk, the app will establish a secure, encrypted connection (HTTPS/TLS) to transmit your local data to the central WIMS server. This only occurs when you are online and actively trigger or authorize a sync. For this to work, you would need to set up an account at https://wims.org.uk and create an API Key in your UserInfo settings.
Section 2: Technical & Security Specification
For IT, System Administrators, and Security Professionals.
This section details the client-side architecture, data isolation boundaries, network behavior, and security model of the offline.wims.org.uk Progressive Web App (PWA).
1. Architectural Overview & Storage Engine
- Storage Technology: The application utilizes IndexedDB, a transactional, object-oriented database system embedded natively within the user's web browser user agent.
- Service Workers & Caching: Application assets (HTML, JavaScript, CSS, icons) are cached locally using the Cache Storage API via a registered Service Worker. Once the initial application shell is fetched and registered, subsequent application boots execute entirely from the local cache, enabling zero-network dependency.
2. Data Boundary & Origin Isolation
- Same-Origin Policy (SOP): All stored data is strictly bound to the origin (
https://offline.wims.org.uk). Standard browser sandboxing prevents any third-party websites, external scripts, or cross-origin requests from accessing the IndexedDB instances associated with this origin. - Local Persistence: Data resides in the browser profile directory on the client device's physical storage (e.g., encrypted local disk if BitLocker, FileVault, or mobile device hardware encryption is active). Data persistence is subject to standard browser quota management policies, but standard PWA lifecycle practices request persistent storage permission to prevent accidental browser cleanup.
3. Network Behavior & Sync Protocol
- Default Network State (Zero Egress): Standard read/write operations against IndexedDB occur locally via client-side JavaScript execution. In default operation (and completely while offline), zero network traffic (HTTP GET/POST) is generated.
-
Explicit Synchronization (
wims.org.uk):- Transport Security: All sync operations utilize Transport Layer Security (TLS 1.2/1.3) via HTTPS REST APIs connecting to
wims.org.uk. - User-Initiated Trigger: Data egress occurs strictly upon API Key authentication and explicit user invocation.
- Authentication & Authorisation: Sync sessions require standard secure token authentication (REST API Key over HTTPS) to authorize data transmission to the target server instance.
- Transport Security: All sync operations utilize Transport Layer Security (TLS 1.2/1.3) via HTTPS REST APIs connecting to
4. Enterprise Compliance & Security Summary
| Feature | Implementation / Control |
|---|---|
| Data at Rest (Client) | Protected by host OS disk encryption (BitLocker, FileVault, iOS/Android hardware encryption) and browser origin isolation boundaries. |
| Data in Transit | Standard HTTPS/TLS 1.2+ encryption for all sync traffic to wims.org.uk. Zero unencrypted plain-text transport. |
| Data Sovereignty | Client data remains local to the physical endpoint hardware until explicitly synced or exported by the authenticated local user. |
| Third-Party Telemetry | No automatic third-party analytics or external database logging of user entries. |
| Export Control | File exports (CSV, JSON, etc.) are compiled entirely client-side using JavaScript Blob objects without server rendering or relay. |
5. Blocking All Outbound Connections to WIMS.org.uk
If an enterprise organization wishes to restrict all synchronization capabilities with wims.org.uk, this can be achieved via network rules without blocking access to the core application itself.
All sync options (fetching current projects or sending records to the central server) can be blocked by denying outbound network traffic to:
https://offline.wims.org.uk/api/
Specifically, the primary backend helper endpoint:
https://offline.wims.org.uk/api/wims.php
Client Application Behavior
If access to wims.php is blocked by an administrator or missing, attempting to invoke the Update Projects or Sync feature will safely fail client-side and return the notification:
"Couldn't get a valid response from wims.org.uk"
The rest of the offline application will continue to function normally for local data entry and storage.