The Belda browser extension, and your data

Last updated 17 November 2026.

Who we are and how to reach us

The extension is made and operated by Belda Technologies, Inc., a Delaware company, the company behind app.belda.ai. It is held by Mansour Ventures ApS, Thit Jensens Gade 4, 8000 Aarhus C, Denmark. For anything about your data, write to hussam@belda.ai and a person answers.

What the extension is for

Belda is the Autonomous Revenue Operating System. It 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 Chrome, one action at a time, at human pace: the LinkedIn steps in one pinned tab it opens for itself, so your own LinkedIn tabs are left alone, and the WhatsApp steps in your own WhatsApp Web tab, only while that tab is open. On a Sales Navigator search, lead list or lead page you have open it offers one button, Bring to Belda, that reads the page once and brings the people and companies it shows into your own workspace. Four optional features can do more, each only when you start it: Read my chats, Do it on this site, Show me once and the website form step, described below under Optional features, each started by you. Beyond these, the extension does nothing.

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, and only its outcome is reported. It also reads the number WhatsApp Web shows as your own, once at pairing and once per request for work, and keeps only its last two digits.

Your own conversations, so they land in your Inbox: while your LinkedIn messages (linkedin.com/messaging) are open in a tab and LinkedIn is paired, it checks the conversations that tab shows every 3 minutes, opening at most the 10 newest and only while that tab is in the background, and right after LinkedIn pairs it goes through your whole conversation list once. It never opens a conversation LinkedIn marks unread, so nobody is told you saw it. While your WhatsApp Web tab is open and WhatsApp is paired, it checks the chat that tab has open, every minute; a group chat is skipped. A chat your list shows unread is handed over as its last line without opening it, and counted as theirs only when your list showed your own tick since the page loaded, never when that row's send failed or still waits. With each WhatsApp check-in goes a tally of those readings by kind (such as unread rows, waiting chats, your tick seen), never a person's name, number or words. For each conversation it takes the other person's profile address on LinkedIn or the chat's number on WhatsApp, the name the header shows, on LinkedIn the line under that name, and each message with its id, whether you or they wrote it, its text and its moment. It opens no tab and focuses none to do this.

When you press Bring to Belda on a Sales Navigator search, lead list or lead page you have open, it reads that page once: the names, titles, companies, locations and lead links the page shows, and the list's name. It reads nothing before you press: no timer, no scroll handler, no background fetch. A list page is read as it stands, and the extension never scrolls for more by itself.

In a sequence you started, it also reads the posts a person's profile shows, on the visits your sequence makes: after a profile visit Belda itself queued, it reads that profile's Activity section once, as the page showed it, and reports how many in the last 30 days, the newest post's date, its first lines and its language. It reads only the profile the visit opened, only for a person in your data, never on a timer and never on a page you opened yourself.

The extension always has access to LinkedIn, WhatsApp Web, the Belda web app and the Belda API, and to nothing else. On any other website it reads nothing of the page: while the side panel is open it asks Belda about the site's address alone (its scheme and host, never the page within it, its title or its text) so the panel says New or In Belda, Belda answers and does not store that address, and anything more is read only through the optional features described under Optional features, each of which starts with your own click. Chrome asks you to allow a site the first time a feature needs it. Once you have pressed Allow contact forms on prospects' sites and allowed it, Chrome has allowed the extension on every https site at once and does not ask again site by site, for any feature. Removing the extension withdraws that permission.

What it sends to Belda

The extension asks Belda for the next action, performs it, and reports the outcome. When it asks for the next action, it says which version of the extension it is, which browser it runs in, whether you are signed in on the site, whether the run switch is on, whether this browser has allowed contact forms on prospects' sites, on LinkedIn whether your account shows Sales Navigator, and which version of the page recipes it holds. The report carries the action's own identifier, the outcome word (such as sent, skipped, failed, session absent or 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, whether its tab was open, the browser's name, whether the run switch was on, whether this browser dropped its pairing, and which of the page recipes' ways to find and press a control it tried and which one worked. When a step fails because a control was not found, that line lists the page's controls by role and shape alone: how many characters a button's label and the words on its face carry, whether a link has an address and the first word of its path, how long a text box's placeholder is. It never carries their words, so no name on the page travels with it.

Three kinds of step add to the report. A visit to a profile Belda queued adds whether you are connected with that person, and the title line, at most 300 characters, and current company that profile's top card shows; Belda uses these only to fill that person's title and company where it has none. Until Belda has taken the report, the extension keeps it in its own storage in your browser. A LinkedIn or Sales Navigator search Belda queued to find people at a company adds the people the search showed at that company, at most 10, each with name, title, company, location and profile link. A website form step adds the type and size of its two pictures. That is the whole report.

On WhatsApp it also tells Belda the last two digits of your own number, the one WhatsApp Web shows as yours, when it pairs and each time it asks for work. That is how Belda can say which number your messages go from. It never sends your whole number.

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, it tells Belda where the connection request stands as the page shows it: still pending, accepted (you are connected with no invitation pending), or gone (the Connect control is back on a profile Belda sent a request to). That message carries the profile address Belda handed over with the action, the state word 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.

Bring to Belda sends your own workspace what it read when you pressed it: the rows the page showed, the page's address and title, how many rows the page said it had, when it was read and, on a list, the list's name. Belda lands them as companies and people with a line that says where they came from, and tells you how many of the rows on the page it brought. Nothing of LinkedIn's is stored in the browser, Belda keeps no LinkedIn token, and pressing it sends no message, connection request or InMail.

The conversations taken from your own LinkedIn messages tab and WhatsApp Web tab go to your own workspace: each message once, with its id, whether you or they wrote it, its text and its moment, under the other person's profile address, name and the line under that name on LinkedIn or the chat's number and name on WhatsApp. Belda files them in your Inbox, a WhatsApp chat only when its number belongs to a person in your workspace.

Apart from the page you pressed Bring to Belda on, the people a search Belda queued showed, the posts read after a visit the sequence made, those conversations and the optional features described below, it sends no profile field, no message, no thread, no phone number beyond those two digits of your own and no page content.

What it stores

In this browser, in the extension's own storage, the extension keeps: one pairing bearer per channel, with the address of the Belda API it pairs against, when it was paired and when Belda last answered it; your run-mode switch and whether you set it yourself; your local Stop; the one action it currently holds, with the words Belda drafted for it and the person's name, company and page address it names; when it may ask for the next one; the id of the pinned tab the LinkedIn channel opened for itself; the ids of the window and tab it opens for a website form step, and when you first allowed contact forms on prospects' sites; and the page recipes Belda serves, which say which controls to look for on LinkedIn and WhatsApp Web and in what order, never anything about a person.

From the moment a step ends until Belda has acknowledged its report, it also keeps that report as it will be sent (see What it sends to Belda), so a report is not lost when the browser closes. For a LinkedIn or Sales Navigator search Belda queued, that report holds the people the search showed at the company, at most 10, with their names, titles, companies, locations and profile links. The report leaves the browser's storage the moment Belda acknowledges it. Nothing else is stored.

  • No LinkedIn or WhatsApp password, session cookie or QR code.
  • No messages, threads or phone numbers, and no profile fields beyond the search rows a report holds until Belda acknowledges it.
  • Nothing else a page showed. The steps you record with Show me once are held in the extension's memory while you record and go to your workspace; they are not stored in the browser.
  • No analytics, no advertising identifiers, no tracking of your browsing.

Optional features, each started by you

Four things the extension can do go beyond the LinkedIn and WhatsApp steps. Each is off until your workspace switches it on, each starts with a click of your own, and after that click only Read my chats runs again by itself, once a day while your WhatsApp Web tab is open. The extension asks for nothing on any site beyond the ones named here until you press the button of the feature that needs it.

Read my chats: on your own WhatsApp Web tab, when you press the button and then once a day while that tab is open, it reads the list of chats and hands your workspace one row per chat, at most forty each time: the name the row shows, the number when the name is one, whether it is a group or a business, the unread count, the last day and whether you or they wrote last. It does not read, store or send a single message. Those rows include other people's numbers, because they are the people in your chat list; they go only to your own workspace.

Do it on this site: you say what you want done on the page open in your tab. When you press Plan the steps, the extension sends your workspace up to 4,000 characters of that page's visible text with its address and title, so Belda can write the steps. Nothing happens until you press Approve. When you ask Belda for such a run from WhatsApp instead, the extension checks once a minute whether the run waits for your tab; on a site you already allowed, it sends the same reading of the page open in your active tab, and once you approve the steps it performs them in that tab while the tab is on that site. It then performs the steps in that tab, one at a time, and after each step reports what it did and the page's address after it, with a screenshot of your own tab put in your workspace's private storage. It never types into a password or payment field and never presses a control that sends, submits or pays before you have ticked that step. Chrome asks you to allow each site before the extension can act on it, unless you have already allowed contact forms on prospects' sites, which allowed every https site at once. Asks for this site when you press Plan the steps, for any other site a step opens when you press Approve, and for prospects' sites when you press Allow contact forms, never on its own. Belda never types into a password or payment field, and a step that sends or submits waits for your approval on its own card. A screenshot of each step goes to your workspace's private files. Belda writes the steps, you say yes, they run in this tab.

Show me once: you press Record, do the steps once on the page in your tab, and press Stop. When you press Record, the extension reads the start page once: its address, its title and up to 4,000 characters of its visible text. While you record, it describes each click, typed value and chosen option by the control's role and name, and notes the address of each page the tab moves to, at most twelve steps. On Stop it sends all of that to your workspace as a named recipe that Belda can repeat for companies you list. A password field is recorded with an empty value. Nothing is stored in the browser, and every repeat waits for your approval. Keeps steps only while you are recording, by each control's role and name, never by a selector. A password field is kept as a step with an empty value and Belda does not keep that recipe, so no password leaves this tab. Nothing runs for a company until you say yes on its row. Do the steps on this site once. Belda keeps them as a recipe and repeats them for every company you list, asking before anything leaves.

Website form step: when you have allowed it with one button, a sequence you started can have the extension open a window of its own, read a prospect's contact page once, fill the form with your own name, mailbox, company name and phone number, and send it, within your daily cap. That button asks Chrome to allow the extension on every https site at once, because the prospects' sites are not known ahead; once you allow it, Chrome does not ask again site by site. It never touches your own tabs, never types into a password or payment field, and never answers a captcha. It reports the outcome and two pictures of that window to your workspace. A website form step fills the contact form on a prospect's site from this browser, in a window of its own, one per company, within your cap. Website form steps wait until you allow prospects' sites in the extension's panel. Belda fills the contact form on a prospect's site from this browser, one per company, within your cap.

How pairing works

When you press Pair it 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.

Data we collect

In short, the extension collects these kinds of data, and only for the purposes described on this page: the outcome of each action it performs for you, with the technical facts described under What it sends to Belda; the last two digits of your own WhatsApp number; the connection status and the Activity summary of a LinkedIn profile Belda itself queued an action for; the people a LinkedIn or Sales Navigator search Belda queued showed at the company it looked for, at most 10, with name, title, company, location and profile link; only when you press Bring to Belda, the names, titles, companies, locations and lead links a Sales Navigator page shows; and the conversations your own LinkedIn messages tab and WhatsApp Web tab show while they are open (the other person's profile address or the chat's number, the name, and each message's text, whether you or they wrote it and its moment). The optional features add, each only when you use them: the chat list of your own WhatsApp Web tab (the name a row shows, the number when the name is one, whether it is a group or a business, the unread count, the last day and whether you or they wrote last, never a message); up to 4,000 characters of the visible text, the address and title of a page when you press Plan the steps, and after each step the page's address and a screenshot of your own tab; with Show me once, the start page's address, title and up to 4,000 characters of its visible text, the steps you recorded, described by control role and name, and the address of each page you visited while recording, never a password value; and, for a website form step your sequence queued, the outcome and two pictures of the window the extension opened for itself. The extension also keeps, and sends to the Belda API with each call, one pairing bearer per channel, which identifies you to Belda and is the only authentication data it handles. It collects no health, financial or payment data, no location and no passwords, and no browsing history beyond the page addresses Do it on this site and Show me once send and the LinkedIn profile and company page addresses, and the scheme and host of any other site, the open side panel asks about, described above.

How we use and share it

The data is used for one purpose: to run the steps you asked Belda to run, on LinkedIn, on WhatsApp Web and on the sites where you started an optional feature, to show you what happened, and to tell you in the open side panel whether Belda already has the person or the company your tab shows. We do not sell it, we do not share it with advertisers or data brokers, and we do not use it for advertising, credit or lending decisions, or for anything unrelated to the extension's single purpose. We share it with no third party. The only recipient is your own Belda workspace, and the service providers that host Belda and process data for it under agreement with Belda: Hetzner (application hosting, in Nuremberg, Germany, European Union), Supabase (database and private file storage, in Frankfurt, Germany, European Union) and the AI model providers Belda writes with: Anthropic, OpenAI, Google and DeepSeek. The page text you send with Plan the steps goes to Anthropic's Claude or to OpenAI, whichever Belda runs as its default, so Belda can write the steps; when that one is unavailable it goes to the other, when both are unavailable to Google's Gemini, and when Gemini is unavailable too, to DeepSeek. When Belda drafts a comment under a person's post, the post's first lines the extension read go to OpenAI or Anthropic, whichever writes the draft. People and companies the extension brings into your workspace, and the conversations it hands to your Inbox, are part of your workspace's data, which these providers also process when Belda sorts or summarizes that data, drafts a reply for your approval, or writes to people when you ask. Show me once, Read my chats and the website form step send nothing to a model. If the owner of your workspace picks another model for a step, or adds the workspace's own model keys, that step's text goes to the provider of the model the owner picked. Under their API terms Anthropic, OpenAI and Google may not train their models on this data by default, and they process it only on Belda's instructions and may not use it for their own purposes. DeepSeek's published terms do not say where it processes this data, how long it keeps it or whether it trains on it. Belda does not train models on it. The use of information received from Chrome and the Belda extension will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements: it is used only to provide the single purpose described above, it is not transferred to others except as needed to provide that purpose, it is not used for advertising, it is not sold, and no human reads it unless you ask for support, it is needed for security or a legal duty, or it has been aggregated and anonymized.

How long we keep it, and how to delete it

Outcome rows and rows brought in with Bring to Belda are kept in your workspace for as long as the workspace exists, so you can see what was sent and when. The pairing bearer is kept until you press Unpair or pair again, and it stops working the moment it is replaced. To have your data deleted, write to hussam@belda.ai, or ask the person who runs your workspace; we delete it within 30 days of a verified request, and everything the extension stored in your browser is removed when you remove the extension from Chrome.

What the optional features and the LinkedIn steps send has no fixed period either, and nothing of it is deleted on a timer. The chat list rows of Read my chats, the LinkedIn and WhatsApp messages filed in your Inbox, the sentence, page address, title and page text of each Do it on this site run, the recipes of Show me once with the steps you recorded and their start page, and the people a search Belda queued reported are kept in your workspace for as long as the workspace exists, and are deleted with it. A WhatsApp chat you ticked can be deleted on its own sooner: in Settings, under Connections, open the WhatsApp chat list, press Delete beside the chat and confirm. Belda then deletes the messages it filed from that chat and stores nothing more from it until you tick it again. The chat stays on your phone. What a profile's Activity section showed is kept on that person's record until the record or the workspace is deleted.

The screenshots of Do it on this site and the two pictures of a website form step are kept in your workspace's private file storage, also with no fixed period. Deleting your account or your workspace does not remove these files, and they are kept until Belda decides otherwise. Deleted rows can remain in Belda's nightly database backups for up to 7 days.

To delete your Belda account, open Settings, You and your data in the app and click Delete my account; your sign-in goes at once. If you cannot sign in, write to hussam@belda.ai from the address you signed up with and we delete it for you.

How we protect it

Everything the extension sends goes over HTTPS to api.belda.ai. The bearer is limited to one channel and refused anything it was not issued for. The extension holds no password, no session cookie and no QR code, so there is nothing of that kind to leak from it. The STOP comparison on a WhatsApp thread happens in your tab, and only its outcome leaves it.

Who can see what

Your pairing belongs to you and to your workspace. The bearer speaks for one channel only. The extension asks the Belda API for exactly twenty-nine things: to complete its own pairing, once, with the ten-minute pairing ticket; to read the page recipes Belda serves (which controls to look for and in what order, never anything about the person); to end that pairing when the person presses Unpair in the popup; to take the next action; to report the outcome of that action; when a step Belda queued finds none of the controls it looks for, to send the buttons and links of that page once (each one's role, its visible words, its label and data attributes and its place on the page, never a message and no other person's profile link), so Belda can name the control that does the step; to read the health of its own channel; on LinkedIn only, to say that a connection request Belda queued was accepted; on LinkedIn only, after a profile visit Belda queued, to report what that profile's Activity section showed on that visit (how many posts in the last 30 days, the newest post's date, its first lines and its language), under the address Belda handed over; on LinkedIn only, before a like, a repost or a comment Belda queued acts, to send the words, the shared link's title and the language of the newest posts that person's profile shows as their own, at most ten and never a name or an address, so Belda never likes, reposts or comments on a post about politics; when the person presses Bring to Belda on a Sales Navigator search, list or lead page they have open, to bring the people and companies that page shows into their own workspace; from the Do it on this site card, to write the steps for the page they have open, to read that run, to approve it, to stop it, and to report what one step did in their own tab; and, for a run the person asked for from WhatsApp, to read once a minute their runs that wait for their tab and to hand such a run the address, the title and up to 4,000 characters of the visible text of the page open in their active tab, only on a site they already allowed; and, from the Show me once card, to keep the steps they did on a site as a named recipe, to list the recipes they have kept, and to run a kept recipe for the companies they list, one held run per row; and, from the Read my chats card on the person's own WhatsApp Web tab, to hand their own workspace the chat list that tab shows (the name a row shows, the number when the name is one, whether it is a group or a business, the unread count, the last day and whether you or they wrote last, never a message), at most forty rows a press; and, when the person presses Add this person in the side panel on a LinkedIn profile they have open, to create the person and the company that profile names (the name, the title and company its headline shows, and the profile address), once for each profile; and, while the side panel is open on a LinkedIn profile or company page, or on any other website, to ask what Belda already has for it (on LinkedIn the page's address, and on a company page its title; on any other website the site's address alone: its scheme and host, never the page within it, its title or its text), once for each address a tab shows, and again when that answer is two minutes old or the person has just added or brought something with the panel, so the panel says New or In Belda; and, while the side panel is open on a LinkedIn message thread, to ask the same for the person that thread's header links to, with LinkedIn's own ids of the messages the thread shows and never their words, so the panel shows what that person last wrote and the reply Belda has drafted for them; and, when the person clicks Send on that drafted reply, to ask Belda to send that one draft, as it is held, into that thread, once; and, when the person opens their own company page's followers list as its admin, and once a day after that in a tab of its own, to hand their own workspace the followers that list shows (the name, the line under it, the company it names, the profile address and the day they followed), down to the newest follower an earlier reading handed over; and, once a day after that reading, to hand their own workspace the people who reacted to or commented on the newest ten posts of that page and of the person's own (the name, the line under it, the company it names, the profile address, the words of a comment and its day), under the post's address and its first line; and, on LinkedIn only, while the person has their own LinkedIn messages open, to hand their own workspace each conversation that tab shows (the profile address of the person they are talking to, the name its header shows, the line under that name, and each message with LinkedIn's own id for it, whether you or they wrote it, its text and its moment), each message once, so it lands in their Inbox; and, on WhatsApp only, while the person has their own WhatsApp Web open, to hand their own workspace the chat that tab has open (the number WhatsApp gives that chat, the name its header shows, and each message with WhatsApp's own id for it, whether you or they wrote it, its text and its moment), each message once, so it lands in their Inbox; and, when the extension itself breaks, to report its own last five errors, each the first line of the error's message with any address or quoted words struck, the file name and the line, never a page's text and never a person's field, so Connections can name the hour the extension itself broke. While nothing is paired, that same error report, the extension's and Chrome's versions, the names of its own stored settings with their kind (never their values) and a random number made for this install go to Belda with no bearer, at most once a minute. The Belda API refuses this bearer anything it was not issued for, and refuses a WhatsApp pairing the LinkedIn one as well.

Belda's own data protection follows the workspace agreement your organization 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 channel 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, and Chrome withdraws the site permissions you gave it. Ask the person who runs your Belda workspace to unpair the channel 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 hussam@belda.ai, or to the person who runs your Belda workspace, who can reach Belda.