AEM Agent – Privacy Policy

Effective Date: April 14, 2026

1. Overview

AEM Agent is a Chrome browser extension designed to assist Adobe Experience Manager (AEM) developers and architects. This policy describes what data the extension accesses, how it is used, and what is never collected.

2. Data We Access

• Active tab URL and DOM — Read only when you are on an AEM author instance (localhost:4502 or localhost:4503). Used to extract page context (path, template, workflow status) and run on-page audits.
• AEM credentials — Username and password you enter in the Settings panel. Stored exclusively in chrome.storage.local on your own device. Never transmitted to any third party or remote server.
• AEM server responses — API responses from your local AEM instance (JCR data, logs, MSM status). Processed in-browser only; never sent externally.

3. Data We Do NOT Collect

• No analytics, telemetry, or usage tracking of any kind.
• No data is sent to any remote server operated by the extension authors.
• No personal information is stored beyond your local browser storage.
• No browsing history outside of AEM author URLs is accessed.

4. Permissions Explained

• activeTab — Required to read the current AEM page context when you click the extension.
• sidePanel — Required to open the agent side panel in Chrome.
• storage — Required to persist your AEM credentials and settings locally on your device.
• scripting — Required to inject the bridge script into AEM pages to read page context from the MAIN world.

5. Third-Party Services

AEM Agent communicates only with:

• Your local AEM author instance (localhost:4502 / localhost:4503) — under your direct control.
• CXForge running locally on localhost:10004 — under your direct control.
• The browser-native Gemini Nano AI model (window.ai) — runs entirely on-device; no data leaves your browser.

No data is sent to Adobe, Google, or any other third party by this extension.

6. Data Retention

All data (credentials, settings) is stored in chrome.storage.local and remains on your device. You can clear it at any time via Chrome's extension storage settings or by uninstalling the extension.

7. Contact

For questions about this privacy policy, please open an issue on the project's GitHub repository.