Privacy policy — PulsarGTM

What Pulsar Enrich is

Pulsar Enrich, built by PulsarGTM Ltd, is a contact-enrichment engine that connects to your team's Salesloft account. When Salesloft sends us a webhook for a person on a cadence you've enabled, we look up missing phone or email details through data providers you've configured, and write the result back to that person's record in Salesloft. This policy describes what data we collect, why, and where it goes.

The BYOK model — whose data this is

Pulsar Enrich is "bring your own key": your team connects its own Salesloft account and its own accounts with whichever enrichment providers you choose. We don't operate a shared pool of contact data across customers — each tenant's Salesloft connection, provider credentials, cadence configuration, and enrichment history are isolated to that tenant and not visible to any other tenant.

The one thing shared across teams is how phone numbers perform. Pulsar Connect scores each phone number (which number to call first) from every team's calls to it. Numbers are only ever stored as salted hashes, so the score is keyed to a hash, not a readable number, and no team sees another team's calls, people, companies or results. This is pseudonymised data, not anonymous: we hold the salt, so we treat it as personal data and protect it accordingly.

Data we collect and why

We collect the following categories of data in order to run the service:

Account and connection data. Your company name, your Salesloft connection (auth method, a webhook callback token we generate, and which custom fields your Salesloft instance supports), and the waterfall and cadence settings you configure in the dashboard.
Sign-in email addresses. When someone requests a sign-in link, we temporarily store the email address they entered along with a one-time code and link, so we can verify it belongs to an active Admin on your connected Salesloft team. This record expires after 30 minutes (or sooner if you resend); we don't maintain a separate list of named user accounts beyond this.
Provider credentials. The Salesloft and enrichment-provider API keys you enter are encrypted at rest (see our Security page for how) and are only decrypted in memory, at the moment we need to make a call on your behalf. We never log or re-display a credential after you enter it.
Contact and enrichment data. For each person your cadence sends us, we store the Salesloft person and cadence IDs, a best-effort display name, which provider we tried, the enrichment result (the phone number, email, job title, or custom field value it returned, and its confidence level where available), and a status trail for that job. This is what lets the dashboard show you what happened and lets a failed Salesloft write-back be retried without spending a second credit.
Usage and audit records. Every enrichment attempt is logged — what triggered it, which provider, the outcome, and credits spent — for the activity view in the dashboard and for troubleshooting.

The browser extension (Pulsar Lens, coming soon)

Pulsar Lens, our extension for Chrome and Edge, works only on Salesloft, LinkedIn and Pulsar’s own pages. It signs in with a key made for your team, which you can disconnect at any time in Settings. It never holds your Salesloft or provider keys: everything goes through Pulsar with the same checks as the app.

On Salesloft, it reads only the address of the page you’re on, to know which person is open, and shows what Pulsar already holds about their numbers.
On LinkedIn, it reads one profile, the one on screen, only when you click “Read this profile”: name, job title, company, location and the profile’s address. You can correct them before anything is sent. Pulsar sends them to your Salesloft when you click “Add to Salesloft”, and keeps only a salted hash of the LinkedIn address, for spotting duplicates. The extension doesn’t browse, scroll, or read pages in the background.
Someone added without an email gets a stand-in address at no-email.pulsargtm.com, which can’t receive mail, and Pulsar asks Salesloft to hold back emails to them until Enrich finds a real address.

Where data goes

Two different things happen with your data, and they're worth telling apart:

Your own vendor relationships. Salesloft (where contact data comes from and where results get written) and whichever enrichment providers you've connected receive contact identifiers because you've configured your own account with them to be called on your behalf. That data exchange is governed by your own agreement with each of those companies, not by us.
Infrastructure we use to run the service. We rely on a small number of infrastructure providers to host the application and move data through it:
- Railway — hosts our application servers, background worker, Postgres database, and Redis queue. All tenant data described above lives in Railway-hosted Postgres.
- Resend — delivers the sign-in link and code emails, and the messages sent through this website's forms to our inbox. Resend receives the recipient and sender email addresses and the message content for each email.

This website

pulsargtm.com is a static site. It sets no cookies of its own and runs no analytics or tracking scripts. Fonts are loaded from Google Fonts, which means Google receives your IP address and browser details when a page loads; see our cookie policy. If you use a contact or walkthrough form, we receive what you enter (your name, email, company and message) and use it only to reply to you. It's emailed to our inbox through Resend; the form itself isn't stored on the site, and we keep the email only as long as the conversation needs.

Data retention

Sign-in codes expire after 30 minutes. Import's uploaded rows (and the values an import replaced, kept so it can be undone) are deleted 30 days after each import finishes. Everything else — connection data, credentials, enrichment history, call history, audit logs — is kept for as long as your team's account is active. An admin can disconnect Salesloft or delete all of the team's data at any time from Workspace settings, or you can email us (below) and we'll do it.

When a team deletes its data, one thing is kept: for each phone number its team called (as a salted hash), how many calls were made and how many connected, week by week, for up to two years. It carries nothing that links it to the team — no people, companies, reps, call outcomes or exact times — and it is used only to score phone numbers for every team.

Your rights and deletion requests

You can ask us what data we hold for your team, correct it, or delete it, at any time, by emailing privacy@pulsargtm.com. We don't have a formal response-time SLA published here yet — we'll follow up promptly, and can commit to specific timelines in a signed data processing agreement if your team needs one.

Changes to this policy

We'll update the "last updated" date above whenever this page changes, and we'll keep it in sync with what the product actually does rather than let it drift.

Contact

Questions about this policy or your data: privacy@pulsargtm.com.

PulsarGTM Ltd, registered in England & Wales, company number 17516178 · Registered office: 66 Paul Street, London EC2A 4NA, United Kingdom.