How The Extension Talks To Hivi
How the extension talks to hivi
This article explains what happens on the wire in everyday language. For legal detail, always read the Privacy Policy and Terms.
Core idea
The extension works inside Chrome on pages where you use hivi. It reacts to actions you take after you turn autofill on for that site, or to buttons you click (such as LinkedIn import). It sends just enough context to hivi so the service can return suggestions or saved captures you asked for.
Typical flows
| You do… | What is sent (summary) |
|---|---|
| Focus a field / open suggestions | Field metadata the page exposes: name, id, label text, placeholder, aria-label, frame origin, page URL—so hivi can match against your profile. |
| Fill all on this page | Similar metadata for many fields in one pass. |
| AI suggestion button (when shown) | Same field context plus server-side processing to propose text when there is no direct profile match. |
| Import LinkedIn profile (on your profile page) | Parsed visible profile content you chose to import. |
| Add to job search (if your account has this feature) | Parsed job posting fields when you trigger capture. |
| Sign in in the popup | Credentials over TLS, same as signing in on the website. |
Default protections
- Autofill stays off on
chrome://and other restricted browser pages. - Autofill uses per-site opt-in: it contacts hivi when you enable a site and use a feature, rather than on every keystroke across the web.
If you share a computer
Sign out of the extension when you are done, or use a separate OS user profile. See Sign out and shared devices.