Brida

BRIDA TERMS OF SERVICE

Terms of Service

In force from 6 November 2026. They bind each Customer from its owner's acceptance (clause 4). The hosted Brida Reflex preview keeps its own terms at /reflex/terms.

Version 1 (customer_terms@1), in English · In force from 6 November 2026 · SHA-256 digest of the text: c030958aaee7b6971d3f7e566da7298cf0fb83b36d061c9de919525acfd93b2a · Versión en español (prevalece)

THE ESSENTIALS

This summary is part of the Terms so that you see what matters most before you accept. If anything in this summary differs from a clause, the clause applies.

  • Brida is a service for businesses and professionals only, not for consumers.
  • The Customer is the controller of its contacts' data and the sender of every message. Brida is its processor, under the DPA.
  • Until the owner has accepted a version of these Terms that is in force, Brida accepts no Attestation, sends nothing, accepts no payment and charges nothing in the Organization (clause 4.4).
  • These Terms are in force from 6 November 2026 and bind each Customer from its owner's acceptance. Until they can be accepted on Brida's pages, the owner accepts them in writing (clause 4). The DPA, by contrast, is accepted only on Brida's pages, and Brida processes no personal data on the Customer's behalf until its owner accepts it there (clause 4.1). Features not offered yet, such as the attestation or the purchase of credits, apply from when Brida offers them (clause 5.8).
  • Before anyone is contacted, a person of the Customer attests the legal basis for each base or segment, channel, use case and market. The Customer warrants that it is true and answers to Brida if it is not, including, without limit, for the proven damage that spam or a false attestation causes Brida (clauses 7, 21.9 and 22).
  • Brida blocks, on the data recorded in the Service, contacts without an attestation, content in which its filter detects health data, contacts with a recorded opt-out or objection, and attestations incompatible with the source the Customer declared for the base. In addition, every message carries the unsubscribe, WhatsApp requires an opt-in record, there are caps and a stop button, and a person approves every batch or envelope. Everything else, Brida only warns about. Only if an instruction is manifestly unlawful may Brida hold it, explaining why, until the Customer corrects or withdraws it (clause 8).
  • Once Brida starts charging (clause 12.11), the Service is paid with prepaid credits in euros, under the Price List in Annex B. Purchased credits expire after 12 months. When the contract ends, Brida refunds the unused ones, less whatever the Customer owes it (clause 12.6).
  • An Opportunity is charged automatically if nobody disputes it within the period that starts when its email notice arrives. A person at Brida resolves each dispute within 10 Business Days; otherwise the Customer wins (clause 11).
  • WhatsApp messaging is charged at cost, with no margin.
  • There is no lock-in: the Customer can leave whenever it wants, take its data and get back its unused purchased credits (clauses 12.6 and 18 and Annex C).
  • Brida may suspend a funnel, a connection or the Organization on the grounds of clause 17, and says why.
  • Estonian law governs and the courts of Tallinn decide (clause 25). If the Spanish and English versions differ, the Spanish one prevails.

PARTIES

a) Brida OÜ, a company of Estonia with registry code 17445507, VAT number EE102958610 and registered office at Harju maakond, Tallinn, Kesklinna linnaosa, Tornimäe tn 5, 10145 ("Brida").

b) The entity recorded in the acceptance evidence of these Terms, with its legal name, its country and its tax or registry identifier ("the Customer"), represented by the signatory recorded in that evidence, who declares that they can bind it.

Each is a "Party".

Clause 1. Definitions

In these Terms:

  • "Service": the Brida service, with which the Customer designs, approves and runs campaigns and funnels to win and win back customers, from Brida's pages and from an artificial intelligence (AI) client that it connects to Brida through the MCP protocol.
  • "Organization": the Customer's account in Brida. "Owner" is the person with the owner role in that account.
  • "Authorised Person": the owner, an administrator or another person to whom the Customer gives access to its Organization and, if the Customer grants it, a person of its Agency with an active delegation to approve.
  • "Channel": the mailbox, the WhatsApp Business number or another means of communication of the Customer's own that the Customer connects to the Service.
  • "Channel Provider": whoever provides a Channel to the Customer and with whom the Customer holds the account in its own name, such as Google, Microsoft, its email provider or Meta (WhatsApp Business). The BSP is not a Channel Provider.
  • "BSP": the WhatsApp Business solution provider that Brida contracts and pays to provide the Service's WhatsApp messaging. It is Brida's supplier and subprocessor (clause 15.2).
  • "Platform Terms": the terms and policies that the Customer accepts with each Channel Provider and the published usage policies of Brida's AI providers that Annex A links, in the version in force when each conduct occurs. Brida notifies the Customer of the material changes it knows of.
  • "Contacts": the people the Customer wants to write to with the Service.
  • "Customer Data": the personal data processed in the Organization, as the DPA defines it.
  • "Customer Content": what the Customer provides to the Service or approves in it: contact bases, offers, prices, claims, texts, templates and messages.
  • "Outputs": the drafts, classifications, proposals and other results that the Service's AI models generate for the Customer.
  • "Funnel": a campaign of the Organization, with its audience, its steps, its goal, its caps and its pricing mode. "Approved Version" is the version of a Funnel that an Authorised Person approves.
  • "Attestation": the declaration of the legal basis in clause 7.
  • "DPA": the data processing agreement under Article 28 of the GDPR that the Customer accepts on Brida's pages, in the version in force for its Organization.
  • "GDPR": Regulation (EU) 2016/679.
  • "Marketing Laws": the data protection, commercial communications, consumer protection and advertising rules of each market to which the Customer sends messages.
  • "Credits": the Customer's prepaid balance in euros (clause 12).
  • "Price List": the one in Annex B.
  • "Quote": the summary of mode, band, prices, caps and estimate that Brida shows when a Version is approved (clause 10.6).
  • "Active Contact" and "Opportunity": as defined in clauses 10.3 and 10.4.
  • "Agency": a company that works for the Customer in Brida with a delegation from the Customer.
  • "Business Days": working days in Estonia.

Clause 2. Purpose and contract documents

2.1. These Terms govern Brida's provision of the Service to the Customer. They are the "Contract" referred to in clause 1.2 of the DPA.

2.2. Besides these Terms and their annexes (A, Acceptable Use Policy; B, Price List; C, Data export and switching), the DPA and the Quote of each Approved Version form part of the contract.

2.3. If they conflict, this order applies: the DPA, as regards personal data; Annex C, as regards data export and switching; the Quote of an Approved Version, as regards that Version's prices, band and caps; these Terms; and their other annexes. The grounds and periods for suspension and termination are those of these Terms, and Brida also respects them when it applies clauses 11.1 and 15.4 of the DPA.

2.4. Brida's privacy notice (https://www.brida.ai/privacy) explains how Brida, as controller, processes the data of accounts and of the people who use the Service. It is information, not a clause of this contract.

2.5. The Customer's general terms, such as those of its purchase orders, do not apply unless Brida accepts them in writing.

Clause 3. Businesses only

3.1. The Service is for businesses and professionals only. The Customer declares that it contracts for its business or professional activity and not as a consumer.

3.2. The signatory declares that they can bind the Customer. The people who use the Service are at least 18 years old.

3.3. The Customer gives its legal name, its country and its business tax or registry identifier: in Mexico, its RFC; in the European Union, also its VAT number, if it has one. Brida may verify them, and checks the VAT number in the VIES system. Clause 13.2 says how that number affects the invoice.

3.4. Sanctions. The Customer declares that neither it, nor whoever controls it, nor the people who use its Organization: are on a sanctions list of the European Union, the United Nations, the United Kingdom or the United States, or are 50 % or more owned by, or controlled by, anyone who is; or are established in a territory subject to comprehensive sanctions. The Customer does not use the Service for the Government of Russia or for entities established in Russia or in Belarus. Brida may suspend the Service at once if it has reasonable grounds to believe this clause is breached.

Clause 4. How the contract is made

4.1. Until Brida's pages allow these Terms to be accepted, the owner accepts them in writing, before the Organization's first Attestation, first send or first payment: with an email to hi@brida.ai from their owner address, or with a document they sign, which names this version (customer_terms@1) and its language and gives the Customer's legal name, country and tax or registry identifier and their own name as signatory. Acceptance in writing applies only to these Terms, not to the DPA: the owner accepts the DPA only on Brida's pages (clause 17.1 of the DPA), and Brida processes no Customer Data until the owner has accepted it there. When Brida offers acceptance on its pages (clause 5.8), the owner accepts there, in a session with two-factor authentication and with a verification of their passkey bound to this version, its language, its exact text, the entity and the signatory. No machine credential (an API key, an OAuth token or an MCP client) and no person of an Agency on behalf of a client accepts them.

4.2. Before acceptance, the owner can read, save and print the full text, in Spanish at https://www.brida.ai/es/terms and in English at https://www.brida.ai/terms. They review the entity and the signatory and can correct them before accepting. These Terms exist in Spanish and in English.

4.3. Brida stores the evidence of the acceptance, with the version and language accepted, and confirms it to the owner by email without undue delay. The text of each version is immutable and remains available: the owner can request it at hi@brida.ai at any time.

4.4. The contract is made when the owner's acceptance reaches Brida. Until the owner has accepted a version of these Terms that is in force, Brida accepts no Attestation, sends no message, accepts no payment and grants no Credits, and charges nothing in the Organization. This applies in every Organization of the Customer in which Brida is a processor, whoever pays, including where an Agency pays for it in the mode of clause 14.3.

4.5. Each version of these Terms, in each language, is immutable and has an identifier. This one is customer_terms@1, in force from 6 November 2026. It binds each Customer from its owner's acceptance.

4.6. If the Customer wants to negotiate a clause, it can write to hi@brida.ai before accepting. What the Parties agree in writing and sign prevails over these Terms.

Clause 5. The Service

5.1. With the Service, the Customer designs Funnels by talking to its AI client connected to Brida through MCP, such as Claude, or on Brida's pages. Brida's AI agents draft the messages, read and classify the replies and move Contacts through the Funnel's steps. Messages go out through the Customer's own Channels and in its name. Every step is visible to the Customer, with a record of what was done, why and with which version.

5.2. Channels. The Service supports the Channels that Brida's pages show as available, among them the Customer's mailbox (for example, from Google or Microsoft, or over IMAP and SMTP) and, when Brida offers it, its WhatsApp Business number, with the messaging of Brida's BSP. Brida gives notice when it adds a Channel.

5.3. The Channels belong to the Customer. The Customer holds each account in its own name with its Channel Provider, including its WhatsApp Business account with Meta, although the charges for WhatsApp conversations are billed to Brida through its BSP (clause 10.8). It connects each Channel with a provider link, with OAuth or with Brida's credentials form, never through the chat. Brida stores only opaque references to its credentials.

5.4. The Service does not include: choosing whom the Customer writes to or why; sending messages in Brida's name; legal advice; sending through bulk email delivery providers; unofficial WhatsApp automation; LinkedIn automation; or outbound calls with an AI voice.

5.5. The Customer's AI client, such as Claude, is a service of the Customer, with its own provider and its own terms. What the Customer types into it is processed by that provider, not by Brida, and the DPA does not cover it. The Customer does not paste contact lists or other personal data into the chat: it imports them with Brida's import.

5.6. Beta features. Brida may offer features marked as beta. They are offered as they are, may change or be withdrawn, and the Customer decides whether to use them. The "value" mode has no price in this version: pricing it is a new version of these Terms (clause 19.2).

5.7. Brida may improve and change the Service under clause 19. It never withdraws the controls of clause 8 without a new version of these Terms.

5.8. Features not offered yet. Some features these Terms describe are not available yet, such as acceptance on Brida's pages; the Attestation of clause 7, with the blocks of clause 8.1 a) (i) and (iv), which depend on it; the purchase of Credits and its automatic recharge; the usage statement; the email notice of each Opportunity and the tracking of its bounces; and connecting a WhatsApp number. Each applies from when Brida offers it in the Service, and Brida notifies the owner when it does. While one is not available, Brida charges nothing that depends on it, and the Customer exercises in writing, at hi@brida.ai, the rights these Terms give it without it, such as those of Annex C. While the Attestation is not available, the Service writes to no Contact of the Customer (clause 7.1).

Clause 6. Role of each Party and use of data

6.1. The Customer is the controller of the Customer Data, the advertiser and the sender of every message. Brida is its processor, under the DPA.

6.2. Brida processes the data of accounts and of the people who use the Service as controller, under its privacy notice.

6.3. The Approved Version of each Funnel, with the Attestations that cover its audience, is the Customer's documented instruction (clause 4 of the DPA). Brida writes to no one outside the audience of an Approved Version and for no other purpose.

6.4. Brida does not use Customer Data, Customer Content or Outputs for its own purposes, to serve other customers or to train or improve AI models. Its model providers do not use them for training, under their terms or what Brida asks of them in each request (Annex I of the DPA).

6.5. Brida may compute aggregate Service metrics (counts, costs, rates and times), without personal data or Customer Content, to operate, protect and bill the Service. It does not publish them in a way that identifies the Customer without its permission.

6.6. An Agency accesses the Organization only with the delegation the owner grants it, and loses it when the Customer revokes it (clause 14).

Clause 7. The legal basis: what the Customer attests and warrants

7.1. Before the Service writes to a Contact, a person of the Customer (the owner or an administrator, never an Agency) attests on Brida's pages, for each base or segment, channel, use case and market:

  • the legal basis, from this list: consent; existing customer with a prior contract and similar products or services; legitimate interest; or performance of a contract, with a reference to its own documentation;
  • that the information the law requires to be given to recipients (for example, that of Articles 13 and 14 of the GDPR or the privacy notice under Mexican law) is its own and has been given;
  • if the basis is consent, that it holds proof of each consent;
  • that it has read Brida's warning for that market and channel.

7.2. Each Attestation is valid for 12 months unless the Customer withdraws it earlier. It is both a representation and warranty of the Customer and its documented instruction to Brida. Each Approved Version is bound to the Attestations that cover its audience.

7.3. The Customer warrants, when it attests and while it uses each Attestation, that:

a) it is the controller of the data, or acts with the controller's authorisation;

b) each base has the lawful source it declares, and the Attestation matches that source;

c) if it attests "existing customer with a prior contract", the Contact is its customer, the message offers its own products or services similar to those the Contact bought and, where the law requires it (for example, in Spain), it offered the Contact the chance to opt out when collecting the data;

d) it has checked the advertising exclusion systems that the law of each market requires (for example, the Robinson List in Spain or the REPEP in Mexico) and has excluded whoever is on them;

e) it has imported into Brida every opt-out, objection and suppression it knows of, and does not ask Brida to write to those people;

f) the bases contain no health data, other special categories of data, patient data or data of minors;

g) on WhatsApp, each Contact gave their number to the Customer itself and agreed to receive its messages with an opt-in that names the Customer, not the Agency or Brida, and it never uses on WhatsApp numbers that are bought, provided by third parties, enriched or scraped from the web;

h) its offers, prices and claims are true and lawful, and the offer price of each Approved Version is the price it really charges;

i) it may use the mailboxes, domains and numbers it connects;

j) the people who attest and approve on its behalf are authorised to do so.

7.4. The Customer complies with the Marketing Laws of each market to which it sends messages, including the information they require in each message (for example, in Mexico, the details of Article 17 of the Federal Consumer Protection Law when the recipient is a consumer), and with the Platform Terms.

7.5. The Customer keeps the evidence of each Attestation (consents, privacy notices, legitimate interest assessments and checks of the exclusion systems) and gives it to Brida within 10 Business Days if Brida, a Channel Provider or an authority asks for it.

7.6. If an Attestation stops being true, the Customer corrects or withdraws it at once. Brida may rely on each Attestation and on the data the Customer records (the source of each base, the relationship with each Contact, the opt-outs it imports and the opt-ins it attests) without checking them.

7.7. Brida's warnings are not legal advice. When the attested basis does not fit what Brida knows about a market and a channel, the page warns before signing, and the Attestation keeps the warning. In this way Brida informs the Customer of an instruction that, in its opinion, may infringe the law (Article 28.3 of the GDPR and clause 4.4 of the DPA); this does not limit its duty to inform the Customer again if it later considers so. Going ahead is a decision of the Customer, which is the controller. Brida does not certify that a send is lawful, and its controls do not ensure that the Customer complies with the Platform Terms.

Clause 8. What Brida blocks, what it warns about and what it always does

8.1. Brida blocks, with or without an Attestation, with deterministic checks on the data recorded in the Service:

a) the four manifest cases: (i) a Contact not covered by any Attestation in force; (ii) a reply or other inbound content in which Brida's health filter detects health data, which it moves to a quarantine for human review and never uses for drafting; (iii) a Contact with an opt-out, objection or suppression recorded on any channel of the Organization; and (iv) an Attestation incompatible with the source the Customer declared for the base, such as "existing customer with a prior contract" or "performance of a contract" on contacts that the Customer declared to have no prior relationship or to come from a third-party list;

b) a message without the unsubscribe: every message carries a fixed block with a one-click unsubscribe link or, on WhatsApp, the option to reply with an opt-out word, such as BAJA or STOP, in the language of the message;

c) a WhatsApp message started by the Customer without a record of each Contact's opt-in, attested by the Customer or captured by the Service, or without a template approved by Meta;

d) whatever exceeds the caps: on spend and on outcomes, per channel and day, the sending ramp and the contacts per person and month;

e) whatever the stop button stops: globally, per Organization or per connection;

f) a send without the human approval of clause 9.

Brida does not analyse the bases the Customer imports to find out whether they contain patients or health data, and cannot know it: that they do not contain them is warranted by the Customer alone (clause 7.3 f)). Health data in a Customer's base that the filter does not detect is not a failure of this clause, nor is an opt-out, an objection, a source or an opt-in that is not recorded in the Service.

8.2. In addition, these Service rules remain, which do not decide the legal basis: the AI notice in the first message (clause 8.5); the rules that protect the Channels, such as quiet hours or that cold email does not go out from the Customer's main domain; which Channel supports each use case; and the checks on every send (current authorisation, the fingerprint of the approved content, the control group, idempotency and the receipt).

8.3. The blocks are instructions that Brida does not carry out. Brida does not breach these Terms or the DPA by not carrying them out, and it may hold an affected instruction until the Customer corrects or withdraws it.

8.4. Everything else is a warning that the Customer sees and signs (clause 7.7). A doubtful case is only warned about, and a warning, by itself, does not make Brida block or suspend. Only when Brida considers an instruction manifestly unlawful (Article 28.3 of the GDPR) may a person at Brida hold it without breaching these Terms: they explain to the Customer in writing why, and the instruction stays held until the Customer corrects or withdraws it, or until Brida, with what the Customer provides, no longer considers it manifestly unlawful. Faced with a complaint from a data subject or a request from an authority, a person at Brida may use the suspension of clause 17.

8.5. The fixed block of every message identifies the Customer as the sender and carries the unsubscribe. In the first message of each conversation on each channel, it also states that the message was written by an AI assistant acting on the Customer's behalf. Marking Outputs as AI-generated in a machine-readable format is a duty of Brida as the provider of the AI system (Article 50 of Regulation (EU) 2024/1689, the AI Act), not of the Customer. Brida applies that marking when it is available in the Service, to the extent technically feasible.

8.6. The Customer does not remove, hide, change or contradict the fixed block, the unsubscribe, the AI notice or those marks. It does not present a message drafted with AI as written by a person, nor say that a person is present when none is.

8.7. Brida may apply in an Organization market or sender rules stricter than those of this clause where the Parties agree so in writing or in a pilot. Those rules are blocks too (clause 8.3).

Clause 9. Human approval and review of Outputs

9.1. No message goes out without the approval of an Authorised Person on Brida's pages, with a verification of their passkey bound to what they approve: each batch or, where the Service and the DPA in force allow it, an envelope of sends with its limits. Cold email to businesses is approved batch by batch. When sending, Brida checks that the content is the approved content.

9.2. Outputs may be inaccurate, incomplete or unsuitable. Their factual assertions should not be relied on without checking them. The Customer reviews each batch, version or envelope before approving it.

9.3. The Customer is responsible for the Customer Content and for what it approves. Brida is responsible for sending exactly what was approved and for its controls working as clause 20.1 says.

9.4. In automated conversations, the Customer keeps a quick and clear way for the Contact to talk to a person, and attends to the Service's attention queue.

Clause 10. Prices and metering

10.1. Prices are those in the Price List (Annex B): a single list in euros, the same in every country, excluding taxes.

10.2. Modes. Each Approved Version chooses one:

  • "outcome": a floor per Active Contact per month, plus a price for each Opportunity according to the offer's band;
  • "usage": a price per Active Contact per month, in tiers.

The "value" mode remains in beta. If a new Version changes the mode in the middle of a month, each Contact is charged, in each Funnel and month, under the mode of the Version that made its first delivery to them that month.

10.3. Active Contact. It is a Contact to whom an Approved Version delivered at least one message in a calendar month, in UTC. It counts once per Contact, Funnel and month, in the month of delivery. Contacts that the Service blocks, hard bounces, undelivered WhatsApp messages and Contacts in the control group do not count. On WhatsApp, a message is delivered at the first delivered or read status that Meta reports. On email, at the sending server's acceptance without a permanent failure notice in the following 72 hours; if the Channel does not give that signal, acceptance counts, and the statement says so.

10.4. Opportunity. It is a reply from a Contact, within the 30 days after the last message the Funnel sent them, in which they ask for a price or availability, ask to buy or book, or book a meeting. A meeting only counts with the signed confirmation of the calendar tool the Customer connects or with the confirmation of a person of the Customer. There is at most one Opportunity per Contact and Funnel, across all its versions. An unsubscribe, a "not now", an automatic reply, a complaint, a support or billing query, or the reply of a Contact in the control group is never an Opportunity. Each Opportunity carries its evidence in view: the message received and its classification, with the classifier's version. It is only charged in the "outcome" mode.

10.5. Band. The price of each Opportunity depends on the band of the offer that the Approved Version names, according to its price: under €100; from €100 to under €1,000; or €1,000 or more. The band is fixed when the Version is approved and does not change while it lasts. An offer in another currency is converted into euros at the latest European Central Bank reference rate published at the moment of approval. A subscription uses the value of its first year, and a free entry offer, that of the paid offer that follows it. Brida checks by sampling that the messages state that price. A discrepancy is only corrected in the Customer's favour, with a compensating entry and never by recalculating a settled charge, and a new band only applies through a new Approved Version. If the offer price the Customer declared was not true, Brida may claim under clauses 7.3 h) and 21.

10.6. Quote and caps. Before a Version is approved, Brida shows its Quote: the mode, the band, the prices, an estimated cost range, the work cap and the outcome cap. The Authorised Person approves them with the Version. Outcome charges never exceed the outcome cap or leave the balance negative: what does not fit is not charged, and the Funnel pauses so that the Customer can decide.

10.7. Reservation. Before each batch, Brida reserves its estimated cost against the cap and the balance, and afterwards settles what it really costs. Without balance or with the cap reached, the Service stops before drafting or sending.

10.8. WhatsApp messaging. WhatsApp messaging is part of the Service: Brida buys it in its own name from its BSP and charges it to the Customer at its cost, which is the fee Meta applies to each message, with no margin and no currency conversion surcharge. It is charged on the delivery Meta charges for, and is not charged if the message fails or is not delivered within 72 hours. A fee in dollars is converted into euros at the latest European Central Bank reference rate published at the moment of that delivery. Meta sets and changes its fees, and Brida applies those in force.

10.9. Connected WhatsApp number: the monthly price in Annex B.

10.10. Statement. When Brida offers it (clause 5.8), it provides a usage statement per Organization and month, broken down by Funnel. The month closes 72 hours after it ends, and anything arriving later goes to the next month. A settled charge is never modified: every correction is a new compensating entry.

Clause 11. Opportunities: notice, dispute and charge

11.1. Notice. When an Opportunity is created, Brida shows it with its evidence on Brida's pages and sends an email to the owners and to the person who approved the Version. The email only states the band, the amount and the date on which it will be charged if nobody disputes it, with a link to the page that shows the evidence; it does not carry the Contact's message.

11.2. Dispute. A person of the Customer can mark it on Brida's pages as "not an Opportunity" during the dispute period, which ends 7 days after the notice of clause 11.1 arrives (clause 27.2) or 5 Business Days after it, whichever is later. While it is disputed, it is not charged. Disputing is an act of a person of the Customer; an Agency cannot dispute on its behalf.

11.3. Tacit charge. If nobody disputes it within that period, the Opportunity is confirmed when the period closes and is charged automatically. There is no tacit confirmation while the notice has not arrived (clause 27.2): the Opportunity is only confirmed when a notice arrives and its period ends, or when a person of the Customer confirms it. The Customer can confirm it earlier. Nor is there tacit confirmation while the Organization is suspended, for any reason, or after the contract ends: when the Organization is suspended or the contract ends, the Opportunities not yet confirmed are voided and not charged.

11.4. Review. A person at Brida reviews each dispute against the evidence, the definition in clause 10.4 and whatever the Customer provides, and resolves it in writing, with its reason, within 10 Business Days. If it does not resolve it within that period, the dispute is resolved in the Customer's favour. If it is resolved in the Customer's favour, the Opportunity is voided and not charged; if not, it is confirmed and charged. If the Customer disagrees with the resolution, it can make a claim under clause 25.

11.5. Billing errors. During the 60 days after a charge, the Customer can ask for a manifest error to be corrected, such as an Opportunity that does not meet the definition in clause 10.4, a duplicate charge or a wrongly applied band. Brida corrects it with a compensating entry in Credits.

Clause 12. Credits, payments and refunds

12.1. Prepayment. The Service is paid with Credits in euros that a person of the Customer buys in advance by card, through Brida's payment processor (Stripe), from when Brida offers that purchase on its pages (clause 5.8). Brida gives no credit: without balance, work stops, except before charging starts (clause 12.11). When Brida offers it, a person of the Customer can turn on an automatic recharge on Brida's pages: when the balance of purchased Credits falls below the threshold it chooses, Brida charges the amount it chose to the card it saved for that purpose and notifies each recharge by email. The recharge can be turned off at any time on Brida's pages.

12.2. What they are. Credits are an advance payment for Brida's services. They are not money, electronic money, a deposit or a payment instrument. They bear no interest and have no cash value. They only pay Brida's charges, including WhatsApp messaging, which Brida charges at its cost (clause 10.8). They cannot be transferred or exchanged, except for the use of an Agency's balance for its clients in the mode of clause 14.3.

12.3. Classes. There are purchased Credits and promotional Credits: welcome Credits (clause 12.7) and guarantee Credits (clause 12.8). Promotional Credits are spent before purchased ones, and never pay WhatsApp messaging or other provider costs. Among purchased Credits, those that expire first are spent first.

12.4. Expiry. Purchased Credits expire 12 months after their purchase. Brida gives notice by email 30 days and 7 days before and shows on its pages when each purchase expires; the expiry does not depend on the notice arriving. The expiry is extended by the length of a suspension not caused by the Customer or of a stop of chargeable work because the owner has not accepted a new version (clause 19.3). The expired balance is removed with an expiry entry.

12.5. Credits are worth euros. If the Price List goes up, Credits buy less service; that is why the Customer can terminate with a refund under clauses 12.6 and 19.

12.6. Refunds. Brida refunds to the original payment method, within 30 days, the purchased Credits that have not been used and have not expired:

a) when the contract ends, for any reason and whoever ends it, including to switch provider or after a request under Annex C, less whatever the Customer owes Brida and, if Brida terminates for a breach by the Customer, the damage that the Customer acknowledges or that a final decision sets. Until then, Brida may withhold at most the amount of the damage it has claimed from the Customer in writing, and refunds it if it does not start court proceedings for that damage, under clause 25, within the 60 days after that claim;

b) when Brida stops providing the Service in the Customer's country (clause 15.3);

c) when there is a billing error; or

d) when the law requires it.

While the contract lasts, the balance is not refunded outside these cases, and an expired balance is never refunded. Promotional Credits are never refunded.

12.7. Welcome Credits. Brida may give €50 in welcome Credits, once per Organization, after a short application with the country, the size of the base, the sector and the legal basis for contacting it, which is information to review the application and not an Attestation. They are only granted to an Organization whose owner has accepted these Terms (clause 4.4). A person at Brida reviews the application and decides. They expire 90 days after they are granted, have no cash value, and Brida may withdraw them if it detects abuse, such as opening several Organizations to obtain them. They go to the Organization that pays and, in the mode of clause 14.3, only to the Agency.

12.8. First-campaign guarantee. If an Organization's first Funnel in the "outcome" mode gets no Opportunity, Brida returns, as promotional Credits, the entire floor settled in that Funnel:

  • it is assessed when the Funnel is archived or 60 days after its first delivered message, whichever comes first, and after its open disputes are resolved;
  • Opportunities that meet clause 10.4, with their evidence, confirmed or pending, charged or not, count, and voided ones and those a dispute resolves in the Customer's favour do not;
  • the returned Credits expire after 90 days and do not pay WhatsApp messaging, and they go back to whoever paid the floor: the Customer or, in the mode of clause 14.3, the Agency, for the wholesale amount it paid;
  • it is the only remedy under this guarantee, and it does not return Opportunity charges, WhatsApp messaging or the connected number.

12.9. Payments. Stripe processes payments on Brida's behalf, and Brida does not store card details. If the Customer disputes with its bank a payment for Credits it has already used, Brida may suspend the Service until it is resolved.

12.10. Invoices. Brida issues electronic invoices in euros for each purchase of Credits, with the particulars the law requires, and makes each month's usage statement available once it offers it (clause 10.10). The Customer agrees to receive invoices by electronic means. A Customer in Mexico receives an invoice from Brida as a foreign company, not a CFDI, unless Brida registers in Mexico (clause 13.3).

12.11. Before charging starts. Brida may provide the Service in the Organization without charging for it until the date on which it starts charging, which it notifies to the owner by email at least 14 days in advance. Until that date, Brida advances the costs up to a spending limit that it sets and that bounds the Customer's caps, shows the prices of these Terms without charging them and deducts no Credits; chargeable work stops when there is no limit or it is used up, not for lack of balance.

Clause 13. Taxes

13.1. Prices exclude VAT and other taxes. The Customer pays them on top of the price, except Brida's income taxes.

13.2. If the Customer is established in the European Union, outside Estonia, and gives a VAT number valid in VIES, the reverse charge applies: the invoice carries no VAT, carries its number and the mention "reverse charge", and the Customer accounts for the VAT in its country. If it is in Estonia, Brida charges it Estonian VAT. If it does not give a VAT number valid in VIES, Brida treats the purchase as made by a person who is not a taxable person for VAT and charges the VAT the law requires, or refuses the purchase.

13.3. If the Customer is outside the European Union, for example in Mexico, Brida does not charge it Estonian VAT, and the Customer accounts for the taxes its country applies to services received from abroad. If Brida registers in the Customer's country to collect a local tax, such as Mexican VAT, it gives notice beforehand and adds it separately on the invoice.

13.4. If the law requires the Customer to withhold a tax on a payment to Brida, the Customer pays in addition whatever is needed for Brida to receive the full amount, unless Brida can recover that withholding. Brida provides its tax residence certificate if asked.

13.5. WhatsApp messaging forms part of the price of the Service for tax purposes.

Clause 14. Agencies

14.1. A client invited by an Agency contracts directly with Brida: it accepts the DPA and these Terms before its first Attestation or its first send, including in the mode of clause 14.3. The Agency works in its Organization with the delegation the owner grants it, to configure and, if the Customer grants it, to approve. The Customer revokes it whenever it wants, with immediate effect. These are never delegated: accepting or terminating the DPA or these Terms, granting or revoking delegations, closing the relationship, connecting Channels or entering their credentials, attesting the legal basis, confirming Opportunities or sales, or disputing Opportunities.

14.2. Default mode: Brida bills the Customer. The Customer pays from its own Credits, at list price, like any direct customer. The Agency of its delegation is its registered agency, and Brida pays it, under its contract with the Agency, 40 % of Brida's charges that the Customer pays with purchased Credits, not counting WhatsApp messaging, other provider costs or the connected number. That does not change the Customer's price or rights.

14.3. Alternative mode: the Agency resells. The Agency buys Credits at wholesale price (the list with a 40 % discount), the Customer consumes from the Agency's balance within the caps the Agency sets, and the Agency charges the Customer whatever they agree, outside Brida. Brida only offers this mode when the Agency has accepted, for its own Organization, agency terms that bind it, for the client Organizations it pays for, to clauses 10 to 13 and that govern their welcome and guarantee Credits. In this mode, those clauses apply between Brida and the Agency, not to the Customer; the Agency also receives the notice of clause 11.1, and a dispute by the Customer also applies against the Agency's balance. Everything else in these Terms, including clauses 7 and 22, binds the Customer towards Brida.

14.4. The mode is part of the delegation the Customer grants, and the Customer sees who charges it and at what price. In this version, the mode does not change while the delegation lasts. If the Customer revokes it, the Customer remains a direct customer of Brida, with no registered agency, until a later version allows a new proposal.

14.5. An Agency does not represent Brida or its providers, and cannot bind them or promise anything on their behalf.

14.6. In its own prospecting Organization, the Agency is the Customer and the controller, and these Terms apply to it in full.

Clause 15. Third-party providers

15.1. Channel Providers. The Customer complies with the Platform Terms of each Channel and bears the risk of its account: the sending limits, the loss of reputation, the quality downgrades, the suspensions and the closures that the Channel Provider decides. Brida is not liable for those decisions unless a breach by Brida causes them. If a message does not go out because of a provider's decision, Brida releases its reservation.

15.2. WhatsApp. Meta requires the opt-in that names the Customer, approved templates outside the 24-hour window, the correct category for each template and a path to a person. Meta may limit, pause or close the Customer's number or WhatsApp Business account and change its rules and fees at any time. The BSP is Brida's supplier and subprocessor: Brida contracts and pays it, is responsible for it under the DPA and does not let it process Customer Data before it appears in Annex I of the DPA (clause 7.1 of the DPA).

15.3. AI providers. Brida uses AI models from the providers in Annex I of the DPA. The Customer complies with their published usage policies, which Annex A links. Brida may limit or suspend an AI feature if a provider requires it, and is not liable for that limitation when a breach by the Customer causes it. If one of Brida's AI providers stops supporting the country in which the Customer is established, Brida may stop providing the Service to it with 30 days' notice or, if the provider gives less, as soon as Brida knows, and refunds its unused purchased Credits (clause 12.6).

15.4. Google. Brida uses the data it obtains from Google APIs in accordance with the Google API Services User Data Policy, including its Limited Use requirements.

15.5. Brida is responsible for its subprocessors, including the BSP, under the DPA. It is not responsible for the Channel Providers or for the Customer's AI client, which the Customer chooses and contracts for.

Clause 16. Intellectual property and confidentiality

16.1. The Customer keeps its rights in the Customer Data and the Customer Content. It gives Brida only the licence needed to provide the Service under these Terms and the DPA.

16.2. As between the Parties, the Outputs generated for the Customer belong to the Customer, and Brida assigns to it any rights it may have in them. Other people may receive similar Outputs, and Brida does not warrant that an Output does not infringe third-party rights.

16.3. Brida keeps all its rights in the Service: its software, its agents' instructions and classifiers, its policies and its documentation. The Customer does not decompile it, does not copy it to build a competing product, does not extract models or training data from it and does not resell it, except as the agency terms allow.

16.4. If the Customer suggests improvements, Brida may use them without obligation.

16.5. Confidentiality. Each Party keeps secret the other's non-public information that it receives under this contract, and uses it only for this contract. This does not apply to what it already knew, to what becomes public through no fault of its own or to what it must disclose by law, giving the other Party prior notice where it can. It lasts for the term of the contract and 3 years after; for trade secrets, as long as they remain so.

16.6. Brida does not use the Customer's name or brand in its advertising without its written permission.

Clause 17. Suspension

17.1. Brida may suspend a Funnel, a connection or the Organization, to the extent necessary, only on these grounds, which are the legal mandate, breach, security and non-payment grounds of clause 15.4 of the DPA:

a) legal mandate: a legal obligation, a request from an authority or the cases of clause 3.4 (sanctions);

b) breach: a credible complaint from a recipient or an authority that points to unlawful sending; a breach of Annex A; an attempt to get around the blocks, the unsubscribe or the AI notice; or an Attestation shown to be false or inaccurate by evidence, by a complaint, by an authority or because it contradicts the source the Customer declared for the base;

c) security: a security incident or compromised credentials;

d) non-payment: a payment dispute under clause 12.9.

That Brida warned about a legal basis (clause 7.7) does not, by itself, make the Attestation inaccurate. Signals from a Channel Provider, such as a drop in the number's quality or a high complaint rate, lead to the pauses of clause 17.4, not to a suspension.

17.2. A person at Brida decides. When suspending, or before, Brida notifies the owner by email of the ground, the facts, how to respond and what is needed to lift the suspension. Brida lifts it without delay once the problem is resolved.

17.3. While the suspension lasts, the Customer can view, export and delete its data, revoke delegations, accept a new version of these Terms or close the relationship, but no new send goes out. Brida keeps recording opt-outs and bounces. Work that is not done is not charged, reservations are released, and the Opportunities not yet confirmed are voided and not charged (clause 11.3).

17.4. Automatic pauses that protect a Channel, for example because of bounces, complaints or a signal from the Channel Provider, and stopping a connection are not a suspension: they are part of the Service. A person of the Customer lifts the automatic pauses.

Clause 18. Term and termination

18.1. The contract has no fixed term. There is no lock-in and no minimum fee.

18.2. The Customer can terminate whenever it wants: by closing the relationship on Brida's pages with its passkey, or in writing to hi@brida.ai. A request by email opens the process: the owner confirms it on Brida's pages with their passkey or, if they cannot, Brida reasonably verifies the identity and authority of whoever makes it (Annex C).

18.3. Brida can terminate without cause with 30 days' notice to the owner, stating its reasons, and refunds the unused purchased Credits (clause 12.6).

18.4. Either Party can terminate for a material breach by the other that is not cured within 15 days of notice. Brida can terminate at once for a material breach that cannot be cured or that is repeated, such as a knowingly false Attestation or fraud, or by legal mandate.

18.5. When the contract ends (in a switch of provider, when the transition of Annex C ends), sends stop, delegations are revoked and the Channels' credentials are discarded. For 30 days the owner keeps access to the export page (Annex C), and then Brida deletes the data under the DPA. The Opportunities not yet confirmed are voided and not charged (clause 11.3). Charges already incurred are paid from the Credits, and the rest of the purchased Credits is refunded under clause 12.6.

18.6. The clauses that by their nature must survive termination survive it, among them clauses 7, 11, 12.6, 13, 16, 18.5, 21, 22, 25 and 26.

Clause 19. Changes to the Service, these Terms and the Price List

19.1. Brida only changes these Terms or the Price List for a valid reason: a change in the law or in an authority's position; a change in its providers' terms or costs; security or abuse prevention; new features that take no rights away from the Customer; correcting errors; or a new Price List, at most once every 6 months.

19.2. A change to these Terms, including to the Price List in Annex B, is a new version. Brida notifies the owner of it by email and on Brida's pages at least 30 days before its effective date, and explains what changes and why. A change required by law or security may apply earlier, with notice as soon as possible.

19.3. The owner accepts the new version as clause 4 provides. Until it does, from the effective date Brida does not charge under it and chargeable work stops, but the Customer keeps access to its data and the expiry of its purchased Credits stops running (clause 12.4). The Customer can terminate at any time, before or after the effective date, at no cost and with a refund of its unused purchased Credits (clause 12.6).

19.4. No change is retroactive. A settled charge is never recalculated. If the owner accepts the new version, a Version approved before its effective date keeps the prices of its Quote until it ends or until 30 days after that date, whichever comes first, and then pauses until an Authorised Person approves a Version with the new Quote.

19.5. The fee for WhatsApp messaging and the other provider costs charged at cost change when the provider changes them (clause 10.8). If it does not agree, the Customer can terminate at any time with the refund of clause 12.6.

19.6. Brida may change the Service without a new version of these Terms if the change does not materially reduce what the Service does for the Customer.

Clause 20. What Brida warrants and what it does not

20.1. Brida provides the Service with reasonable professional care and in accordance with these Terms, the DPA and the law. It warrants that the controls of clause 8 that the Service applies to the sends it makes and the content it receives (clause 5.8) work as described, on the data recorded in the Service and with that care, not an absolute result.

20.2. Brida does not guarantee results: replies, Opportunities, sales or deliveries. The only results guarantee is the one in clause 12.8.

20.3. Brida aims to keep the Service available, but gives no service level agreement. Where it can, it gives advance notice of planned maintenance.

20.4. Except as these Terms say, and to the extent the law allows, Brida gives no other warranties.

Clause 21. Liability

21.1. Each Party is liable for the damage it causes to the other by breaching this contract, within the limits of this clause.

21.2. Except as clause 21.9 says, neither Party is liable to the other for loss of profit, loss of revenue, customers, reputation or business opportunities, or loss of data beyond the reasonable cost of restoring it from a copy.

21.3. Each Party's total liability to the other in each period of 12 months does not exceed the greater of these amounts: the amount of the Service charges to the Customer's Organization in the 12 months before the first event giving rise to the claim, not counting WhatsApp messaging or other provider costs charged at cost; or €1,000. In the mode of clause 14.3, the charges generated by the Customer's Organization count, at list price, even if the Agency pays them.

21.4. For a breach of the DPA, of the security of Customer Data or of the controls of clause 8, Brida's limit, in total for each 12-month period and not in addition to that of clause 21.3, is the greater of these amounts: three times the amount of clause 21.3, or €25,000.

21.5. The limits and exclusions of this clause do not apply to damage caused intentionally or with gross negligence, to fraud, to death or personal injury, to liability that the law does not allow to be limited, to a breach of the confidentiality of clause 16.5 except for what clause 21.4 covers, to the Customer's payment obligations, to the indemnity in clause 22.1 or to Brida's damage under clause 21.9.

21.6. Brida is not liable for decisions of Meta and the other Channel Providers, or of the AI providers, that a breach by Brida does not cause (clause 15). This does not limit Brida's responsibility for its subprocessors under the DPA.

21.7. Nothing in this clause limits the rights of data subjects against each Party. Between the Parties, liability for damage to a data subject is shared according to each one's part of the responsibility (Article 82.5 of the GDPR), and whatever one Party claims back from the other falls within the limits of clauses 21.3 and 21.4, except in the cases of clause 21.5.

21.8. These limits apply to every claim between the Parties arising from these Terms or the DPA, except to the extent the standard contractual clauses incorporated by clause 13.2 of the DPA do not allow it. They do not shorten the statutory limitation periods.

21.9. Brida's damage from a breach by the Customer. Clauses 21.2 and 21.3 do not limit the direct and proven damage that a breach by the Customer of clauses 7.3 or 8.6, or of letters a), b), c) or k) of section A.1 of Annex A, causes to Brida: the sanctions that Brida's providers impose on it, such as the suspension of its WhatsApp access through the BSP or of the verification of its Google application, the reasonable costs of remedying them and of being verified again, and the revenue Brida loses while they last. They are always proven damage, never a fixed penalty.

Clause 22. Indemnity

22.1. The Customer holds Brida and its staff harmless against claims by third parties, including data subjects, recipients, Channel Providers and Brida's providers (its AI providers and the BSP), to the extent that they arise from:

a) a breach of the warranties and obligations of clause 7 or of an Attestation;

b) the Customer Content or the claims the Customer approves in the messages, except to the extent that the claim is due to a defect of the Service other than the text shown to it for approval;

c) an instruction of the Customer given after a warning from Brida about it;

d) a breach of Annex A or of the Platform Terms;

e) the acts of its Agency or of the people who use its Organization.

It covers what Brida must pay under a judgment or a settlement made under clause 22.5, reasonable defence costs and providers' penalties.

22.2. To the extent the law allows, clause 22.1 also covers administrative fines and penalties imposed on Brida, only for the part caused by that breach by the Customer. If this clause 22.2 were not valid, the rest of clause 22 remains in force.

22.3. Clause 22.1 does not cover what is due to a breach by Brida of these Terms, the DPA or the law, such as a check of clause 8.1 failing to stop a send that, applied to the data recorded in the Service, it should have stopped, a failure of the fixed block or of the unsubscribe, a security breach in Brida's systems or processing outside the Customer's instructions. Between the Parties, carrying out an Approved Version with its Attestations after a warning under clause 7.7 is not, by itself, a breach by Brida for the purposes of this clause. If both Parties contribute to a damage, each answers for its part.

22.4. Brida holds the Customer harmless, within the limit of clause 21.4 and with the exceptions of clause 21.5, against claims by third parties arising from a breach by Brida of the DPA or of its obligations as processor, or from the Service's software, without the Outputs, the Customer Content or third-party services, infringing a third party's intellectual property rights.

22.5. Whoever asks for the indemnity notifies the other Party without delay; late notice only reduces the indemnity to the extent of the prejudice it causes. The indemnifying Party leads the defence of third parties' civil claims, with the other's reasonable cooperation. Brida always leads its own defence in proceedings before authorities and in claims about its duties as processor, with the Customer's reasonable cooperation. Neither Party accepts a settlement that admits the other's fault or imposes obligations on it without its consent, which is not to be refused without reason. Each Party tries to reduce the damage.

Clause 23. Unlawful content, notices and contact

23.1. Brida's point of contact for customers, recipients and authorities is hi@brida.ai, in Spanish or in English.

23.2. Anyone may notify hi@brida.ai of a message or content sent with the Service that they consider unlawful or unwanted. Brida reviews it diligently, asks the Customer for what it needs and may apply clause 17. A recipient can unsubscribe at any time from the link in each message.

23.3. Brida controls content and sends with automated checks (the Funnel validator, the permission engine, the health quarantine and suppression) and with human review of complaints. When it restricts content or an account, it explains why under clause 17.2, and the Customer can respond.

Clause 24. Data export and switching

The Customer can export its data and switch provider at no cost, under Annex C.

Clause 25. Governing law and courts

25.1. This contract is governed by the law of Estonia, without its conflict of laws rules and without the United Nations Convention on Contracts for the International Sale of Goods, without prejudice to the mandatory data protection rules that apply to each Party.

25.2. The Parties submit exclusively, waiving any other forum, to the courts of Estonia and, at first instance, to Harju County Court (Harju Maakohus), in Tallinn. For claims of up to €5,000, a Party may use the European Small Claims Procedure (Regulation (EC) No 861/2007) before that court where that Regulation allows it. Either Party may seek urgent or interim measures before the competent court.

25.3. Before suing, the Party making the claim writes to the other, and both try to resolve it in good faith for 30 days. This does not prevent urgent measures or affect limitation periods.

25.4. Nothing in this clause takes away the rights that mandatory law gives the Customer, such as those of a Mexican micro-enterprise before the Federal Consumer Protection Agency (Profeco).

Clause 26. Language

These Terms exist in Spanish and in English. If the two texts differ, the Spanish text prevails.

Clause 27. Notices

27.1. Brida gives notice to the Customer by email to its owners and on Brida's pages. The Customer gives notice to Brida at hi@brida.ai.

27.2. A notice by email arrives when the recipient's mail server accepts it and does not return it as undelivered, and it is effective from then. If it bounces, the periods of clause 11 do not start until a notice arrives. When Brida offers it (clause 5.8), it shows the bounce on its pages and retries the notice at another owner's email. The Customer keeps its owners' email addresses up to date.

Clause 28. General provisions

28.1. Force majeure. Neither Party is liable for a delay or a failure caused by circumstances beyond its reasonable control that it could not foresee or avoid, such as a general outage of the internet, of a Channel Provider or of an AI provider.

28.2. Assignment. Brida may assign this contract to a company of its group or to whoever acquires its business, with notice to the Customer, who may terminate before the assignment with a refund of its unused purchased Credits. The Customer may assign it with Brida's consent, which Brida will not refuse without reason, or in a merger.

28.3. Brida may subcontract parts of the Service and is responsible for its subcontractors. Subprocessors follow the DPA.

28.4. This contract is the entire agreement on the Service and replaces anything before it.

28.5. If a clause is void, the rest remains in force.

28.6. Not exercising a right does not waive it.

28.7. The Parties are independent. This contract does not create a partnership, an agency or an employment relationship between them.

28.8. Only the Parties can enforce this contract, except for the people that clause 22 protects.

ANNEX A. Acceptable Use Policy

A.1. The Customer does not use the Service, or let anyone use it, to:

a) send unsolicited commercial communications without a legal basis, spam or bulk sends that breach the Marketing Laws or the Platform Terms;

b) write on WhatsApp to numbers that are bought, provided by third parties, enriched or scraped from the web, or without Meta's opt-in;

c) impersonate a person or another company, hide who sends or who sponsors a message, present the AI as a person or say that a person is present when none is;

d) deceive, defraud or mislead recipients, or publish fake reviews;

e) enter or request health data, other special categories of data, patient data or data of minors, full payment card numbers, bank credentials, identity document numbers or biometric identifiers;

f) offer on WhatsApp what the WhatsApp Business Messaging Policy prohibits (section A.2), among other things weapons, drugs, medical and healthcare products, adult content, dating, multi-level marketing, payday loans, debt collection, real, virtual or fake currencies, and alcohol, tobacco or gambling where they are not allowed;

g) political campaigns, or on behalf of parties or candidates;

h) give personalised recommendations on investments, credit, insurance, housing, employment or access to healthcare, unless Brida gives prior written permission;

i) send messages as a regulated financial institution in Mexico, unless Brida gives prior written permission;

j) miscategorise a WhatsApp template, send outside the 24-hour window without a template or get around Meta's review;

k) get around the caps, the blocks, the unsubscribe, the AI notice or the Channel Providers' limits;

l) offer a general-purpose AI assistant on WhatsApp;

m) make telemarketing calls or calls with an AI voice;

n) build or train a competing model or product, or extract the Service's instructions, models or data;

o) attack, probe without permission or overload the Service, or distribute malicious software;

p) unlawful content or content that infringes third-party rights;

q) breach sanctions or export controls (clause 3.4).

A.2. The Customer also complies with the Platform Terms, among them:

Of the terms of Brida's BSP, the Customer only takes on what this annex sets out, such as not entering the data of letter e) of section A.1. It does not have to accept the BSP's terms.

A.3. If the Customer breaches this annex, Brida may suspend under clause 17 and, if the breach is serious or repeated, terminate under clause 18.4.

ANNEX B. Price List brida-lista@2026-11-05

A single list in euros, the same in every country. Amounts exclude taxes. The wholesale price for Agencies is the list with a 40 % discount: the list × 0.6, rounded to the cent.

  • Account and monthly fee: €0.
  • "outcome" mode, floor per Active Contact per month: €0.05 (wholesale, €0.03).
  • "outcome" mode, per Opportunity, with an offer under €100: €5 (wholesale, €3).
  • "outcome" mode, per Opportunity, with an offer from €100 to under €1,000: €15 (wholesale, €9).
  • "outcome" mode, per Opportunity, with an offer of €1,000 or more: €20 (wholesale, €12).
  • "usage" mode, per Active Contact per month, from 1 to 10,000: €0.30 (wholesale, €0.18).
  • "usage" mode, per Active Contact per month, from 10,001: €0.20 (wholesale, €0.12). Tiers are marginal, per paying Organization and calendar month, and add up all its Funnels in the "usage" mode.
  • "value" mode: in beta and without a price; its price will come with a new version of these Terms (clause 19.2).
  • WhatsApp messaging: Meta's fee for each message, at cost and with no margin (clause 10.8).
  • Connected WhatsApp number: €10 per month, with no wholesale discount.
  • Email from the Customer's mailbox: €0.
  • Welcome Credits: €50, once per Organization, expiring after 90 days (clause 12.7).
  • First-campaign guarantee: clause 12.8.
  • Expiry of purchased Credits: 12 months (clause 12.4).

ANNEX C. Data export and switching

C.1. This annex sets out the switching rights of Chapter VI of Regulation (EU) 2023/2854 (the Data Act), and Brida applies it to all its Customers.

C.2. Notice. The Customer can ask at any time, without prior notice, to switch to another provider, to move its data to its own systems or to delete it, and says which of the three it wants. It asks on Brida's pages, with the owner's passkey, or at hi@brida.ai. A request by email opens the process: the owner confirms it on Brida's pages with their passkey or, if they cannot, Brida reasonably verifies the identity and authority of whoever makes it before acting.

C.3. Transition. From the request, Brida keeps the Service running for a transition period of up to 30 days, reasonably assists the Customer and its new provider, reports the known risks to continuity and maintains security. If 30 days are not technically feasible, Brida says so within 14 Business Days, with the reason, and proposes another period of up to 7 months. The Customer can extend the transition period once.

C.4. The contract ends when the switch is complete. If the Customer only asked for deletion, it ends when Brida confirms the request: there is then no transition, and the retrieval period of clause C.5 only applies if the Customer asks for it when asking for deletion.

C.5. Retrieval. After the transition, the Customer has at least 30 more days to download its data. Then Brida deletes it completely under the DPA and sends it a receipt.

C.6. These data, and only these, can be exported, in open, structured and machine-readable formats (CSV, JSON or YAML):

  • the Contacts, with their source and their permission evidence;
  • the suppression list, with the opt-outs and objections, which the Customer must keep honouring;
  • the Attestations, with their warnings and their cryptographic digests;
  • the Funnels and their versions;
  • the approved outbound content, while it is kept (180 days);
  • the admitted replies, with their intent and their metadata, and their text while it is kept (30 days);
  • the Opportunities, with their evidence;
  • the decision records of each agent action, without content;
  • the usage statements, the invoices and the Credit entries;
  • the metadata of the Channel connections, never their credentials.

C.7. These are not exported, because they are trade secrets or part of Brida's internal workings: the instructions and configurations of its agents and models, its classifiers and internal policies, aggregate statistics of several customers and security logs that would expose other customers.

C.8. Switching provider has no cost: Brida charges nothing for export, switching or deletion, and refunds the unused purchased Credits under clause 12.6.

C.9. Where the systems that process the data are located and who processes it is explained in Annex I of the DPA and in Brida's privacy notice (https://www.brida.ai/privacy), in what it says about its providers and about transfers outside the European Economic Area.