Who we are
In this page, "Belda", "we" and "us" mean Belda Technologies, Inc., a Delaware C corporation, with teams in Dubai and Aarhus, the company behind the product.
If your organization holds a written agreement with us, that agreement decides what we may do with your workspace’s data, and this page describes it in plain words.
Questions about this page, or about your own data, go to hussam@belda.ai.
What we read, and why
Belda reads only what a connection you made gives it, and only to do the work you asked it to do.
Your mailbox. When you connect your work mailbox, the agent writes letters and replies from it, in your name, and watches the inbox for the replies to the threads it wrote in. It keeps those replies, and it reads them to classify the answer, draft your reply and recognize a booking. We ask for the narrowest access that lets it do that, and we say on the connection screen what each permission is for.
Your calendar. The agent reads when you are free or busy so that it never offers a slot you cannot keep, and it creates the meeting on your own calendar, in your own name.
Your CRM, when you bring one. The grant we ask for reads and writes nothing back, not even a field definition. You approve the field map before anything is imported, so the boards that must never enter your workspace are unticked by a person rather than discovered afterwards.
Your meeting recaps, when you connect a notetaker. We read the recap the notetaker you already pay for produces: the summary, the action items and who attended, so that the meeting lands on the right deal and is marked held by evidence rather than by memory. Belda never joins your meeting and never records it.
LinkedIn and WhatsApp, in your own browser. These two steps run in your own signed-in tab through the Belda browser extension. The section on the extension below says exactly what it reads, what it sends and what it stores, and nothing beyond that paragraph is true of it.
The open web. To write a fit reason we read the company's own website, the way anyone can. Every value we write down carries where it came from and the date it was read.
Your workspace's own records. Companies, people, deals, activities, notes and meetings, written by the work as it happens. This includes the contact details of the people your team writes to.
How Belda itself is used. We record errors and how the product is used so that we can fix what breaks and see what works: which screens were opened, which actions ran, and what failed. These records carry the workspace and the seat, not the content of your letters.
What we store, and where
Your workspace lives in one Postgres database in Frankfurt, Germany, inside the European Union, and the application and the job worker that read it run in Frankfurt too. This is not a preference, it is where the machines are. Your data travels encrypted. Every connection between your browser, Belda, the database and the services named on this page uses TLS, and the database in Frankfurt is encrypted at rest.
Every row belongs to a workspace, row-level security is enabled and forced on the database itself, and no route reads across workspaces. The tokens that let the agent reach your mailbox and calendar are sealed before they are written down, with a key that lives only as a server secret. Access by people. No human at Belda reads your workspace’s data unless you ask us to look at something, the law requires it, or we must investigate a security problem. Everyone who works for or with Belda, and any successor to Belda, is bound to this policy and to Google’s User Data Policy, including its Limited Use requirements. If there is a security problem. If we find a security problem that touches your data, we tell your workspace’s owner in writing as soon as we know what happened, what it touched and what we did, and we write it down. Where the problem touches data received through Google APIs, we also tell Google.
The people your team writes to are in your workspace because your organization put them there. Your organization decides what is collected about them and why; we hold it on your instruction.
What we never do
We never sell your data, and we never hand it to a data broker, an advertising platform or an information reseller. We do not advertise, and we do not profile anyone for advertising.
We never train a model on your data. Your letters, replies, records and transcripts are not training material, not ours and not anyone else's.
Nothing leaves that you have not approved. Every letter, every reply and every booking passes one gate first, and the gate writes down what it allowed or refused and which rule decided, before anything happens. A new seat starts at the lowest setting, where nothing leaves without a person’s press: on Microsoft 365 the letter lands in your own Drafts folder, on Google Workspace it waits in Belda for your approval. You raise that setting yourself, one kind of reply at a time, and you can lower it again; anything the agent will not answer alone waits for you with the answer already drafted and the rule that held it. One press stops everything.
Nothing the agent reads on a website or in a reply can make it send an email or book a meeting. The model only drafts; the sending and the booking are done by code that runs the same checks every time, under the setting you chose.
We never read across workspaces. What your team accumulates is your team's.
We never sign in as you anywhere we were not given a connection, and Belda's own servers never open a LinkedIn or WhatsApp page.
We never test with your data. Our tests, previews and demonstrations run on made-up companies and people, never on a customer’s workspace.
Who else handles your data
These are the companies we use to run Belda. Each one does one job, each one gets only what that job needs, and this list changes on this page before it changes in the product.
Microsoft. Your mailbox and calendar, when you connect Microsoft 365. Where the data sits: your organization’s own Microsoft 365 tenant.
Google. Your mailbox and calendar, when you connect a Google account. Where the data sits: your own Google account.
Pipedrive. Your old CRM, read only, when you connect it. Where the data sits: your own Pipedrive account.
Read.ai. The meeting recap, when you connect the notetaker. Where the data sits: Read.ai's own service.
Anthropic. The model service behind the agent's reading and writing.
OpenAI. The fallback model service, used when the first one cannot answer.
Google (Gemini). A model service for reading replies and writing drafts, used when the one asked first cannot answer.
Our other language-model providers (the current list is available on request at hussam@belda.ai). The model service asked first for translating, sorting and summarizing, including the text of your mail. Where the data sits: not every one of these providers states where its API processes or keeps requests.
Supabase. The Postgres database that holds your workspace. Where the data sits: Frankfurt, Germany (eu-central-1).
Fly.io. The servers that run the application and its jobs. Where the data sits: Frankfurt (fra).
Sentry. Error reports from the application, so we can fix what breaks. Where the data sits: Sentry's European region.
PostHog. Product and website analytics. Where the data sits: PostHog's European cloud.
Framer. This website, belda.ai. Where the data sits: Framer's own hosting.
Vercel. Preview environments for changes, never with customer data.
Some services are in our accounts but are not in use today, and this page changes before they are: an email verification service, an SMS provider, a person data provider and the service that sends Belda’s own account emails.
How long we keep it
Your workspace’s data stays while your workspace does. When your organization ends its agreement, you can take your data out first: every export carries the source and the date of every value we enriched. After that we delete it.
You can disconnect any connection at any time, in the product, and the agent stops reading it at once. Removing the browser extension removes everything it stored in that browser.
Your data
Your data: manage, export, delete. Disconnect a mailbox or calendar in Settings, Connections; the agent stops at once, and the connection’s tokens are deleted. Export your records as CSV from any list header in the product; every value carries its source and date. Delete a person or a company from its record; delete a workspace by writing to hussam@belda.ai from the workspace’s own domain, and we confirm the deletion in writing. Ask for a copy, a correction or a deletion of your own personal data at hussam@belda.ai.
Your rights
If you are in the European Union or the United Kingdom, the law gives you rights over your own personal data, and we mean to honor them wherever you are: to know what we hold about you and to get a copy of it; to have what is wrong corrected; to have it deleted; to take it with you in a form another service can read; to object to a use, or ask us to restrict one; and to complain to your country’s data protection authority.
Ask by writing to hussam@belda.ai. Where the data is in your organization’s workspace, your organization decides it and we will pass your request on and help them answer it.
Google user data, and the Limited Use requirements
When you connect a Google account, Belda asks Google for what the work needs and uses it only for that: your name and address (openid, email, profile); permission to send the emails you approve from your mailbox (gmail.send); permission to save your own reply in your Gmail Drafts when sending is paused or you want to finish it in Gmail, never sent until you press Send (gmail.compose); permission to read your mail, so that replies to your emails appear in your Belda inbox and Belda can draft an answer for you to approve (gmail.readonly); when you are free or busy (calendar.freebusy), permission to create and cancel the meetings people book with you on your calendar and to read your own events on it (calendar.events), and your Google Contacts, so the people you already know show as known (contacts.readonly); and, only if you turn them on, the list of your calendars, so you choose which ones count as busy (calendar.calendarlist.readonly), the notes Google Meet saves for your meetings (drive.meet.readonly), the Drive documents you point Belda at (drive.readonly), and the Sheets you export to, which are only the files Belda creates (drive.file). Belda never deletes, labels or changes your mail. The letters sent from this mailbox and the replies to them are part of your workspace’s record. A mailbox starts private: your teammates see only who you wrote to and when, until you share a conversation or the whole mailbox. You can delete what Belda read from a mailbox at any time, in Settings or when you disconnect it. What it does with that data is exactly what this page says: it drafts, it answers, it books, and it shows you each one before it happens. To read, translate, summarize and answer that mail, Belda sends the text a task needs to one of the model services named under “Who else handles your data” (Anthropic, OpenAI, Google Gemini and our other language-model providers; the current list is available on request at hussam@belda.ai), only to get that task’s answer. Google data is stored in the same Frankfurt database as everything else in your workspace, is never sold and is never used to train a model. When you disconnect the account we stop reading it, and it is deleted when your workspace closes or when you ask us to delete it. No human at Belda reads it, unless you ask us to look at something, the law requires it, or we must investigate a security problem.
The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.
Belda’s use of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.
Belda does not use Google Workspace user data to develop, improve or train generalized AI or ML models.
The Belda browser extension
Two steps of the work happen on sites that have no API for it: 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.
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, and it has no permission for any site other than LinkedIn, WhatsApp Web, the Belda web app and the Belda API.
The extension asks Belda for the next action, performs it, and reports the outcome: the action’s own identifier, the outcome word, 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. It sends no profile field, no message you received, no thread, no phone number, no contact list and no page content. In this browser it keeps one pairing key per channel, 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, and nothing else: no LinkedIn or WhatsApp password, session cookie or QR code, no profile fields, messages, threads or phone numbers, and no analytics, advertising identifiers or tracking of your browsing.
Stop in the extension halts that channel in this browser at once. Stop in Belda halts it on the server too. Removing the extension from Chrome removes everything it stored in this browser.
When this page changes
We change this page when the product changes, and the date at the top says when it last changed. If a change matters to you, we tell you in the product before it takes effect rather than leaving you to find it.
Contact
hussam@belda.ai
Belda is the Autonomous Revenue Operating System. It does the selling, and you say yes.
Belda Technologies, Inc., Dubai and Aarhus