NB - Native Browser Bridge

@@ -0,0 +1,115 @@+# Privacy Policy — Adom for Chrome & Edge++**Effective date:** June 24, 2026+**Publisher:** Adom Industries Inc. ("Adom", "we", "us")+**Contact:** [email protected] · https://adom.inc++This Privacy Policy explains how the **Adom for Chrome & Edge** browser extension (the+"Extension") handles information. It is written to be read alongside the extension's+permission justifications and the Chrome Web Store / Microsoft Edge Add-ons listings.++---++## Who we are, and why this extension needs broad browser capabilities++**Adom Industries is an AI electronics-prototyping company.** We build a full, AI-native+development environment for the entire electronics industry — and we let developers+everywhere build *on top of us*. Our ecosystem and our users are continuously writing and+running code: **web-based oscilloscopes, web-based electronic design automation (EDA) and+CAD software, and applications that drive and control real circuit boards** — all in the+browser, all day, every day.++Because Adom is a **complete development environment** — a "vibe coding" environment where an+AI assistant and the developer build software together in real time — the Extension must be+able to **fully operate the browser the same way a human developer does**: open and navigate+pages, read and screenshot what's on screen, fill forms, click controls, inspect the DOM, run+and debug JavaScript, and manage tabs, windows, downloads, and the developer's own logged-in+sessions. This is the **same category of capability that AI coding assistants such as the+Claude browser extension already use to drive a browser on the user's behalf.** We are, by+design, that same kind of tool: an AI agent's hands inside the developer's own browser.++That is the reason the Extension requests powerful permissions (such as the debugger,+all-sites access, and cookies). They exist to **deliver functionality the developer explicitly+asks for**, not to collect data about the developer. Every action the Extension takes is+initiated by the user, through their own Adom AI session, on their own machine.++---++## What the Extension can access++To act as the developer's hands in the browser, the Extension can, **when the user directs an+action**, access:++- **Page content & the DOM** of sites the user navigates or asks the AI to drive (to read,+  screenshot, fill, click, and inspect).+- **The Chrome DevTools Protocol (debugger)** for the active tab, to dispatch trusted input,+  capture full-page screenshots, evaluate/debug JavaScript, and read console/network logs —+  exactly what a developer or an AI coding assistant needs to build and test web apps.+- **Tabs, windows, navigation history, and downloads** the user asks to open, switch, reload,+  or save.+- **Cookies and the user's signed-in sessions**, so authenticated workflows (the developer's+  own logged-in tools, dashboards, and vendor sites) work without re-login — the same sessions+  the user already has in their browser.+- **Local extension storage**, to remember the user's session/window mapping between commands.++The Extension does **not** silently scan, harvest, or index your browsing. It accesses a page+only as part of carrying out a command you (or your AI session, acting for you) issue.++## How information is used and where it goes++- The Extension runs **inside your own browser** and connects, via a Chrome **native-messaging+  host on your own computer**, to your local **Adom Desktop** application. Commands flow *to*+  the Extension and results (including screenshots and page data) flow *back* to **your own+  active Adom AI session** so the AI can complete the task you asked for.+- Depending on how you run Adom, that AI session may execute in **Adom cloud infrastructure+  you control**. In that case the page data and screenshots needed for your task transit to+  that session **solely to fulfill your request** — the same way any cloud-based AI assistant+  receives the page it is helping you with.+- We use this information **only to perform the automation the user requests.** We do **not**:+  - sell or rent it;+  - use it for advertising or to build advertising profiles;+  - use it for any purpose unrelated to the user-requested feature;+  - share it with third parties except infrastructure providers that process it on our behalf+    to deliver the service, under confidentiality obligations.++## Data we do **not** collect++We do not collect or store the contents of your web pages, your passwords, or your browsing+history as a standalone product dataset. Saved passwords are never decrypted or exfiltrated by+the Extension — where a login is needed, the **browser's own autofill** fills it. The Extension+is a conduit for your own commands, not a data-collection product.++## Retention++Operational data (screenshots, page snapshots, command results) exists only for as long as+needed to complete your request and to appear in your AI session transcript, after which it is+subject to that session's normal retention. The Extension itself keeps only minimal local state+(your session-to-window mapping) in your browser's local storage, which you can clear at any+time by removing the Extension.++## Security++Traffic between the Extension and your machine uses Chrome's native-messaging channel and a+loopback (127.0.0.1) connection that is pinned to this Extension's identity, so other pages and+extensions cannot drive it. Connections out to your Adom session use authenticated, encrypted+transport.++## Your controls++- Remove the Extension at any time (Chrome/Edge → Extensions → Remove) to revoke all access.+- The Extension acts only while your Adom Desktop and an Adom AI session are connected; with+  them closed, it does nothing.+- Requests to access or delete data tied to your account: **[email protected]**.++## Children++The Extension is a professional developer tool and is not directed to children under 13.++## Changes++We may update this policy as the product evolves; the "Effective date" above will change and+material updates will be reflected on this page.++## Contact++**Adom Industries Inc.** — [email protected] — https://adom.inc

@@ -0,0 +1,148 @@+<!doctype html><html lang="en"><head><meta charset="utf-8">+<meta name="viewport" content="width=device-width,initial-scale=1">+<title>Privacy Policy — Adom for Chrome &amp; Edge</title>+<style>+body{max-width:760px;margin:40px auto;padding:0 20px;font:16px/1.6 -apple-system,Segoe UI,Roboto,sans-serif;color:#1d1d1f;background:#fff}+h1{font-size:30px;line-height:1.2}h2{font-size:21px;margin-top:1.8em;border-top:1px solid #eee;padding-top:1em}h3{font-size:17px}+code{background:#f3f4f6;padding:1px 5px;border-radius:4px;font-size:.9em}+a{color:#0a66c2}hr{border:none;border-top:1px solid #eee;margin:1.5em 0}+table,th,td{border:1px solid #ddd;border-collapse:collapse;padding:6px 10px;text-align:left}+@media(prefers-color-scheme:dark){body{background:#0d1117;color:#e6edf3}code{background:#1b2230}a{color:#58a6ff}h2,hr{border-color:#222}}+</style></head><body>+<h1>Privacy Policy — Adom for Chrome &amp; Edge</h1>++<p><strong>Effective date:</strong> June 24, 2026</p>+<p><strong>Publisher:</strong> Adom Industries Inc. ("Adom", "we", "us")</p>+<p><strong>Contact:</strong> [email protected] · <a href="https://adom.inc">https://adom.inc</a></p>++<p>This Privacy Policy explains how the <strong>Adom for Chrome &amp; Edge</strong> browser extension (the</p>+<p>"Extension") handles information. It is written to be read alongside the extension's</p>+<p>permission justifications and the Chrome Web Store / Microsoft Edge Add-ons listings.</p>++<hr>++<h2>Who we are, and why this extension needs broad browser capabilities</h2>++<p><strong>Adom Industries is an AI electronics-prototyping company.</strong> We build a full, AI-native</p>+<p>development environment for the entire electronics industry — and we let developers</p>+<p>everywhere build *on top of us*. Our ecosystem and our users are continuously writing and</p>+<p>running code: **web-based oscilloscopes, web-based electronic design automation (EDA) and</p>+<p>CAD software, and applications that drive and control real circuit boards** — all in the</p>+<p>browser, all day, every day.</p>++<p>Because Adom is a <strong>complete development environment</strong> — a "vibe coding" environment where an</p>+<p>AI assistant and the developer build software together in real time — the Extension must be</p>+<p>able to <strong>fully operate the browser the same way a human developer does</strong>: open and navigate</p>+<p>pages, read and screenshot what's on screen, fill forms, click controls, inspect the DOM, run</p>+<p>and debug JavaScript, and manage tabs, windows, downloads, and the developer's own logged-in</p>+<p>sessions. This is the **same category of capability that AI coding assistants such as the</p>+<p>Claude browser extension already use to drive a browser on the user's behalf.** We are, by</p>+<p>design, that same kind of tool: an AI agent's hands inside the developer's own browser.</p>++<p>That is the reason the Extension requests powerful permissions (such as the debugger,</p>+<p>all-sites access, and cookies). They exist to **deliver functionality the developer explicitly</p>+<p>asks for**, not to collect data about the developer. Every action the Extension takes is</p>+<p>initiated by the user, through their own Adom AI session, on their own machine.</p>++<hr>++<h2>What the Extension can access</h2>++<p>To act as the developer's hands in the browser, the Extension can, **when the user directs an</p>+<p>action**, access:</p>++<ul>+<li><strong>Page content &amp; the DOM</strong> of sites the user navigates or asks the AI to drive (to read,</li>+</ul>+<p>  screenshot, fill, click, and inspect).</p>+<ul>+<li><strong>The Chrome DevTools Protocol (debugger)</strong> for the active tab, to dispatch trusted input,</li>+</ul>+<p>  capture full-page screenshots, evaluate/debug JavaScript, and read console/network logs —</p>+<p>  exactly what a developer or an AI coding assistant needs to build and test web apps.</p>+<ul>+<li><strong>Tabs, windows, navigation history, and downloads</strong> the user asks to open, switch, reload,</li>+</ul>+<p>  or save.</p>+<ul>+<li><strong>Cookies and the user's signed-in sessions</strong>, so authenticated workflows (the developer's</li>+</ul>+<p>  own logged-in tools, dashboards, and vendor sites) work without re-login — the same sessions</p>+<p>  the user already has in their browser.</p>+<ul>+<li><strong>Local extension storage</strong>, to remember the user's session/window mapping between commands.</li>+</ul>++<p>The Extension does <strong>not</strong> silently scan, harvest, or index your browsing. It accesses a page</p>+<p>only as part of carrying out a command you (or your AI session, acting for you) issue.</p>++<h2>How information is used and where it goes</h2>++<ul>+<li>The Extension runs <strong>inside your own browser</strong> and connects, via a Chrome **native-messaging</li>+</ul>+<p>  host on your own computer<strong>, to your local </strong>Adom Desktop** application. Commands flow *to*</p>+<p>  the Extension and results (including screenshots and page data) flow *back* to **your own</p>+<p>  active Adom AI session** so the AI can complete the task you asked for.</p>+<ul>+<li>Depending on how you run Adom, that AI session may execute in **Adom cloud infrastructure</li>+</ul>+<p>  you control**. In that case the page data and screenshots needed for your task transit to</p>+<p>  that session <strong>solely to fulfill your request</strong> — the same way any cloud-based AI assistant</p>+<p>  receives the page it is helping you with.</p>+<ul>+<li>We use this information <strong>only to perform the automation the user requests.</strong> We do <strong>not</strong>:</li>+<li>sell or rent it;</li>+<li>use it for advertising or to build advertising profiles;</li>+<li>use it for any purpose unrelated to the user-requested feature;</li>+<li>share it with third parties except infrastructure providers that process it on our behalf</li>+</ul>+<p>    to deliver the service, under confidentiality obligations.</p>++<h2>Data we do <strong>not</strong> collect</h2>++<p>We do not collect or store the contents of your web pages, your passwords, or your browsing</p>+<p>history as a standalone product dataset. Saved passwords are never decrypted or exfiltrated by</p>+<p>the Extension — where a login is needed, the <strong>browser's own autofill</strong> fills it. The Extension</p>+<p>is a conduit for your own commands, not a data-collection product.</p>++<h2>Retention</h2>++<p>Operational data (screenshots, page snapshots, command results) exists only for as long as</p>+<p>needed to complete your request and to appear in your AI session transcript, after which it is</p>+<p>subject to that session's normal retention. The Extension itself keeps only minimal local state</p>+<p>(your session-to-window mapping) in your browser's local storage, which you can clear at any</p>+<p>time by removing the Extension.</p>++<h2>Security</h2>++<p>Traffic between the Extension and your machine uses Chrome's native-messaging channel and a</p>+<p>loopback (127.0.0.1) connection that is pinned to this Extension's identity, so other pages and</p>+<p>extensions cannot drive it. Connections out to your Adom session use authenticated, encrypted</p>+<p>transport.</p>++<h2>Your controls</h2>++<ul>+<li>Remove the Extension at any time (Chrome/Edge → Extensions → Remove) to revoke all access.</li>+<li>The Extension acts only while your Adom Desktop and an Adom AI session are connected; with</li>+</ul>+<p>  them closed, it does nothing.</p>+<ul>+<li>Requests to access or delete data tied to your account: <strong>[email protected]</strong>.</li>+</ul>++<h2>Children</h2>++<p>The Extension is a professional developer tool and is not directed to children under 13.</p>++<h2>Changes</h2>++<p>We may update this policy as the product evolves; the "Effective date" above will change and</p>+<p>material updates will be reflected on this page.</p>++<h2>Contact</h2>++<p><strong>Adom Industries Inc.</strong> — [email protected] — <a href="https://adom.inc">https://adom.inc</a></p>++</body></html>\ No newline at end of file