Privacy Policy

Last updated: September 3, 2026

This Privacy Policy explains how the DOM City — Visual Website Inspector browser extension handles information when you install, activate, and use the extension. DOM City is a developer and inspection tool that turns the currently selected webpage into an interactive isometric representation of its DOM structure.

Summary: DOM City analyzes the webpage only when you explicitly activate the extension on that page. The analysis happens locally in your browser. DOM City does not send scanned page content to a developer server, does not use analytics or advertising trackers, and does not sell or share scanned page information. The extension uses the activeTab and scripting permissions so it can inspect the page you deliberately choose.

1. Scope of This Privacy Policy

This Privacy Policy applies only to the DOM City — Visual Website Inspector browser extension and the functionality provided directly by that extension. It covers the source page scanning process, the generated isometric city, page-structure inspection, accessibility indicators, color and complexity views, source-element highlighting, and related extension functionality.

This policy does not apply to the websites you inspect, Google Chrome, the Chrome Web Store, your operating system, or other browser extensions and services. Those products and websites may process information independently under their own policies.

2. How DOM City Is Activated

DOM City does not continuously monitor browser tabs. The extension is activated when you click its toolbar button while viewing a normal webpage.

After activation, DOM City injects its inspection script into that specific page and opens a DOM City visualization tab. The extension then requests a snapshot of relevant page structure so it can construct the isometric city.

Access granted through activeTab is tied to the page on which you explicitly invoke the extension. DOM City is not designed to silently scan unrelated tabs in the background.

3. Information DOM City Reads From the Selected Page

To create the visual city and inspection views, DOM City reads limited information from meaningful visible elements on the webpage you choose to inspect. Depending on the page, this information may include:

The page title, URL, hostname, page dimensions, and scan timestamp.
HTML element types such as headings, sections, links, buttons, images, forms, tables, and other structural elements.
Generated CSS selectors used to reconnect a building in DOM City with its original source element.
Element dimensions and approximate document positions.
DOM hierarchy depth and semantic grouping information.
ARIA roles and selected accessibility-related attributes.
Short text associated with an element, including limited direct text, aria-label, or image alt text where applicable.
Selected computed style information such as background color, text color, font size, display mode, position, and z-index.
Whether an element appears interactive.
Locally calculated accessibility indicators such as missing image alt text, missing form labels, unlabeled controls, empty links, or unusually small text.

This information is needed to decide how webpage elements should be represented as buildings, districts, colors, accessibility states, and inspection details inside DOM City.

4. Page Content That Is Not Intentionally Collected

DOM City is not designed to extract or archive the complete contents of a webpage. The extension skips several non-visual or implementation-focused element types and limits how much page structure is processed for visualization.

DOM City does not intentionally collect or build a remote database containing:

Your general browsing history.
A list of websites you visited before or after activating DOM City.
Your browser search history.
Your saved passwords or authentication credentials.
Your browser cookies.
Your bookmarks or download history.
Your contacts, local files, photos, microphone data, or camera data.
Your precise or approximate physical location.
Payment information or financial account information.
Advertising identifiers or cross-site tracking profiles.

However, because DOM City is a webpage inspector, information already displayed or encoded in the specific page you activate may be represented in the local scan if it is associated with a meaningful visible DOM element. You should therefore avoid activating DOM City on a sensitive page if you do not want that page analyzed locally in the browser.

5. Local Processing of Scan Data

The DOM snapshot is processed locally by the extension. The source-page script sends the scan result through the browser extension messaging system to the DOM City visualization.

DOM City uses that in-memory scan result to calculate:

Building types and dimensions.
Semantic districts.
Isometric city layout.
Search and filtering within the current visualization.
Color-based representations.
Accessibility indicators.
Local complexity or performance-oriented estimates.
Source-element selection and highlighting.

DOM City version 1.0.1 does not use a developer-operated server to perform this analysis. The extension does not upload the scan result to a remote analysis API.

6. Data Storage and Persistence

DOM City version 1.0.1 does not use chrome.storage, localStorage, or a remote database to persist scanned webpage content as part of its normal inspection workflow.

The scanned representation is held for the current DOM City session so that you can pan, zoom, rotate, search, switch inspection modes, and select buildings. Closing the DOM City visualization tab ends that visualization session.

The source webpage itself remains controlled by the website and the browser. DOM City does not create a cloud archive of inspected pages.

7. Browser Permissions

DOM City version 1.0.1 requests the following Chrome permissions:

activeTab: allows DOM City to access the webpage on which you explicitly click the extension button. This is used to inspect that selected page and to communicate with it while the visualization is open.
scripting: allows DOM City to inject its packaged inspection script into the selected page after you activate the extension.

These permissions are used to provide the extension's core single purpose: visually inspecting the current webpage. DOM City does not request broad persistent host permissions covering all websites.

8. Source Element Highlighting

When you select a building in DOM City and choose the option to locate it on the source page, the extension sends the locally generated selector back to the inspected tab.

DOM City then scrolls the corresponding webpage element into view and temporarily draws a visual highlight overlay around it. This overlay is used only to help you identify the source element and is automatically removed shortly afterward.

This feature does not send the selector or element information to an external service.

9. Accessibility and Performance Indicators

DOM City's accessibility view performs lightweight local checks intended to help identify elements that may deserve review. Examples include missing image alternative text, form fields without detected labels, unlabeled controls, empty links, and small text.

These indicators are informational and are not a complete accessibility audit. A page that appears clear in DOM City may still contain accessibility issues, and a flagged element may require human review to determine whether it is actually problematic.

Likewise, performance or complexity views are visual estimates based on page structure and locally available element information. DOM City does not transmit performance telemetry to a remote monitoring service.

10. Analytics, Tracking, and Advertising

DOM City does not use third-party analytics platforms, advertising networks, tracking pixels, fingerprinting technologies, behavioral advertising systems, or cross-site tracking services.

The extension does not create an advertising profile based on the websites you inspect and does not send inspected page URLs or DOM snapshots to an analytics provider.

11. Network Requests and Third-Party Services

DOM City version 1.0.1 does not use fetch, XMLHttpRequest, WebSocket, or a developer API to upload scanned page data. The extension's HTML, JavaScript, CSS, and icon assets are packaged locally with the extension.

Chrome itself, the website you are viewing, your operating system, security software, or other browser components may independently make network requests. Those requests are not generated by DOM City's page-analysis backend because DOM City does not operate such a backend in this version.

12. Protected and Restricted Browser Pages

Chrome restricts extensions from injecting scripts into certain browser-owned or protected pages, including some internal browser pages and extension-store pages. DOM City may be unable to inspect those locations.

When access is unavailable, DOM City displays an error or protected-page message rather than attempting to bypass browser security restrictions.

13. Data Sharing and Sale

DOM City does not sell, rent, trade, license, or disclose scanned webpage information to advertisers, data brokers, marketing companies, analytics providers, or other third parties.

Because scan information is processed locally and is not uploaded to a DOM City server, there is no developer-maintained database of inspected page snapshots available for commercial sale or profiling.

14. Data Retention

DOM City does not maintain a remote retention period for inspected webpage data because it does not upload that data to a developer database in version 1.0.1.

The current scan is used for the active visualization session. Closing the visualization removes the active in-memory representation from that extension page. The original website remains subject to the website's own storage and privacy practices.

Browser crash recovery, operating-system memory management, security software, or other browser/platform behavior is outside DOM City's control.

15. Data Security

DOM City minimizes privacy exposure by using user-initiated tab access, avoiding broad host permissions, performing analysis locally, and avoiding a remote scan database.

No software environment can be guaranteed to be completely secure. Users should keep their browser and operating system updated and should use appropriate device security, especially when inspecting pages that contain confidential or sensitive information.

16. Your Choices and Control

You control when DOM City receives temporary access to a webpage by choosing when to click the extension button. If you do not want a particular page analyzed, do not activate DOM City on that page.

You can close the DOM City visualization tab at any time. You can also disable or uninstall the extension through your browser's extension management controls.

17. Children's Privacy

DOM City is a developer and webpage-inspection utility. It does not include a user account system, social profile, advertising profile, or feature intended to request personal information from children or other categories of users.

The extension does not knowingly collect personal information from children for storage on a DOM City server.

18. International Data Transfers

DOM City version 1.0.1 does not operate a remote system for collecting inspected webpage content. Because scanned page information is not intentionally uploaded to DOM City servers, DOM City does not ordinarily transfer that scan data between countries or remote data centers.

19. Changes to This Privacy Policy

This Privacy Policy may be updated to reflect changes to DOM City, browser platform requirements, legal requirements, or privacy practices.

If a future version introduces materially different behavior such as persistent scan storage, cloud analysis, analytics, accounts, remote services, or broader browser permissions, this policy should be updated to describe those changes.

When this policy is updated, the revised version will be published on this page and the “Last updated” date at the top will be changed accordingly.

20. Contact

If you have questions, concerns, or requests regarding this Privacy Policy or the privacy practices of DOM City, you can contact:

hanhruiroc@gmail.com