Privacy Policy for AEM Editorial Toolbar
Last Updated: July 2025
Overview
The AEM Editorial Toolbar is a Chrome extension for Adobe Experience Manager users. I don't want your data, I don't collect your data, and I don't care about your data. Everything happens locally in your browser.
Simple Truth: I Collect NOTHING
Zero data collection. Zero tracking. Zero transmission.
- No personal information - I don't know who you are
- No browsing history - I don't track where you go
- No analytics - I don't measure what you do
- No external servers - I don't send anything anywhere
- No user accounts - I don't store profiles or login data
- No cookies - I don't set tracking cookies
- No fingerprinting - I don't identify your device
What Actually Happens (All Local)
The Extension Reads (Locally Only)
- Current page URL: To detect if you're on an AEM site (processed locally, never sent anywhere)
- Page elements: To identify AEM editing contexts (processed locally, never sent anywhere)
- Your configuration: YAML files you create to tell the extension about your AEM setup
The Extension Stores (In Your Browser Only)
- Your preferences: Toolbar position, colors, enabled/disabled state
- Your configuration files: The YAML files you create for your AEM environments
- Nothing else: Seriously, that's it
Permissions Explanation
Why We Need Broad Website Access
The extension requires access to all websites (*://*/*
) because:
- Dynamic AEM Detection: AEM instances can be hosted on any domain, and the extension uses your configuration files to determine which sites are AEM environments
- Multi-Environment Support: Organisations typically have AEM instances across multiple domains (production, staging, development, local)
- User-Controlled Activation: The extension only activates functionality on domains you specify in your configuration files
Specific Permissions Used
- Storage: To save your preferences and configuration locally
- Tabs: To open new tabs for AEM editing links
- Host Permissions: To detect AEM contexts and inject the toolbar on configured domains
Why I Don't Want Your Data
- I'm not a data company: I build tools, not data profiles
- Privacy by design: The extension works entirely offline - no internet required except for optional config fetching
- No business model around data: I don't sell data, analyze data, or monetize data
- Simpler is better: No servers to maintain, no databases to secure, no privacy laws to navigate
The Only Network Activity (Optional)
IF you choose to load configuration files from external URLs (completely optional):
- Simple file download: The extension downloads your YAML config files via HTTPS
- No data sent: These are simple GET requests - no personal data is transmitted
- You control the URLs: You specify exactly which URLs to fetch from
- Cached locally: Downloaded files are stored in your browser to minimize requests
- You can disable this: Use local files only if you prefer
Your Control
You have complete control over:
- Configuration: What domains and settings the extension uses
- Activation: The extension only works on sites you configure
- Data: All stored data can be cleared through Chrome's extension settings
- Permissions: You can disable the extension or revoke permissions at any time
Changes to This Policy
I may update this privacy policy occasionally. Any changes will be reflected in the "Last Updated" date above. Continued use of the extension after changes constitutes acceptance of the updated policy.
Contact
If you have questions about this privacy policy or the extension's data practices, please contact me through the Chrome Web Store support channels.
Data Handling Summary
For Chrome Web Store compliance:
- Personal Data Collected: None
- Personal Data Shared: None
- Personal Data Sold: None
- Data Used for Advertising: None
- Data Used for Analytics: None
Compliance
This extension is designed to comply with:
- Chrome Web Store Developer Program Policies
- General Data Protection Regulation (GDPR) principles
- California Consumer Privacy Act (CCPA) requirements
Bottom Line
This extension is a local tool that helps you work with AEM more efficiently. I built it to solve a workflow problem, not to collect data. Your privacy is protected because I literally don't have access to anything about you.
Questions? If you're still concerned about privacy, you can:
- Review the source code (it's a standard Chrome extension)
- Monitor network activity (you'll see only the config file requests you configure)
- Use airplane mode (the extension works fine offline)