← Back to cpicopilot.com
Privacy Policy

CPI Copilot Tools (browser extension)

Last updated 4 August 2026 · Covers the browser extension only. The CPI Copilot web app at cpicopilot.com has its own account and credential-handling practices, described in-product during setup.

CPI Copilot Tools is a browser extension that adds Explain, Steps, Trace, and Compare to the SAP Integration Suite web IDE. This page states plainly what it reads, what it sends, and what it never does — no legal filler.

What the extension reads, and why

DataWhyWhere it goes
Your CPI Copilot login token To authenticate requests to your own CPI Copilot account Stored only in the browser's local extension storage (chrome.storage.local) on your machine. Never sent anywhere except cpicopilot.com.
The iFlow ID of the flow you have open Read from the page URL, to know which flow to explain, map, trace, or compare Sent to the CPI Copilot backend over HTTPS only when a feature needs your account-backed tenant connection
iFlow content (BPMN, Groovy, config) Downloaded from your SAP tenant using your CPI Copilot account's stored tenant credentials, to build Explain, Steps, or a connected Compare snapshot Processed on the CPI Copilot backend and returned to the panel — see "What we never store" below
The iFlow model SAP loads into the page, and the script, mapping and schema files it references (Groovy, XSLT, XSD) To build Steps, Compare and Trace analysis without needing a CPI Copilot account. These are requested from your own SAP tenant, in your browser, using the SAP session you are already signed in with — the same access you have when clicking around the web IDE yourself. Kept in the SAP page's memory only. Never uploaded to CPI Copilot, never sent to an AI provider, and lost when the tab is closed or refreshed.
Browser-local iFlow canvas and Compare baseline To compare the current open iFlow against the earlier state you captured in the same SAP browser tab Kept in extension page memory only. It is not uploaded and is lost when the SAP tab is closed or refreshed.
Open SAP trace popup content (Headers / Properties / Body) To find where a value became null or malformed Depends on the mode — see the two Trace modes below

Trace has two modes, with different data handling

Analyze Open Trace — browser-local

Reads whatever SAP trace popup you already have open, redacts sensitive-looking values, and analyzes it entirely inside your browser. Nothing is uploaded, no AI call is made, nothing is stored anywhere — it disappears when you close the tab.

Backend Latest — server-side, on request

Calls SAP's own official API for the most recent run's trace data, using your account's stored tenant credentials. The result is returned to your browser for that one request; it is not saved in the CPI Copilot database.

What we never store

Chrome/Edge permissions, explained

AI processing

Explain uses an AI model to generate plain-English text. Browser-local Trace and Compare do not call AI. If an account-backed feature uses the default CPI Copilot AI engine, requests are processed via our configured provider (currently Azure OpenAI) under a standard business data-processing agreement. If your account is configured with your own AI key (BYOK), requests go directly to your own provider instead, so analysis stays inside your own AI account.

Your controls

Click Sign out in the extension popup at any time to remove the stored login token from your browser immediately. To request deletion of your CPI Copilot account and associated data, contact us at the email below — the same process as the main web app.

Changes to this policy

If what the extension reads or where it sends data changes in a future version, this page will be updated and the "Last updated" date above will change accordingly.