SmartappS Website Auditor : Full Privacy & Compliance Policy

  • Last Updated: September 9, 2026

SmartappS ("we," "our," or "the extension") is a developer and SEO tool designed to audit websites directly within your browser. To comply with the Google Chrome Web Store Developer Program Policies, this document outlines our single purpose, data usage, permission justifications, and complete privacy practices.

Privacy Policy Summary: This policy contains all necessary information regarding our practices for user data collection, handling, storage, and sharing.

Single Purpose

The single purpose of SmartappS is to provide an in-browser auditing tool for developers, QA engineers, and SEO professionals to instantly analyze on-page SEO, heading structures, links, accessibility, and validate data layer analytics events on the active webpage.

Data Types We Access (Chrome Web Store Categories)

In line with Chrome Web Store's data disclosure requirements, we address each recognized data category below:

  • Website content: Yes. We read DOM elements, meta tags, headings, and links on the page you actively audit, to generate audit reports.

  • Web history: Yes. We access the URL of your active tab to run link validation, canonical checks, and analytics detection.

  • User activity: Yes. When you use the Sanity Test Recording feature, we capture your clicks, inputs, and scroll events locally to replay test cases. This is only active when you explicitly enable the feature.

  • Authentication information: Yes. If you use the Google PageSpeed Insights feature, your API key is stored locally using Chrome's Storage API and sent directly to Google's API from your browser. We do not store or transmit it to our own servers.

  • Personally identifiable information (name, address, email, etc.): No, we do not collect this.

  • Financial and payment information: No, we do not collect this.

  • Health information: No, we do not collect this.

  • Location: No, we do not collect this.

  • Personal communications (emails, texts, chat messages): No, we do not collect this.

All data listed above as "Yes" is processed locally in your browser and is never transmitted to SmartappS servers, except where explicitly noted (e.g., your own PageSpeed API key going directly to Google).

1. User Data Collection

SmartappS is a local-first browser extension. We do not transmit, sell, or harvest this data to any external servers. We access certain data locally on your device to power the extension's features. The complete list of data accessed — including data accessed automatically in the background — is disclosed below:

Automatic Background Activity (runs on every page you visit): Two content scripts run automatically on every page to support core extension features:

  • dataLayer Observer (dlHook.js): Silently observes whether a window.dataLayer object exists on the current page. It does not read, transmit, or store any dataLayer values — it only notifies the extension that a dataLayer push event occurred, enabling real-time analytics capture when you activate that feature.

  • Sidebar & AI Audit Script (content.js): Manages the optional floating sidebar. When the AI Audit feature is used, it reads a pre-generated audit prompt from Chrome session storage and writes it to the clipboard on AI chat platforms (ChatGPT, Gemini, Claude) only. No personal browsing data is read or stored.

Data Accessed Only When You Trigger an Audit:

  • Website Content: We read the DOM (HTML, meta tags, images, links) of the page you actively audit.

  • Web History / URLs: We access the URL of the active tab and observe outbound network request URLs via the webRequest API solely to detect and log analytics events (GA4, GTM, tracking pixels) firing on the audited page.

  • User Activity, Network Monitoring & Storage: We read cookies and local storage values on the audited page solely to verify your Google Tag Manager or GA4 data layer events against your custom rules. Network request URLs are observed locally and never stored beyond the active audit session.

  • Prompts, Conversations & Authentication Data: We do not collect, process, or store user prompts, conversations, or authentication data from third-party AI platforms. (Note: your own API keys, e.g. for Google PageSpeed, are stored locally as described above.)

  • Sanity Test Recording (User Inputs & Clicks): When you actively use the Sanity Recording feature, we locally record your interactions (clicks, inputs, and scroll events) solely for replaying the test case. This data never leaves your device.

Data Consent, Opt-Out, and Offline Mode

  • User Consent: Data is accessed only in connection with features you actively use. On installation and before first use of data-accessing features, you are shown an in-product disclosure describing our data practices. For any additional data access consistent with our single purpose, you will be informed and asked for consent before it begins.

  • Opt-Out Options: You have the ability to opt out of specific data collection features directly from within the extension's options page.

  • Offline Mode: The extension operates in "offline mode" by default. It only stores data locally on your device and never transmits personal data to remote servers.

2. User Data Handling

  • Local Processing Only: All data read from the active tab is processed entirely within your browser. The extension parses HTML and evaluates JavaScript rules locally.

  • No Remote Processing: We do not send your web page data, audit results, browsing history, or personal information to our servers.

  • Third-Party APIs: If you use the Google PageSpeed Insights feature, the extension makes a direct API request from your browser to Google's API, transmitting the URL and your API key. This is subject to Google's privacy policy.

3. User Data Storage

  • Local Storage (storage, unlimitedStorage): We store your custom settings, QA rules, data layer test cases, and audit logs locally on your device using the Chrome Extension Storage API.

  • Space Management: You have full control to view, monitor, and delete your stored data at any time via the built-in "Space Management" settings panel.

  • No Cloud Syncing: Your data is not synced to any cloud database by us. It remains strictly on your local device.

4. User Data Sharing

  • No Third-Party Sharing: We do not sell, trade, rent, or share any user data with third parties. We do not collect it on our servers, so we have nothing to share.

  • No Tracking: The extension does not embed third-party trackers or analytics tools to monitor your usage of the extension itself.

Data Usage Certifications

As developers of SmartappS, we certify that:

  • We do not sell or transfer user data to third parties, outside of the approved use cases.

  • We do not use or transfer user data for purposes that are unrelated to the item's single purpose.

  • We do not use or transfer user data to determine creditworthiness or for lending purposes.

Permission Justifications

To operate correctly, SmartappS requires the following browser permissions. Every permission is strictly used to fulfill the single purpose of the extension:

  • activeTab: Used to read the DOM content, meta tags, and headings of the currently active tab when the user clicks the extension icon to run an audit.

  • storage: Used to locally save user preferences, custom QA test rules, and API keys.

  • unlimitedStorage: Allows users to define and save an unlimited number of custom QA test cases and data layer event assertions, and temporarily store large audit logs during complex QA sessions, all handled locally.

  • tabs: Required to detect the active tab's URL for link validation, canonical checks, and to apply the visual highlight overlays over the active page.

  • scripting: Used to safely inject the audit scripts and visual highlight overlays into the active page upon user request.

  • cookies: Used to inspect cookie-based signals on the active page, which is essential for validating specific tracking and analytics audit rules configured by the user.

  • webRequest: Used to intercept and observe outbound network requests made by the audited page. This enables the extension to detect and log analytics events (such as GA4, GTM, and third-party tracking pixels) as they fire in real time, allowing users to validate their data layer implementations.

  • windows: Used to manage the browser window context when opening audit results in a dedicated panel and when performing multi-tab sanity test replays. No window content data is read or stored.

  • downloads: Used solely to export audit reports and sanity test results as downloadable files (e.g., JSON or CSV) to the user's local machine, triggered explicitly by the user.

  • Host Permissions (<all_urls>): Required because developers and QA engineers need to run audits across any domain they are working on, including localhost, staging, and production environments.

Remote Code

SmartappS does not use remote code. All JavaScript and logic required to perform the audits are bundled directly within the extension's package. No external scripts are evaluated or injected into the extension's background or popup contexts.

5. Data Retention & Deletion

  • Retention Period: All data stored by SmartappS (including custom QA rules, audit logs, sanity recordings, and user preferences) is retained on your local device indefinitely until you choose to delete it. We do not impose automatic expiry on locally stored data.

  • How to Delete Your Data: You can delete all locally stored extension data at any time through the built-in "Space Management" panel within the extension settings. You may also remove all data by uninstalling the extension from Chrome, which will clear all associated local storage.

  • Data from Audited Pages: Data read from web pages during an audit (DOM content, URLs, cookies) is used transiently during the audit session and is not persisted beyond the immediate session unless you explicitly save a report.

6. Changes to This Privacy Policy

  • Policy Updates: We may update this Privacy Policy from time to time to reflect changes in the extension's features, data practices, or applicable legal requirements.

  • How You Will Be Notified: When we make material changes to this policy, we will update the "Last Updated" date at the top of this page. We will also update the Privacy Policy URL in the Chrome Web Store listing and may include a notice in the extension's update release notes.

  • Continued Use: Your continued use of the extension after any changes to this Privacy Policy constitutes your acceptance of the updated terms. We encourage you to review this page periodically.

Contact Support

If you have any questions or concerns about this policy, please reach out to us.

Email Support