Permissions and privacy
ODataTailor has no server. There is no account, no analytics, no telemetry and no code loaded at run time. The extension only calls the services you visibly open or query – with your browser’s sign-in.
- Server
- none
- Fixed in the manifest
- storage, DevTools panel
- Host access
- optional, per system on click
- Never stored
- passwords, tokens, cookies
Permissions
| Permission | What for | When |
|---|---|---|
storage | Settings, systems with the “Production” switch, favourites, saved requests; plus IT’s policy | always |
devtools_page | The “ODataTailor” DevTools panel for capture (Firefox: devtools) | only with DevTools open |
https://*/*, http://*/* – optional | Call a system’s services with the browser’s sign-in | per system on click, revocable |
No content script, no access to tabs, history or cookies. The workbench asks for host access for exactly the system on which you open a service – not for every website at once. In the Systems dialog you see and revoke it; see Opening a service.
What goes over the network
- Requests to the services you open, query, change, compare or measure – to the system, not to CloudDNA.
- Nothing else: fonts, themes and language data ship with the extension. An automated test checks on every build that the workbench makes no request without a user action.
What is stored – and what never is
Stored locally in the browser: the open services with their $metadata, the systems with access and their “Production” switch, favourites from the system catalogue, saved requests with variables and checks, settings.
Never stored: passwords, tokens, session cookies and the CSRF token. Before anything goes into storage or an export, the workbench removes secret headers such as Authorization and Cookie, secrets in URLs and secret lines in the body.
Capture
The capture in the DevTools panel stays in memory, at most 500 requests, bodies shortened. Headers, URL parameters and bodies are redacted while recording, and cookies are dropped. It goes into a file only when you choose Save capture as file – and even then without secrets. More in Capture.
Policy for production systems
IT can lock production systems for all users. For this, the extension reads the key prodHosts from its managed policy: a list of host names, wildcards such as *.prod.example.com or URLs. ODataTailor never sends anything changing to these hosts; the “Systems” dialog then shows “Production (company policy)”, and the switch cannot be turned off.
In Chrome and Edge the list goes under the 3rdparty policy for the extension’s ID; in Firefox into policies.json under 3rdparty – Extensions – odatatailor@clouddna.at. The content is the same in every browser:
"prodHosts": ["erp.example.com", "*.prod.example.com"]
The wording for data protection officers is in the extension’s privacy policy; rollout is described under Security.
See also
- Security Security and permissions
- Docs Opening a service
- Docs Changing, draft and $batch
- Docs Capture
- Sources No server1 · Permissions2 · No secrets3 · PROD lock4