Privacy Policy

Scope and Purpose of This Policy

This Privacy Policy applies to PageData version 1.0.4 for Chrome. It explains how the extension reads information from the webpage the user chooses to inspect, transforms that information into a local structured snapshot, presents it in the Side Panel, handles user-initiated copy and export actions, stores limited interface preferences, and uses its declared browser permissions.

PageData is designed as a focused webpage inspection and extraction utility. Its purpose is to make useful page information easier to review and reuse without requiring the user to manually inspect source code for common metadata, headings, links, media and document-level details.

The extension is not designed as a browsing-history service, cloud crawler, advertising platform, behavioral analytics product, credential collector, account system, or remote webpage archive.

This policy does not govern the privacy practices of Chrome, the Chrome Web Store, websites visited by the user, the user's operating system, or other browser extensions and applications.

How PageData Operates

PageData opens as a Chrome Side Panel. When inspection is available, the extension uses Chrome's scripting capability to run its packaged inspection function in the active webpage and return a structured result to the Side Panel.

The returned snapshot is rendered locally into six focused views: Overview, SEO, Content, Links, Media and Technical. Search, filtering, selection, formatting and most copy-related transformations operate on that in-memory snapshot inside the extension interface.

PageData may refresh the active-page snapshot when the relevant active tab or page changes while the Side Panel is in use. It does not need a developer-operated account, remote database or cloud API to inspect the page or format the result.

The extension includes safeguards for page transitions and browser-restricted surfaces so that expected navigation states or protected Chrome pages are handled without attempting to bypass browser restrictions.

Information Read From the Current Webpage

To provide its inspection features, PageData reads information available in the Document Object Model (DOM) and related browser-exposed page information for the active webpage being inspected.

Depending on what exists on the page, the snapshot can include page identity and document details such as the title, current URL, domain, path, origin, protocol, declared language, character set, viewport information, referrer, base URL, favicon, theme color, doctype and capture time.

PageData also derives page-level counts and summaries such as visible-text word count, character count, reading-time estimate, heading count, paragraph count, list count, table count, form count, input/control count, button count and DOM-node count.

Metadata, SEO Signals, and Structured Data

The SEO view reads common document metadata so the user can review it in one place. This can include the document title, meta description, canonical URL, robots directives, Googlebot directives, author, keywords and generator values when those fields are present.

PageData can inspect heading structure from H1 through H6, including heading text and identifiers, and can expose Open Graph properties, Twitter/X card metadata, hreflang links and JSON-LD blocks found in the page.

For JSON-LD, PageData reads the contents of <script type="application/ld+json"> elements so it can identify structured-data blocks and their declared types. The extension may report whether a block could be parsed as JSON, but it does not submit that structured data to an external validation service.

Lightweight status labels such as missing, found, short, long, multiple H1s or noindex are calculated locally from the inspected values for convenience. They are interface guidance, not a remote SEO audit.

Visible Text, Main Content, Tables, and Forms

PageData reads visible page text using the webpage DOM so it can provide content statistics and user-requested copy actions. It also identifies a main-content candidate from elements such as main, article, or [role="main"] when available.

The Content view can display visible text, main text, heading structure and high-level document counts. Table summaries may include row counts, column counts and captions.

For forms, PageData version 1.0.4 records structural information such as form action, method, identifier, name and the number of controls contained in the form. It also counts page inputs, selects and textareas at a page level.

Link Inspection and Filtering

The Links view reads anchor elements from the inspected webpage so users can review destinations without manually collecting them one by one.

For a link, PageData may process the visible anchor text, resolved destination URL, original href value, relationship attributes and interaction-related properties such as whether the link is internal, external or another link type, whether it declares nofollow, sponsored or ugc, whether it opens in a new tab, and whether it is marked for download.

The Side Panel can filter links by category and can optionally deduplicate the displayed list by URL. These filtering operations happen locally on the current snapshot.

Choosing Copy shown or Copy selected writes the requested link information to the clipboard only after a user action.

Images, Embedded Media, and File Links

The Media view inspects page elements and relevant links to summarize media and file resources referenced by the current document.

For images, PageData may process image URLs, filenames, declared and natural dimensions, loading information, whether an alt attribute exists, and the alt text when provided by the page. This allows the interface to distinguish images with alt text, empty alt attributes and missing alt attributes.

The extension can also list referenced video, audio and iframe sources, together with limited element details such as dimensions or iframe title when available. Downloadable file links may be identified from their URLs and file extensions.

Media URLs shown in the Side Panel remain references to resources used by the webpage. PageData does not upload those media resources to a developer-operated server.

Document, Resource, and Performance Information

The Technical view collects commonly useful document and resource information exposed by the page and browser. This can include document URL and origin, protocol, doctype, viewport declaration and size, referrer, base URL, favicon and theme color.

PageData can list referenced external JavaScript files and linked stylesheets, together with selected attributes such as script type, async or defer state and stylesheet media declarations. It can also inspect preload and prefetch resource hints declared by the page.

The extension reads meta tags present in the document and can summarize browser Performance API resource entries by resource type. When navigation timing is available, PageData may display navigation type, negotiated protocol, DOM-content-loaded timing, load-event timing and transfer/body-size values exposed by the browser.

These technical details are intended for quick inspection and context. PageData does not claim to replace Chrome DevTools, a network proxy, or a remote performance-monitoring service.

Search, Filters, and Selected Fields

PageData lets users search the current inspection result, switch between data views, filter link categories, deduplicate displayed links and select individual fields or rows for copying.

Search text entered into the PageData interface is used locally to match already-inspected data in the Side Panel. It is not sent to a developer-operated search service.

The set of currently selected fields exists as interface state for the current PageData session. Selection is used to determine what should be copied when the user chooses Copy selected.

Changing tabs, filters or selection state does not create a developer-maintained user profile or remote activity record.

Copy Actions and Clipboard Handling

PageData provides explicit copy controls for individual fields, sections, visible links, selected fields and page-level output. When the user activates one of these controls, the extension formats the requested data and writes the resulting text to the system clipboard using the browser clipboard interface.

Available output formats in version 1.0.4 include Key: Value, Plain text, Markdown, JSON and CSV. Formatting is performed locally inside the extension.

PageData does not continuously monitor clipboard contents and does not use copied output as a source of analytics or advertising data.

After copying, the extension may display a brief local confirmation such as Copied or a selected-item count. That notification does not represent a network transmission.

User-Initiated JSON Export

PageData can export the current inspected snapshot as a JSON file when the user explicitly chooses the Export action.

In version 1.0.4, the export is created locally in the browser from the in-memory PageData snapshot using a browser Blob and object URL. The resulting file is offered through the normal browser download mechanism.

The export action does not upload the snapshot to a PageData server. Once a user saves or shares an exported file outside the extension, handling of that file is controlled by the user, the operating system and any destination application or service chosen by the user.

Locally Stored Interface Preferences

PageData uses chrome.storage.local for a small set of interface preferences so the Side Panel can restore the user's chosen experience between sessions.

Version 1.0.4 stores:

• the selected PageData theme preference; and
• the selected copy-format preference.

The reviewed implementation does not use chrome.storage.local to save the full inspected page snapshot, a list of inspected URLs, extracted page text, link inventories, media inventories or exported JSON content.

HTTP and HTTPS Page Access

PageData declares host access for ordinary http:// and https:// webpages because its core function requires reading the DOM of the webpage the user is inspecting.

When the Side Panel needs a snapshot, the extension uses its packaged inspection function in the active supported page. That function reads the page information described in this policy and returns the result to the PageData Side Panel.

This access is not used to build a developer-operated browsing-history database. PageData version 1.0.4 does not transmit inspected URLs or extracted DOM data to a developer backend.

PageData does not declare access for unrelated non-web protocols merely to bypass Chrome's normal page protections.

Chrome Permissions and Protected Pages

PageData version 1.0.4 declares the sidePanel, scripting and storage permissions, together with host permissions for HTTP and HTTPS webpages.

• sidePanel is used to provide the persistent PageData inspection interface beside the active webpage.
• scripting is used to execute the packaged inspection function in a supported active webpage when PageData needs page data.
• storage is used for the limited local theme and copy-format preferences described above.
• HTTP/HTTPS host access allows PageData to inspect ordinary webpages where the browser permits extension scripting.

Chrome restricts extension scripting on protected surfaces such as many chrome:// pages and Chrome Web Store pages. PageData respects those restrictions and presents an unavailable or protected-page state instead of attempting to bypass Chrome's security boundary.

Network Requests, Remote Code, and Backend Services

The reviewed PageData 1.0.4 package does not include a developer-operated backend service, analytics service, advertising SDK, or remote executable script used for its inspection features.

Scanning, classification, filtering, formatting, copying and JSON-export preparation are performed locally by code included with the extension package.

The reviewed implementation does not contain a developer-configured endpoint for uploading inspected page titles, URLs, visible text, metadata, headings, links, media details, technical resource lists or exported snapshots.

The inspected webpage itself, Chrome, the Chrome Web Store and other browser components may independently make network requests for their own purposes. Those requests are controlled by the relevant website or platform and are outside PageData's own data practices.

Advertising, Tracking, Sharing, and Information Not Intentionally Collected

PageData version 1.0.4 does not display advertising and does not include an advertising SDK, behavioral analytics SDK, session-replay service, tracking pixel or developer-operated profiling system.

The extension is not designed to intentionally collect or maintain for the developer:

• names, email addresses, telephone numbers, postal addresses or PageData user accounts;
• passwords, authentication credentials, payment details or financial information;
• cookies or browser authentication tokens;
• current values typed into webpage form controls as part of its form summary;
• a persistent developer-maintained history of inspected pages or visited URLs;
• a cloud archive of visible page text, metadata, link lists, media lists or technical snapshots;
• advertising identifiers, demographic profiles or behavioral marketing segments.

Because the reviewed build does not send inspected page snapshots to a PageData backend, the developer does not maintain a remote PageData dataset of those snapshots for sale, advertising, analytics or data-broker sharing.

Retention, Removal, and Privacy-Oriented Design

The active inspection snapshot is held as PageData Side Panel state so the current data can be displayed, searched, selected, copied and exported. It is not written by version 1.0.4 to local extension storage as a persistent inspection history.

Theme and copy-format preferences can remain in chrome.storage.local so they can be restored in a later session. Users can remove extension-local data through Chrome's extension controls or by uninstalling PageData, subject to Chrome's own storage and deletion behavior.

PageData reduces unnecessary data exposure by keeping inspection and formatting local, avoiding a developer-operated inspection backend, limiting persistent storage to interface preferences, and honoring browser-protected pages.

No software can eliminate every privacy or security risk. Users should review data before intentionally copying it to the clipboard, exporting it to a file, or sharing it with another application or service, because those user-directed destinations are outside PageData's control.

Policy Changes and Contact

This Privacy Policy may be revised when PageData's implementation or data practices change. Examples that may require a meaningful update include adding new permissions, introducing a backend service, transmitting inspected page data, storing inspection history, adding analytics, changing the categories of page information read, or materially changing export or local-storage behavior.

Future versions should be reviewed against the actual PageData implementation rather than assuming that behavior described for version 1.0.4 remains unchanged indefinitely. Material revisions should include an updated effective date and version coverage where appropriate.

Questions about this Privacy Policy or the privacy behavior of PageData may be sent to thanhthuc284917@gmail.com.

When contacting support about privacy or extension behavior, users do not need to provide passwords, authentication tokens, private form values or other sensitive content. A description of the issue, the relevant PageData version and a non-sensitive example are generally sufficient.