Your session, your rules.
A tool that accesses SAP systems with your sign-in has to explain itself to the security department. We built ODataTailor so that the explanation is short: no server, no call without a click, access per system, changes only behind a lock. Everything else is here – every statement with a source.
- Noserver
No telemetry, no analytics, nothing from third parties.1
- Onlyon click
No call you do not visibly trigger.2
- Accessper system
Requested one by one, revocable in the “Systems” dialog.3
- PRODlocked
Changing requests only after a check, fail-closed.4
- Nosecrets
No credentials, tokens or cookies stored.5
Every permission, and what for.
A single permission is fixed in the manifest. Everything else is optional and comes only when you need it.
| Permission | What for | When |
|---|---|---|
storage | Settings, systems with the “Production” switch, favourites and saved requests – locally in the browser; plus the IT’s prodHosts policy | always |
devtools_page | The “ODataTailor” DevTools panel for capture; reads calls via devtools.network (Firefox: implicitly devtools) | only with DevTools open |
https://*/*, http://*/* (optional) | Calling a system’s services from the workbench, with the browser’s sign-in | per system on click, revocable in the “Systems” dialog |
No content script, no access to tabs, cookies or history. Every further permission needs its own documented decision.3
What comes in, what goes out.
The workbench works in your browser. Only what you visibly trigger goes onto the network, and only to your system.
- Metadata and responses. From the service you open, from a file or from the capture – redacted as they are recorded6.
- Analysed and stored. Workspace and collections only locally7, without credentials, tokens and cookies; the CSRF token in memory only.
- Only to your system. GET from the workbench page, anything that changes data only through the background with a PROD check4. Fonts and themes ship with the extension, not from a CDN1.
- Only on your action. “Copy as Markdown”, exports,
.odtrace– without secrets, headers redacted.
Roll out, restrict, define PROD.
- Roll out.ODataTailor can be installed like any extension via the Chrome and Edge browser policies. There is no server to unblock.
- Define PROD.In the extension’s policy,
prodHostsnames the hosts on which it never sends anything that changes data – host names, wildcards such as*.prod.example.comor URLs. Users cannot switch this off. - Restrict.IT can limit the optional host access to certain hosts via the browser policies; files and capture work without it.
- Review.Data flow and permissions are above, the wording for data protection officers is in the privacy policy of the extension. Updates come only through the browser stores.
- Found a vulnerability?Please confidentially to office@clouddna.at. We reply personally.
Sources on this page
The superscript numbers in the text point here. Tap one to see the source right where it is used; all sources of this website are listed on one page.
- 1
No server, no telemetry, nothing from third parties ↑Product · ODataTailor product documentation, ADR-003 and end-to-end test “no request to third parties” · checked on 2026-11-21
- 2
No network call without a visible request ↑Product · ODataTailor product documentation, ADR-003 · checked on 2026-11-21
- 3
Permissions: storage, host access per system ↑Product · ODataTailor product documentation, manifest (wxt.config.ts), ADR-004 and ADR-009 · checked on 2026-11-21
- 4
PROD lock, fail-closed ↑Product · ODataTailor product documentation, ADR-007 and manifest (managed_schema) · checked on 2026-11-21
- 5
No credentials, tokens or cookies stored ↑Product · ODataTailor product documentation, CLAUDE.md, ADR-005, ADR-007 and ADR-008 · checked on 2026-11-21
- 6
Capture in the DevTools panel, redacted ↑Product · ODataTailor product documentation, ADR-009 · checked on 2026-11-21
- 7
Workspace only locally in the browser ↑Product · ODataTailor product documentation, ADR-005 · checked on 2026-11-21
Questions about security.
- Does CloudDNA see my data or requests?
- No. There is no CloudDNA server, no telemetry and no analytics tool. Requests go straight from your browser to your system; the workspace and collections live only in your browser.
- Why does the browser ask for access to a system?
- Because the workbench calls the service from its own page, with your browser’s sign-in. Access is optional and requested per system when you open a service there. The “Systems” dialog lists every grant and revokes it.
- Can ODataTailor write to PROD?
- Not on systems marked as production – in the “Systems” dialog or via the IT’s prodHosts policy. Changing requests and $batch are sent only by the extension’s background, which then blocks. If it cannot tell, it does not send.
- Can our IT roll out ODataTailor centrally and define PROD systems?
- Yes. The extension can be deployed like any other via the Chrome and Edge browser policies. In the extension’s policy, IT uses prodHosts to define the hosts on which it never sends anything that changes data; users cannot switch this off.
- How do I report a vulnerability?
- Please confidentially to office@clouddna.at, subject “Security ODataTailor”. We reply personally and credit you, if you wish, once the issue is fixed.
Your question isn’t here? Talk to me: +43 664 1964199 office@clouddna.at Get in touch