Overview
SurroundR is operated by EKSPOSE BV in Belgium under a GDPR-first posture, with primary infrastructure and data storage in the EU, and your contact data lands in your own HubSpot portal. We are a pipe into your CRM — not a data broker.
Legal entity: EKSPOSE BV · BE 0541.832.102 · Antwerp, Belgium
GDPR
Compliant · EU-based processor
EU Data Residency
HubSpot EU1 · Belgium HQ
Opens email to support@surroundr.io with subject prefilled. Available on paid plans.
SurroundR is operated by EKSPOSE BV in Belgium under a GDPR-first posture, with primary infrastructure and data storage in the EU, and your contact data lands in your own HubSpot portal. We are a pipe into your CRM — not a data broker.
Legal entity: EKSPOSE BV · BE 0541.832.102 · Antwerp, Belgium
What moves where — and what does not. LinkedIn context you trigger, optional enrichment, then write to your HubSpot.
When you trigger a capture or sync, SurroundR reads LinkedIn profile and conversation context — not a background scrape of your network. Typical fields: name, headline, company, role, and LinkedIn URL from the public profile.
The extension sends the capture to SurroundR so enrichment can run (verified work email and/or mobile from third-party B2B data providers when requested) and HubSpot OAuth can write the record. OAuth tokens are encrypted with AES-256-GCM.
Contacts and companies are written to your HubSpot account via OAuth. Captured contacts stay in your CRM — we do not resell, repackage, or train models on your data.
SurroundR never sees your HubSpot password. We do not sell personal data. Captured contacts stay in your CRM — we do not resell, repackage, or train models on them.
When you connect SurroundR, HubSpot lists every permission on the consent screen — including the "unverified app" wall for apps not yet in the marketplace. Here is what each permission is for.
Contacts, companies, and deals — create and update what you capture, and see associated deals from the extension.
Powers the Add-to-sequence button and upcoming workflow-triggered LinkedIn automation.
Your portal's users, permissions, and property definitions — team management and field mapping.
CRM records
| Permission | Access | Why we ask |
|---|---|---|
| Contacts | Read | Match against your existing contacts so captures update records instead of creating duplicates. |
| Contacts | Write | Create and update the contacts you capture from LinkedIn, including enriched emails and mobiles. |
| Companies | Read | Associate captured contacts with the right company records. |
| Companies | Write | Create or update the company when a LinkedIn profile's employer isn't in your portal yet. |
| Deals | Read | Power the Deals tab in the extension — see a contact's associated deals without leaving LinkedIn. |
| Deals | Write | Deal creation from inside SurroundR is rolling out — create a deal the moment a conversation turns real. |
Property settings (schemas)
| Permission | Access | Why we ask |
|---|---|---|
| Contact property settings | Read | Read your property definitions so field mapping shows your real HubSpot fields. |
| Contact property settings | Write | Create the SurroundR properties your field mapping needs when they don't exist yet (e.g. LinkedIn URL) — we never delete or overwrite your own property definitions. |
| Company property settings | Read | Read your property definitions so field mapping shows your real HubSpot fields. |
| Company property settings | Write | Create the SurroundR properties your field mapping needs when they don't exist yet (e.g. LinkedIn URL) — we never delete or overwrite your own property definitions. |
| Deal property settings | Read | Read your property definitions so field mapping shows your real HubSpot fields. |
| Deal property settings | Write | Create the SurroundR properties your field mapping needs when they don't exist yet (e.g. LinkedIn URL) — we never delete or overwrite your own property definitions. |
Import
| Permission | Access | Why we ask |
|---|---|---|
| CRM import (create / modify via import) | Read & write | Bulk capture writes records through HubSpot's import path for reliable high-volume syncs. |
Users & permissions
| Permission | Access | Why we ask |
|---|---|---|
| Users assigned on CRM records | Read | Team management — sync your portal's users into SurroundR so you can assign seats and keep record ownership correct. |
| User object | Read | Team management — sync your portal's users into SurroundR so you can assign seats and keep record ownership correct. |
| Account users & permissions | Read | Team management — sync your portal's users into SurroundR so you can assign seats and keep record ownership correct. |
Automation
| Permission | Access | Why we ask |
|---|---|---|
| Workflows | Read & write | Powers native LinkedIn automation from HubSpot workflows — trigger SurroundR actions (like connection requests or messages) as workflow steps. Rolling out. |
| Sequences | Read | Show whether a contact is already enrolled before you add them. |
| Sequence enrollments | Write | The Add-to-sequence button — enroll a captured contact directly from LinkedIn (requires Sales Hub Pro on HubSpot's side). |
Account
| Permission | Access | Why we ask |
|---|---|---|
| Basic account info (domain, user emails) | Read | Identify which portal is connected and who installed the app. |
The scopes shown match the HubSpot consent screen you will see when you connect.
Separate from HubSpot scopes: how the Chrome extension behaves on LinkedIn.
On LinkedIn, SurroundR reads only the profile page you are actively viewing — when you click to capture. It does not background-scrape your network.
Who may process data on our behalf. Ten named vendors plus a vendor-agnostic enrichment category.
10 named subprocessors + vendor-agnostic enrichment — full register with the DPA
| Vendor / category | Purpose | Region notes |
|---|---|---|
| HubSpot | CRM sync destination — your contacts land in your own portal. | Follows your HubSpot data residency (EU1 for EU customers). |
| Amazon Web Services | Video message (Chirp) and file storage. | EU |
| Fly.io | Application and processing infrastructure. | Primarily EU (Amsterdam/Frankfurt). |
| Vercel | Web application hosting. | Global edge |
| Stripe | Billing and payments. | US/Global — with appropriate safeguards (see privacy policy). |
| PostHog | Product analytics. | EU |
| Sentry | Error monitoring. | EU |
| Scaleway | Transactional email (invites, notifications). | EU (Paris) |
| Featurebase | In-app support chat and feedback. | See vendor DPA |
| Tag management on the marketing site. | Global | |
| B2B data providers (enrichment) | Optional verified email/mobile enrichment when you request it. | Vendor-agnostic waterfall; named register available with the DPA on paid plans. |
All third parties are contractually bound by confidentiality and data protection obligations. We do not sell personal data. Full privacy policy for legal detail. Privacy policy
DPA available on request for paid plans. When EKSPOSE BV acts as processor for customer-controlled prospect data, a DPA (GDPR Art. 28) covers Mono and Stereo — not Free.
Email support@surroundr.io. We will send the agreement for signature. A public /legal/dpa page is not published yet.
Controller vs processor in the privacy policyHow we protect the product — grouped for reviewers. Only claims we can stand behind from public product and privacy copy.
We do not claim SOC 2, ISO 27001, or other certifications on this page. Continuous efforts are made to minimize risk; no system can guarantee absolute security.
Short answers for security reviewers and RevOps buyers evaluating SurroundR.
SurroundR is built and operated in Belgium by EKSPOSE BV under EU GDPR. We take a GDPR-first posture: legitimate-interest processing in a B2B context where applicable, primary infrastructure and data storage in the EU, contact data landing in your HubSpot portal, and a DPA available on paid plans when we act as processor.
Individuals whose public LinkedIn profile may have been captured can use the Delete my data page. We confirm within 24 hours and complete deletion within 7 days. SurroundR customers deleting their own account or exports should email support@surroundr.io.
Primary infrastructure and data storage are in the EU; application compute can scale outside the EU where needed. Captured contacts are written to your HubSpot account. SurroundR operates with HubSpot EU1; your CRM data residency follows your HubSpot portal configuration. Video message (Chirp) storage is in the EU (AWS).
SurroundR requests HubSpot OAuth scopes covering: Contacts, Companies, Deals, Contact property settings, Company property settings, Deal property settings, CRM import (create / modify via import), Users assigned on CRM records, User object, Account users & permissions, Workflows, Sequences, Sequence enrollments, Basic account info (domain, user emails). Access levels are listed in the consent-screen table on this page — including deals and property-schema permissions, not contacts and companies alone. You approve the exact list on HubSpot's consent screen. Authentication uses OAuth 2.0 — SurroundR never sees your HubSpot password. OAuth tokens are encrypted with AES-256-GCM.
SurroundR reads only the LinkedIn profile you are actively viewing when you click to capture — not your messages, connections list, or feed, and not browsing outside linkedin.com. Every capture is a deliberate click; there is no background auto-scrape. Captured contacts go to your HubSpot portal; we do not sell, share, or reuse them for anyone else.
Yes on paid plans (Mono and Stereo). Request a DPA by emailing support@surroundr.io. The Free tier does not include a DPA, matching the pricing comparison table.
The public register on this page lists 10 named subprocessors (including HubSpot, AWS, Fly.io, Vercel, Stripe, PostHog, Sentry, Scaleway, Featurebase, and Google) plus a vendor-agnostic enrichment category. The named enrichment register is available with the DPA on paid plans.
Connections use HTTPS/TLS. HubSpot OAuth tokens are encrypted with AES-256-GCM. See the Security controls section for product, infrastructure, organizational, and data & privacy controls.
Captured contacts are written to your HubSpot account — we are a pipe, not a data broker. We do not resell, repackage, or train models on your contacts. Operational processing (for example enrichment and deletion requests) is described in the privacy policy and Delete my data page.
No. A full audit of our codebase confirms no customer or prospect data is sent to any AI/LLM provider. If that ever changes, it will appear on this page and in our subprocessor register first.
If you believe you have found a security vulnerability in SurroundR, email us with details. We take responsible disclosure seriously and will follow up on reports sent to support@surroundr.io.
Procurement
Email support@surroundr.io — we help security reviewers and RevOps buyers self-serve. Primary action: request the DPA on a paid plan.
