Catalyst Privacy Policy (DealArena Chrome extension)
Last updated: 2026-09-03 · Version v1.3
This policy covers Catalyst, the DealArena Chrome extension (the "Extension"), installed from the Chrome Web Store. It supplements DealArena.io's site-wide privacy policy (dealarena.io/privacy) and is specific to data the Extension collects in your browser.
We have one goal: be honest about the trade. The Extension contributes anonymized profile observations to a shared contact pool. In return, every DealArena user — including you — gets free contact enrichment, AI-drafted outreach, and signals on every prospect they view. This is the data moat the product is built on. We tell you what we collect, give you per-category controls, and let you revoke at any time.
Limited Use
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
In plain English: data collected by Catalyst is used to provide and improve the user-facing features described below. It is never sold, never used for advertising or credit-scoring, and is not read by humans except with your consent, for security and abuse review, or where the law requires it.
1. What we collect
1.1 On data-collection sites (LinkedIn, Sales Navigator)
When you visit a profile or search-result page on these sites, the Extension reads the visible text of the page (the same text rendered in your browser) and may send to DealArena's backend:
- The person's name, current title, current company, location, and headline.
- The canonical profile URL (e.g.,
linkedin.com/in/<slug>/). - The page URL the data was extracted from.
- A SHA-256 hash of
(your_user_id + a server-side secret)ascontributor_user_hash— used only for abuse detection. This hash is automatically nulled on observations older than 90 days by a nightly job.
We do NOT collect: - Your LinkedIn login session, cookies, password, OAuth tokens, or any auth state. - Direct messages, InMail conversations, or anything in your inbox. - Pages outside the listed data-collection sites (except as described in §1.2 below).
1.2 On other sites (universal capture surfaces)
The Extension's floating widget and pipeline-match badge are optional and off
by default. They run only after you explicitly grant Chrome's all-websites
permission from the popup or the onboarding screen, and you can revoke that
grant at any time (popup → Turn off, or chrome://extensions → site access).
When granted, they run on all websites excluding the listed data-collection
sites and dealarena.io itself. Their behavior:
- Floating widget: reads no page content. Displays your XP, streak, and quest state — fetched from DealArena's backend. Cannot read text outside its own UI.
- Pipeline-match badge: scans visible page text only for substring matches against your already-imported pipeline names/companies (cached locally, refreshed every 30 minutes). Matches are not transmitted off-device. The badge appears next to matching names; that's it.
- Right-click menu / popup capture / selection enrichment: these surfaces only send data to DealArena when you explicitly click them. They send the cleaned text of the active page (capped at 50,000 characters) plus the page URL, so DealArena can extract a prospect or company record.
The Extension does NOT silently transmit page content from non-data-collection sites. Read-only widget + opt-in capture only.
1.3 What you actively contribute via right-click / popup / capture
When you choose to capture a page (popup "+ as Prospect" / right-click context menu), the cleaned page text and URL are sent to DealArena's backend. If the page contains email addresses, those addresses may enter the shared contact pool — this is intentional and is the primary mechanism for free contact enrichment across users.
You can disable contribution-mode entirely (read-only Extension) at any time. See §3.
1.4 AI processing (large language models)
Three Extension features send text to a large language model to do their job. The processing happens on DealArena's servers, not in your browser, and the text is passed to a third-party model provider acting as our sub-processor:
- Page capture (popup "+ as Prospect / + as Company", right-click menu, paste-a-URL): the cleaned visible text of the page you chose to capture is transmitted to DealArena (capped at 50,000 characters), and up to the first 18,000 characters of it are sent to the model to extract a prospect or company record.
- ICP scoring: the profile fields being scored (name, title, company, location, headline) plus your own ICP definition are sent to the model.
- Draft outreach: the same profile fields plus your tone-of-voice traits are sent to the model to draft the message.
Our model sub-processors are Anthropic (all tiers today) and Groq (Basic-tier features as they migrate to it). Both process the text under commercial API terms; the data is not used to train their models. DealArena retains the extracted record, not the model conversation; captured page text may be held up to 90 days in the capture log for debugging and abuse review (§5), then deleted.
1.5 Macros (added in v1.2)
Every feature above only ever reads a page. Macros are the exception, and they are the reason this policy has a new version: a macro acts on a page. You record a sequence of clicks and typing, save it, and replay it later.
Macros are off until you switch them on (Settings → Extension, or the onboarding screen). Nothing below happens for a user who never enables them.
What is recorded. When you press Record, and only then, the Extension watches the tab you are on and writes down, for each action: how to find the element again (its stable attributes, its accessible label, its position in the page), what you typed into it, and the page URL. Recording stops when you press Stop or Esc.
What is never recorded. Password fields, credit-card fields, one-time codes, and any field inside a form that submits to a different site. These are detected and skipped before the value is read, so the text never enters the Extension at all. A macro that needed one of these pauses at that step and asks you to type it yourself.
Where macros are stored. On your device, in the browser's local extension storage. Macros are not uploaded to DealArena, not synced between your devices, and not shared with anyone. Deleting a macro, or uninstalling the Extension, deletes it. If a macro fails to find an element we may log the failure reason and the step number — never the recorded values — to help fix the matching, exactly as we do for profile extraction (§1.1).
How replay behaves. A macro runs only when you click Run, on the tab you are looking at, after confirming a prompt. It never starts on its own: there is no schedule, no background trigger, and no retry loop. While it runs, a banner across the top of the page says so and offers Stop; Esc also stops it. Steps are paced above a minimum interval that DealArena sets, and there is a cap on how many steps may run per hour. Replay stops immediately if a step's target cannot be found, or if it could match more than one thing on the page.
Your responsibility. Macros act as you, in your own logged-in session. Many sites — LinkedIn among them — restrict automated interaction in their terms of service, and using macros there may breach your agreement with that site and put your account at risk. DealArena gives you the tool and the limits above; the decision to point it at a particular site is yours.
We can switch it off. Macro availability is checked with DealArena on every session. If we need to disable the feature — for example because a site objects — it stops working without you updating anything.
2. How we use the data
- Your pipeline: profiles you capture become prospects in your DealArena CRM. This is the primary user-facing value.
- Shared contact pool: anonymized observations from all consenting users
feed
contact_graph_entries— a deduped, recency-weighted record of where each profile was last seen and what their current title/company is. Every consenting user can read from this pool (rate-limited). - Signal correlation: we monitor public sources for events relevant to prospects in your pipeline (job changes, funding, hiring, news). When a signal hits, we surface it in the drawer + push a desktop notification.
- Abuse detection: the
contributor_user_hashlets us detect whether any single contributor is submitting abnormally above the median rate (an indicator of automation). This hash is one-way and can't be reversed to your user_id without server-side secrets. - AI features: captured page text and profile fields power the extraction, ICP scoring, and outreach drafting described in §1.4, via our model sub-processors (Anthropic, and Groq for Basic-tier features). Nothing else is sent to a model.
We do NOT: - Sell your data to third parties. - Use observations for ad targeting or marketing analytics. - Build a profile of you — observations are about prospects you view, not about your own browsing.
3. Your controls
Per-category toggles (Settings → Extension privacy & data)
- Contribute observations — when off, we stop reading profile content on data-collection sites. Other Extension features still work.
- Contribute to contact graph — when off, emails / phones found in pages you capture do not enter the shared pool (they go only to your own pipeline).
- Show floating widget — toggle the cross-site widget UI.
- Notify on signals — toggle desktop notifications.
Consent revocation
Settings → Extension privacy & data → "Revoke consent". This:
- Immediately invalidates contribution mode for all your future Extension activity. The Extension keeps working in read-only mode.
- Within minutes, nulls the
contributor_user_hashon your observations from the last 90 days, unlinking them from your account. - Older observations have already had their hashes nulled by the routine 90-day scrubber, so they're already unlinked.
Account deletion
Deleting your DealArena account (Settings → Delete account) hard-deletes all your prospects, settings, ICP definition, consent record, and ledger. Anonymized observations remain in the shared pool because they are no longer linked to your account.
4. EU / UK / EFTA users
If your IP geolocates to an EU/UK/EFTA country (via Cloudflare's
Cf-Ipcountry header at the time of consent), the Extension issues you
a category='read_only' consent record. Contribution endpoints will 403
for read-only consent; the rest of the Extension features (drawer
lookups, ICP scoring, draft outreach, signals) work the same as for
non-EU users.
This is a temporary stance until v1.x ships granular GDPR-style consent flows. We'd rather exclude you from contribution than risk a non-compliant collection pipeline.
5. Data retention
| Data | Retention |
|---|---|
profile_observations |
Indefinite (anonymized by 90-day hash scrub) |
contact_graph_entries |
Indefinite (deduped, no per-user attribution) |
extension_capture_log |
90 days for debugging / abuse review |
extension_consent |
Permanent audit trail (granted_at + revoked_at) |
usage_ledger |
Permanent (billing history) |
Account deletion hard-deletes everything attributable to your account.
6. Security
- All Extension API calls go to
app.dealarena.ioover HTTPS with a per-user bearer token in theAuthorizationheader. Cookies are not shared across origins. The API origin is user-configurable in the popup for self-hosting and staging setups; calls then go to the origin you set. - Tokens are revocable from Settings → Extension token at any time.
- IPs at consent time are stored as SHA-256 hashes (
ip_hash), not as raw IPs.
- We don't request unnecessary Chrome permissions: no
tabs(broad history access), nowebRequest(network interception), nocookies. All-websites access is an optional permission you grant and can revoke; it powers only the widget + badge, and we do not exfiltrate page content from non-data-collection sites. - Macros (§1.5) added no new permissions. They reuse
scripting, are injected only into the single tab where you pressed Record or Run, and are not present on any other page. We deliberately did not adddebugger, which would let a macro produce browser-level input events: it is not needed, and an extension that can attach a debugger to your browser is not one we want to ask you to trust.
7. Contact
- Privacy questions:
privacy@dealarena.io - General support and bug reports:
team@dealarena.io
This document is canonical. The version published at dealarena.io/extension/privacy is the same content rendered from this file.