# SiteLens SB – MarTech Inspector Privacy Policy Last updated: August 29, 2026 Applies to: SiteLens SB – MarTech Inspector, version 1.0.0 ## Overview SiteLens SB – MarTech Inspector ("SiteLens SB") is a local browser-based inspection tool developed and maintained by Sergiu Bratis. Its single purpose is to provide local technical inspection and troubleshooting for the current website's MarTech implementation, including Adobe tags and requests, data layers, consent state, cookies, browser storage and observed third-party network vendors. SiteLens SB has no developer-operated backend, analytics service, advertising, account system or telemetry. The extension does not sell user data and does not transmit inspected data to the developer or to advertising, analytics or data-broker services. This policy explains what information the extension handles, why it is needed, where it is retained and what controls are available to the user. ## Data handled by the extension When SiteLens SB is used on a supported HTTP or HTTPS page, the extension may process the following information locally: - the active page URL and hostname, together with the hostnames and URLs of resources requested by the inspected tab; - request method, resource type, timing, initiator and response status; - for recognized Adobe Edge Network, Adobe Web SDK and Adobe Analytics request patterns, request payload data when Chrome makes it available; - cookies associated with the current site or with external domain families observed in that tab, including cookie names, values, domain, path, expiration, SameSite, Secure, HttpOnly and partition information when available; - Local Storage, Session Storage, Cache Storage, IndexedDB and Service Worker metadata for the inspected site; - website implementation objects such as `digitalData`, `dataLayer`, `adobeDataLayer` and the published `_satellite` container; - Adobe Launch runtime rule callbacks, including rule identity and condition metadata reported by the page when a condition fails; - consent-related cookies, storage keys and observable TrustArc or OneTrust page markers; - click, keyboard-activation and form-submit metadata used to associate an Adobe request with an interaction, but only while the user has explicitly enabled Adobe request recording; and - the user's selected interface theme and font-size preference. Depending on what the inspected website places in cookies, browser storage, data layers or Adobe payloads, locally processed values may contain identifiers, authentication state, transaction information or other website content. SiteLens SB does not require or intentionally request passwords, payment-card numbers, health information or personal communications. ## How data is collected and used SiteLens SB uses this information only to provide its visible inspection features. These features include rendering implementation views, correlating relevant requests and cookies, explaining observable rule activity, clearing site data selected by the user and creating a copy or export explicitly requested by the user. The packaged Adobe Launch monitor is injected at document start on supported pages. When Adobe Launch is present, it registers a local debugging monitor and keeps a bounded callback buffer in that page's memory so early lifecycle events can be inspected later. Before the user opens SiteLens SB for that tab, the buffer is not copied into extension storage or transmitted externally. The extension's other inspection activity begins when the user explicitly opens its Side Panel for a supported tab or starts a visible inspection or recording feature. The isolated content script remains dormant until the extension requests a page snapshot or Adobe request recording is enabled. General request observation records metadata without requesting request bodies. A separate, narrowly filtered listener requests body data only for recognized Adobe Edge Network, Adobe Web SDK and Adobe Analytics endpoint patterns. Live request monitoring is limited to the tab where the user opened SiteLens SB. Cookie queries are restricted to the current hostname and domain families actually observed in that tab. A packaged copy of the Public Suffix List is used locally to calculate those domain families and does not cause any network transmission. ## Local storage and retention - Interface theme and font-size preferences are stored in `chrome.storage.local` until the user changes them, clears the extension's stored data or removes the extension. - Adobe recorder logs and the inspected tab's live network-host summary are stored in `chrome.storage.session` within the user's Chrome profile. - Adobe recorder logs are limited to 500 request records. - The visible recorder list renders at most the newest 150 matching requests at once. Counts and user-triggered exports can continue to use the complete bounded log. - The live network summary is limited to the inspected tab and 350 hostnames. - The in-page Adobe Launch detail timeline is limited to 250 callbacks. Per-rule aggregate counts cover the current document lifecycle and disappear when that document navigates or reloads. - Before session storage approaches its available budget, SiteLens SB omits older captured request bodies first and then older request records when necessary. A visible warning informs the user when compaction occurs. - A tab's live network summary is removed when that tab closes. - Session data is not intended as permanent storage and is cleared when the Chrome session ends. Chrome or the user may clear it earlier. - The **Copy** control places the selected information on the user's clipboard only after an explicit user action. - A JSON download is created only when the user explicitly uses an **Export** control. The user controls where exported files are stored and when they are deleted. ## Sharing and transmission SiteLens SB does not send inspected data, browsing activity, cookies, page content or interaction data to the developer or to any analytics, advertising, data-broker or other third-party service. The inspected website continues to make its own normal network requests independently of SiteLens SB. When the user explicitly applies an Adobe Launch library override, Chrome redirects that page's existing Launch script request to the HTTPS URL supplied by the user. The replacement script executes as part of the inspected website, not as extension code. SiteLens SB does not upload the supplied URL or replacement script to the developer and does not use either to alter the extension's own behavior. The optional creator link opens LinkedIn only after the user clicks it. No inspected data is attached to that navigation. ## Third-party websites and services This policy applies only to SiteLens SB. It does not govern the privacy practices of: - websites inspected by the user; - Chrome or the Chrome Web Store; - LinkedIn; or - any Adobe Launch library URL supplied by the user for an override test. Those websites and services operate under their own terms and privacy policies. ## Data deletion and user control Users can: - stop or clear the Adobe request recorder at any time; - close the inspected tab, open SiteLens SB in another tab or remove the extension to release its tab-scoped network summary; - use the **Clear current website** controls in Overview to remove only the selected cookies or site-storage categories; - remove an active Adobe Launch override from the extension interface; - disable or remove the extension to stop its processing; - clear locally stored extension data through Chrome; and - delete exported files through the operating system's normal file controls. ## Permissions SiteLens SB requests browser permissions only for its disclosed, user-facing inspection functions: inspecting the active tab and page implementation, observing relevant requests, reading and removing relevant cookies, clearing site data selected by the user, storing local or session state, presenting the Side Panel and applying an explicit tab-scoped Adobe Launch test override. These permissions are not used for advertising, profiling, telemetry or developer-operated data collection. ## Limited Use SiteLens SB's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Information accessed by the extension is used only to provide or improve its disclosed, user-facing MarTech inspection functionality. SiteLens SB does not: - sell user data; - use inspected data for advertising, profiling, creditworthiness or lending decisions; - transfer inspected data to data brokers, advertising platforms or other third parties; - allow the developer or other individuals to read inspected user data; or - use browsing activity for purposes unrelated to the extension's disclosed functionality. ## Security All extension logic is packaged with the extension. SiteLens SB does not load remote code into the extension context, use `eval` or use a remote configuration service. The extension does not intentionally transmit inspected user data. Session information is retained within the user's local Chrome profile and is subject to the bounded limits described in this policy. Users should avoid copying or exporting sensitive inspected values unless necessary for their own authorized work, and should protect or delete any resulting clipboard content or files appropriately. ## Changes to this policy This policy will be updated when the extension's functionality or data-handling behavior changes. The date at the top identifies the current version of the policy. If a future extension update materially changes how user data is handled, the related Chrome Web Store disclosures and this policy will be updated accordingly. ## Contact For privacy, support or data-handling questions, contact [sitelens.sb@gmail.com](mailto:sitelens.sb@gmail.com). ## Independent product notice SiteLens SB is an independent inspection utility. It is not affiliated with, sponsored by or endorsed by Adobe, Google, TrustArc, OneTrust or any vendor detected on an inspected website. Product and company names are used only to identify compatible technologies or observed services.