Auto-detection of new sites

When you land on a website Teleperson hasn't seen before, the extension does a quick reconnaissance pass and offers to add the company to your Hub. The first user to visit a new site does the work; every Teleperson user after them gets the result for free.

What happens behind the scenes

When the side panel opens on a site:

1. Identify the vendor. The background service worker looks up the current tab's domain against the shared catalog in Supabase. Hits short-circuit; the panel renders the cached company instantly.
2. Scrape a summary. On a miss, the content script collects the page title, meta description, OG tags, and any contact-page links. The background worker posts this digest to the backend.
3. Persist the company. The backend creates a new companies row tagged extension_suggested. The row is private to your Hub until an admin reviews it; until then it stays out of the public catalog browse list.
4. Surface to the user. The panel shows an Add to Hub prompt with the freshly-scraped name and logo. One click follows the company.

While identification is in flight the panel header shows "Great! A new site to learn!" and never the raw hostname or extension ID. As soon as the content script returns the page title (typically under 100ms) the header switches to that title; once the backend resolves the canonical name (typically under 500ms) the header switches again.

What gets sent

Only public page metadata: the URL, document title, meta description, Open Graph fields, and contact-page link hrefs. The extension does not send page body text, form data, cookies, or anything keyed by your account on the site.

What does not get sent

• Authenticated session cookies or tokens for the site.
• Form input, including search terms or login fields.
• DOM contents from pages behind a sign-in.
• Anything from the page when the side panel is closed.

Reviewing auto-added companies

Auto-added entries are tagged extension_suggested in the catalog. They are visible to the user who discovered them, but excluded from the public catalog browse list until an admin sets a reviewed_at timestamp on the row.

Admins resolve these from the Review queues page in the web app, on the User submissions tab. From there an admin can approve a submission as-is, edit the proposed values before approving, or reject it.

Privacy posture

The data flywheel is the point: every new user enriches the directory for everyone. But it works only because we keep the per-page footprint tiny. The security & privacy page covers what we collect and what we don't.

Related

• Submit a site to the library → — contribute extra info so other Teleperson users can find it.
• Company Hub → — where auto-detected companies show up.
• Security & privacy → — full data handling story.