The page is measured here, not uploaded elsewhere.

Page Echo registers a packaged content script on ordinary http:// and https:// webpages. Chrome uses that declaration to make the script available on matching pages. This is necessary because the extension must inspect the active page’s DOM when you ask it to scan that page.

The content script is designed to be dormant until it receives the specific page-echo-scan message from the Page Echo popup. Merely visiting a matching webpage does not cause the content script to create a scan, save a scan record, play audio, change the document, or send page information elsewhere.

When you press “Scan this page,” the popup asks the active tab’s Page Echo content script to inspect visible structural elements. The script checks elements selected from headings, paragraphs, list items, quotes, code and preformatted blocks, images and related visual containers, links, buttons, and common form controls.

The scan excludes elements considered invisible through common CSS and geometry checks. It also avoids double-counting a code element nested inside a pre block.

Page Echo does not modify the webpage during scanning. It does not inject advertisements, rewrite text, replace links, submit forms, click controls, change styles, or persist data inside the website’s own storage.

A Page Echo scan is a local structured record. It is not a screenshot, audio recording, DOM dump, or full copy of the webpage. The record contains measurements used to construct the document tape and sound mapping.

Page Echo considers at most 260 qualifying visible structural elements before thinning. When a page produces more than the studio should render efficiently, the extension thins the sequence to at most 180 items while prioritizing structurally distinctive families such as headings, images, code, quotes, and controls.

The short label can contain a limited excerpt derived from visible text, alternative text, an accessibility label, or the structural type when no label is available. Because that label is saved locally as part of the recent scan, users should regard Page Echo scan records as potentially containing small snippets from the scanned page.

Page Echo does not create a full text archive of the webpage. It does not save complete article bodies, full source HTML, CSS files, JavaScript source, cookies, website localStorage, IndexedDB content, browsing history, browser bookmarks, downloads, saved passwords, autofill records, or developer-tools data.

The extension does not intentionally read password values, credit-card fields, authentication tokens, private keys, clipboard contents, camera input, microphone input, or tab audio. It does not request microphone, camera, downloads, history, bookmarks, geolocation, or clipboard permissions.

Page Echo does not capture a screenshot of the scanned webpage. The visual document tape shown by the studio is generated from structural measurements, not from pixels copied from the site.

Page Echo does not create a user account and does not ask for your name, email, postal address, phone number, payment details, date of birth, or other registration data.

The extension does not run analytics, telemetry, advertising, behavioral profiling, cross-site tracking, or an AI classification service.

Page Echo stores recent scan records in chrome.storage.local. This browser-managed extension storage allows the newly opened studio tab to read the scan produced by the popup and allows a studio reload to continue displaying the same recent scan.

The popup prunes saved scan records so that Page Echo keeps at most five recent scans. Older Page Echo scan keys beyond that limit are removed automatically when a new scan is stored.

Page Echo also stores a small pageEchoLastScan value that identifies the most recent scan. The studio uses this identifier when opened without a specific scan ID.

The studio provides a visible “Clear Saved Scans” control. After confirmation, that control removes Page Echo scan records and the last-scan pointer from local extension storage, then returns the studio to its empty state.

Page Echo does not maintain a server backup of deleted scans. Because there is no Page Echo cloud account, the developer cannot remotely restore a scan that you delete from local storage.

Uninstalling the extension normally causes Chrome to remove its extension storage as part of browser extension management. If you want an explicit in-product deletion before uninstalling, use “Clear Saved Scans” first.

Page Echo generates sound locally through the browser’s Web Audio API. It creates oscillator tones for several structural families and short locally generated noise buffers for image and control accents.

The extension does not record from your microphone. It does not capture audio produced by the webpage. It does not send synthesized audio to a cloud audio engine or speech service.

Tempo, voice selection, remix state, muted structural families, play position, and individual audition actions are used by the current studio session to control sound. Version 1.0.0 does not transmit those interactions as analytics events.

The noise used for selected percussive accents is generated in memory through the Web Audio API. It is not downloaded from a sample library and is not saved as a recording of your device or environment.

Page Echo does not make application network requests. Its production code contains no Page Echo backend endpoint, analytics endpoint, AI endpoint, upload endpoint, advertising request, WebSocket connection, or remote synchronization request.

The extension does not use fetch, XMLHttpRequest, EventSource, WebSocket, or remote executable imports to send scan data away from the browser.

All JavaScript and CSS required for scanning and the studio is packaged with the extension. The privacy page likewise does not require remote scripts, fonts, or tracking resources.

The website you choose to scan was already loaded by your browser and can have its own network activity. Page Echo does not control or represent the privacy practices of that website.

The scan operation communicates between the Page Echo popup and the Page Echo content script using Chrome extension messaging inside the browser. That internal message is not an Internet upload.

storage

The declared storage permission is required to save recent local scans, the last-scan identifier, and to let the Page Echo studio retrieve a scan after the popup closes. It is also necessary for the built-in scan-deletion workflow.

Content script access on HTTP and HTTPS pages

The manifest declares a content script for http://*/* and https://*/* because Page Echo is designed to work on ordinary webpages across sites rather than on one fixed domain. This is website access, even though it is not listed as a named permission inside the manifest’s permissions array.

The script waits for the explicit scan message before building a record. Its purpose is limited to reading qualifying visible DOM structure and returning the local scan result to the extension popup.

The extension does not declare broad permissions such as tabs, history, bookmarks, downloads, cookies, webRequest, clipboardRead, geolocation, audioCapture, or videoCapture.

You decide when a scan is created by pressing the Page Echo action and then choosing “Scan this page.” The extension does not automatically build a saved scan for every page you visit.

You can mute or restore a structural family in the studio. This affects the local sequence and audio generation; it does not change the underlying webpage.

You can change tempo and synthesized voice, remix the mapping variation, play or pause the sequence, and audition a single tape mark. These are local interactions and do not require a service account.

You can delete the saved Page Echo scan records with “Clear Saved Scans.” You can also disable or uninstall the extension through Chrome’s extension management interface.

If you do not want Page Echo to have content-script access to a particular browsing context, you can manage extension site access through browser controls where supported, disable the extension, or avoid initiating a scan on that page.

Page Echo does not sell scan data, page labels, source URLs, document structure, or usage information. It does not rent or exchange that information for advertising value.

The extension does not include advertising and does not use scan data to build advertising segments or cross-site profiles.

Page Echo does not integrate a third-party analytics SDK or crash-reporting SDK. Version 1.0.0 does not send studio events to Google Analytics, Firebase Analytics, Segment, Mixpanel, Amplitude, Sentry, or a comparable provider.

Chrome provides the extension platform, content-script environment, Web Audio implementation, and local storage API. Your use of Chrome or Chromium is subject to the browser provider’s policies, which are separate from this Page Echo policy.

The webpages you scan are third-party sites unless you own them. Page Echo does not change the privacy terms of those sites and does not claim control over their independent data practices.

Page Echo minimizes remote exposure by not operating a cloud account or server for scans. Stored records stay in the browser profile rather than being transmitted to a Page Echo database.

The extension uses Manifest V3 and packaged JavaScript. Production files do not contain a manifest signing key, private key, remote loader, development harness, or remotely hosted executable code.

Chrome extension local storage is not an end-to-end encrypted vault created by Page Echo. A person or administrator with sufficient access to your operating-system account or browser profile may be able to inspect local browser data.

Because short scan labels can reflect visible page content, use the deletion control when you no longer want those local snippets retained. Avoid sharing browser profiles containing scans you consider sensitive.

Managed-browser administrators may apply extension or site-access policies outside Page Echo’s control. Those enterprise capabilities are part of the browser environment rather than a Page Echo data-sharing feature.

Page Echo is a general-purpose creative browser utility and is not specifically directed to children. It does not operate an age-gated account system and does not request a birth date.

The extension can be used on many kinds of webpages, including pages containing sensitive subjects. Page Echo does not attempt to infer sensitive traits from the scan and does not categorize the user based on the page.

If a shared or supervised browser profile is used, the person responsible for that profile should consider whether keeping recent local scans is appropriate and use the clear control when needed.

This document describes version 1.0.0. A future release might change structural families, storage limits, permissions, site-access scope, or other behavior. Material privacy changes should be reflected in an updated policy that describes the actual production code.

If a future version introduces an account, remote synchronization, analytics, AI processing, upload feature, or another network-dependent behavior, the relevant sections of this policy would need to change before that behavior could be accurately represented.

The effective date shown on this document identifies the current policy revision. Chrome may also inform users when an extension update requests materially broader browser permissions.

For a privacy question, bug report involving data handling, or request for clarification about Page Echo, use the developer support or contact method displayed on the official Chrome Web Store listing from which you obtained the extension.

You do not need to send the developer a saved scan to ask a privacy question. If a bug concerns a particular page, you can describe the page structure or provide a non-sensitive reproduction page instead of sharing private content.

Because the developer does not maintain a Page Echo account database, the developer cannot remotely locate or erase scan records stored in your local Chrome profile. Use “Clear Saved Scans,” Chrome’s extension-data controls, or uninstall the extension on the device where the records exist.