For IT teams
Task Planner security details
How the app handles network access, data storage, imported files and browser permissions, written so it can be forwarded to whoever reviews software for your organisation.
| Delivery | A single HTML file of about 2 MB, opened in a web browser. No installer, no server, no account. |
|---|---|
| Network | External requests are blocked by a Content Security Policy. No telemetry, analytics, update checks or licence checks. |
| Data | A plain-text JSON board file in a location the user chooses, plus a working copy in the browser’s own storage. |
| AI | No cloud AI is built in. An optional local AI feature, off by default, can only reach a model on the same computer. |
Network access
The first thing the file does is apply this Content Security Policy, so the browser itself refuses any connection the app did not declare:
default-src 'none'; script-src 'unsafe-inline' blob:; style-src 'unsafe-inline'; img-src data: blob:; font-src data:; manifest-src data:; connect-src 'none'; base-uri 'none'; form-action 'none'; frame-ancestors 'none'
If a user switches on the optional local AI feature, connect-src becomes http://localhost:* http://127.0.0.1:*, which still allows nothing beyond the same computer. A copy of the locked policy also applies if scripts are disabled.
- The only code that can make a request is two calls to the local AI address, used only when that feature is on.
- Links to AI assistant websites are ordinary links the user clicks. No board data is sent with them; the user copies a summary to the clipboard themselves.
- Email references open the user’s own mail program. Reminders use the browser’s local notifications only, with no push service.
Where data is stored
- Board file — a
.jsonfile saved where the user chooses: their computer, a network drive or a synced folder. - Browser storage — a working copy of the open board in
localStorage(kanban_v1), plus small display preferences. Settings → Privacy → Forget this board from this browser removes it. - File permissions — in Chrome and Edge, the permission to reopen the board file (and an optional backup file) is kept in IndexedDB (
offgrid_tp_backup). - Optional backup — if switched on, one rolling backup file in a folder the user chooses.
Board files are not encrypted. Anyone who can read the file can read its contents, so store it with the same controls you would use for any work document.
Imported files
- Board files and handover files are validated before they open. A file with unexpected values in its identifiers, colours or images is refused, and the board already open is left unchanged.
- Text from files is escaped wherever it is displayed.
- Spreadsheet (CSV) exports are protected against formula injection.
- Excel import uses SheetJS 0.20.3 and JSZip 3.10.1, embedded in the file and loaded only when an import is started.
Browser requirements
- Chrome or Edge (recommended) save directly to the board file using the browser’s File System Access feature. The browser asks the user once for permission.
- Other browsers save by downloading the board file.
- The browser must be allowed to open local HTML files. Managed browser policies can restrict local files or file system access, so check these before deployment.
Before you deploy
- Confirm your browser policy allows local HTML files and, for Chrome or Edge, file system access prompts.
- Decide where board files will be kept and who can read them.
- Decide whether the optional local AI feature is permitted.
- Agree how board files are backed up.
- Collaboration is by handing tickets over as files. Two people should not edit the same board file at the same time; the app warns before saving over a file that changed elsewhere.
Check it yourself
The file is readable and is not obfuscated. Open it in a text editor and search for Content-Security-Policy to see the policy, and for fetch( to see every place a request could be made.