Your subscribers gave their address to hear from you
A mailing list is unlike any other document a company holds. It is a file of people who left their address at a particular moment, for a particular reason, in order to hear from your brand. Not one of them agreed to have an artificial intelligence walk through the list.
The Brevo connector draws a consequence you can verify in its code. It holds no function able to read a contact. Brevo's individual-contact surface, the recipients of a list and the events attached to each recipient are not read and then filtered, they are never asked for. This is therefore not a setting anyone could reopen later.
What your Kastel learns from Brevo is what your marketing team built. Which campaigns exist, what they announced, when they went out, which lists live in which folder, and where your open deals stand. A plugged-in AI works on that without ever coming near a subscriber.
The campaign comes in, the subscribers stay in Brevo
On an emailing source, scope is described object by object rather than by category. Here is the list, as it is written in the connector.
Per-recipient events are excluded for a precise reason. That is where what interests each person can be read, campaign after campaign, and a file of that kind describes individual behaviour rather than company activity. A campaign's totals are enough to know what your market cares about.
What each Brevo object leaves in your Kastel
Every row can be checked in your own Brevo account, by opening the object concerned.
| The object in Brevo | What comes into your Kastel |
|---|---|
| An email campaign | Its name, subject, status, type, the sender's name, its scheduled time |
| That campaign's statistics | The totals sent, delivered, unique opens and unique clicks |
| The campaign's HTML content | Nothing |
| A contact list | Its name, its folder, its subscriber count, its blacklisted count |
| A contact on that list | Nothing |
| A sender | Its name, the company sending address, active or not |
| A CRM deal | Its name, its stage, its amount, its pipeline |
| The contacts and companies linked to that deal | Nothing |
The three rows that leave nothing carry the whole subject of this page. Brevo counts a list's blacklisted contacts separately, the ones who no longer receive anything. That number comes into your Kastel; the people behind that number do not.
What the connector knows about opens and clicks
A campaign leaves its totals. How many messages went out, how many were delivered, how many unique opens and unique clicks were counted. Those four numbers come from the global statistics Brevo attaches to the campaign, and nothing else is read at that point.
The list of per-recipient events is never fetched, and that is what separates a statistic from a behavioural profile. Knowing how many opens a campaign collected tells you about the subject your market cares about. Knowing which of your clients opened it, then clicked the pricing link, tells you about her, and that does not come into your Kastel.
The campaign's HTML content stays out by two routes. The connector asks Brevo not to send it, and it drops it at write time anyway, even if the interface returned it regardless. A field Brevo might add to its campaigns tomorrow would not come in either, for want of having been named. A record of an unexpected shape produces a shorter note, never a wider one.
Nobody reads your marketing data until a department is designated
Brevo works with a key that sees the whole account. There is no read permission per campaign, no owner per list, nothing resembling the permission on a shared file that could be inherited. Brevo's sub-accounts are not used in this version of the connector. The key itself is held separately and never appears on a page of your Kastel, in an address or in a log, as the security page sets out.
The connector therefore refuses to broadcast your marketing data to the whole company. It applies a single scope to every record, and that scope only exists when three conditions hold together. A marketing department must have been named, its name must be a valid identifier, and that department must genuinely exist in your organisation.
If any one of the three is missing, everything waits for an administrator's decision and nobody reads anything. A marketing department invented in a configuration file is not enough to open access. This is the mechanism that decides everywhere else who is entitled to read what, and Brevo is no exception. Every source in the connector catalogue arrives with its own reading rule, and this one is the most closed of the marketing set.
What this connector does not do
It sends nothing. It creates no campaign, schedules no send, changes no list, unsubscribes nobody, and there is no write path into your Brevo account. Nor does it compute any rate or compare campaigns with one another, it leaves the totals Brevo attaches to each one exactly as they are. The analysis stays in Brevo, which does it better.
Brevo's CRM comes in through four business fields only, and that has a price. A deal's custom fields are not read, so useful information your team filed there stays out as well. If your pipeline lives elsewhere, the HubSpot page describes a connector that does read a contact's business record openly.
A campaign's name, its subject and a deal's name are free text. If your team writes a client's name or something sensitive there, it comes in with the record, because the connector does not judge what your people type into a title.
A campaign or a list deleted in Brevo is not erased from your Kastel. It stays in your Kastel flagged as gone at the source, its readers unchanged, until an administrator decides to erase it. An unsubscribe, for its part, concerns no line this connector ever wrote, since no contact ever came in. It only moves a count, on the following pass.
Let us talk about your database before you connect anything.
A subscriber file is the kind of subject where a conversation beats a web page. Tell us what you expect an AI to do with your marketing, and we will tell you plainly what Kastel reads and what it leaves out.
Get in touch
