Security and Privacy
Architecture in one paragraph
Gitoqlok is a browser extension. Everything runs in your browser, inside the Qlik tab and the extension's own popup or side panel. There is no Gitoqlok server in the data path. The only external call the extension makes on its own is the license validation to Motio's licensing service, and anonymous Google Analytics click statistics if you leave them enabled.
Data flows
| Flow | Transport | Authentication |
|---|---|---|
| Qlik Engine (app contents) | WebSocket from the Qlik tab, same origin | Your existing Qlik session; the extension has exactly the rights of the logged-in user |
| Qlik REST APIs (QRS on Enterprise, REST on Qlik Cloud): apps, spaces, tasks, data connections, users, themes, glossaries | HTTPS from the Qlik tab | Your Qlik session, with the CSRF token handling Qlik requires |
| Git provider | HTTPS REST API of the provider, from the background worker | The token from your Git server profile |
| AI provider | HTTPS from the background worker to the provider you configured | Your API key (or the key enforced by policy) |
| QSDA Pro | HTTPS to the server you configured | The QSDA Pro API token |
No Qlik data or Git data is sent to Motio. The optional Google Analytics events contain button-click counters only and can be turned off on the Options page → Git Servers → Feedback.
Storage
- Settings, profiles and tokens live in the extension's local storage (
chrome.storage.local), which is local to the machine and not synced. - Sensitive values (Git tokens, AI keys, QSDA tokens) are encrypted with AES; the key is derived from a random salt generated per installation.
- The repository cache (lists of repositories, branches and commits) is stored locally to reduce API calls and is refreshed automatically.
- Logs are kept in the browser storage of the tab and discarded when the tab closes; Download Logs writes them to a zip with passwords and tokens masked.
What Qlik Helper injects
The Helper injects stylesheets and HTML into the page rendered in your browser and reads the page's Engine session. It cannot change server settings; every write (a thumbnail, a merged chart, an applied commit) is a regular Engine API call made with your user's permissions.
Git tokens
Tokens are used only against the API URL of the profile they belong to. Use the minimal scopes listed on the provider pages under Git Servers, give tokens an expiry and revoke them on the provider when a developer leaves.
Access control and audit
Because Gitoqlok acts as the logged-in user, Qlik's own security rules and space permissions apply unchanged. The Git history provides the audit trail: who committed what and when, per file.
Enterprise controls
AI usage can be disabled or pinned to a corporate provider and key through a managed policy. The extension itself can be force-installed or blocked with the standard Chrome and Edge extension policies.
