The Belda browser extension, and your data

What the extension is for

Belda is a CRM that runs a revenue motion end to end. Two of its steps happen on sites that have no API for this work: LinkedIn and WhatsApp Web. The extension performs those two steps in your own signed-in tab, one action at a time, at human pace, and only while that tab is open. It does one job and nothing beside it.

What it reads

On LinkedIn it reads the page you are on well enough to press the right button and type into the right box: the connect and message controls, and the name of the person whose profile the action names. On WhatsApp Web it reads the last message the other person sent on the thread it is about to write in, once, and compares it whole against the STOP words Belda handed over with the action. That comparison happens in the tab. The text of the thread never leaves the tab and is never sent anywhere.

It reads nothing on any other site. It has no permission for any site other than LinkedIn, WhatsApp Web, the Belda web app and the Belda API.

What it sends to Belda

The extension asks Belda for the next action, performs it, and reports the outcome. The report carries the action's own identifier, the outcome word (sent, skipped, failed, session absent, selector failed, and on WhatsApp stop received or not on WhatsApp), whether it ran assisted or by itself, one line of detail when something failed, and whether your tab was open. That is the whole report.

On LinkedIn there is one more thing it may say, and only about a person Belda itself queued an action for. When the action it just performed was on a profile and the page shows that you are connected with no invitation still pending, it tells Belda that the connection request was accepted. That message carries the profile address Belda handed over with the action and the moment your tab saw it, and nothing else. It is the address Belda already had, not one read off the page; Belda looks it up on your workspace's own records and, when it belongs to nobody there, nothing is read and nothing is written.

It sends no profile field, no message you received, no thread, no phone number, no contact list and no page content.

What it stores

In this browser, in the extension's own storage, the extension keeps one pairing bearer per lane, the address of the Belda API it pairs against, your run-mode switch, your local Stop, the one action it currently holds and when it may ask for the next one. Nothing else is stored.

• No LinkedIn or WhatsApp password, session cookie or QR code.
• No profile fields, messages, threads or phone numbers.
• No analytics, no advertising identifiers, no tracking of your browsing.

How pairing works

When you press Connect extension in Belda, the signed-in Belda tab asks the extension whether it is installed, then hands it a pairing ticket that is good for ten minutes. The extension completes the pairing itself and keeps the bearer the Belda API answers with. The address of the API follows the Belda tab you paired from, so a workspace on staging pairs against the staging API and a workspace on the live app pairs against the live one. If the extension is not installed, Belda shows a pairing code instead and nothing changes about what is stored.

Who can see what

Your pairing belongs to you and to your workspace. The bearer speaks for one lane only, and the Belda API answers it for exactly four things: take the next action, report an outcome, read the lane's health, and, on LinkedIn only, say that a connection request Belda queued was accepted. Anything else it might ask is refused, and a WhatsApp pairing is refused the fourth one too.

Belda's own data protection follows the workspace agreement your organisation holds with Belda; the data the extension itself adds is the outcome rows described above.

Stopping and removing it

Stop in the extension halts the lane in this browser at once. Stop in Belda halts it on the server too, so nothing is offered until you resume. Pair again replaces the pairing and the old bearer stops working the moment it does.

Removing the extension from Chrome removes everything it stored in this browser. Ask the person who runs your Belda workspace to unpair the lane if you also want the pairing closed on Belda's side.

Changes and questions

This page changes when the extension changes, and the date above says when it last did. Questions go to the person who runs your Belda workspace, who can reach Belda.