This is the agreement between you and barua. It is written to be read, because a term you did not understand is a term you did not agree to. Where it says barua does something, the product does that thing today, not in a future version.
Status: draft 1.0, version , prepared 30 August 2026. Not in force. These terms take effect when barua AS is registered and this line carries an effective date.
barua is operated by barua AS, a company registered in Norway (registration pending; the org number and registered address land here on incorporation). Reach us at chris@barua.ai. In these terms "barua", "we" and "us" mean that company, and "you" means the company or person that holds the account.
These terms cover your use of the barua service: the tag you put on your site, the operator
app at barua.ai/app, the pipeline that builds profiles and composes messages, and
the email barua sends for you. Four other documents form part of this agreement, and by
accepting these terms you accept them too:
If you need a countersigned copy of the data processing agreement on paper, ask and you will get one. You do not need to sign it for it to apply.
barua builds a profile of each person from what they did on your site, decides whether one useful message is worth sending, writes it, and puts it in front of you to approve.
barua often decides to send nothing, and that is the product working. We do not promise a minimum number of messages, a minimum number of drafts, or that any given person will ever be written to. Some days produce nothing at all. A quiet week is not a service failure and is not grounds for a refund or a claim.
The message allowance on your plan is a ceiling on what we will spend before we would rather talk to you, not a quantity you have bought. Reaching it starts a conversation. It never generates a charge.
barua composes from what it can see. If your site publishes little, or few people identify themselves, barua will have little to write from and will say so rather than invent. We do not warrant that any message will be opened or lead to a sale.
You need an account, and you are responsible for what happens under it. Keep your credentials private, keep the people you invite to the account limited to people who should see your visitors' data, and tell us promptly at chris@barua.ai if you think an account has been reached by someone who should not have it.
Your account carries a publishable key that goes in the tag on your site. That key is public by design: it is what a browser posts with, it is stored hashed on our side, and you can rotate it from the Setup screen at any time. It is a write-only key, so it cannot read your data. It is not a secret and must not be treated as one.
barua is for organisations rather than consumers, and not for anyone under 18. Do not open an account on behalf of a company unless you are authorised to bind it.
We give you a licence to put the barua tag on sites you control, for as long as your account is open. You decide where it goes, and you are responsible for your own site: its markup, its content security policy, and whether the tag is on the right domain.
You are responsible for having a lawful basis for what the tag captures.
Depending on where your visitors live, that includes obtaining consent before anything is
stored on their device or read from it. barua ships the switch for this: put
data-consent="required" on the tag and nothing is captured and nothing is written
to the device until your own banner calls barua.consent(true). By default, without
that attribute, the tag captures from the first pageview and writes to local storage
immediately. If the law where your visitors are requires consent first, you must use consent
mode. We cannot tell from our side whether you did.
You also owe your visitors notice. Your privacy policy is the one that applies to them, not ours, and it should say that a service like barua is in use and what it does. The privacy page is written plainly enough that you can link to it or lift from it.
Two things you must not do with the tag: put it on a site you do not control, or modify it.
If you need the traffic to route through your own domain, the tag supports a
data-endpoint override and we will help you set it up.
This clause is its own section because it is the one most worth understanding before you install anything.
By default, barua captures contact details a visitor is actively handing to your site: the email typed into a newsletter popup, the name on a checkout form. It takes them at the moment the form or the popup actually sends, never from typing alone, and it takes the same details when your site passes them through its data layer, the way shop platforms announce a signed-in customer.
That is a real collection of personal data, made by you, using barua as your processor. You
warrant that your own notice and lawful basis cover it. If they do not, or if you would rather
hand over identities explicitly from your own code, put
data-auto-identify="off" on the tag and barua will only learn an email when you call
barua.identify() yourself.
An external customer id sent from a browser is held as an unverified claim and is never trusted on its own, because a browser can say anything. To make your own ids authoritative, assert them from your backend against the authenticated endpoint. Ask us for credentials.
barua sends from your sending domain, so the message arrives as yours. You authorise us to send on your behalf from the domain you verify, and you warrant that you control it. You keep the DNS records we ask for in place.
If those records lapse, sending does not stop. A domain that stops authenticating raises an alert to us rather than pausing your messages, because a silent stop is its own kind of damage. That means mail can keep going out with failing authentication until the records are fixed, which hurts your deliverability, and we will email you when we see it. Fixing it is yours.
Checking is a rotation rather than a guarantee: domains are re-checked in batches through the day, newly added ones first, so on a busy day an established domain may wait longer than 24 hours for its turn. Watch the Deliverability screen if you have just changed DNS rather than waiting to hear from us.
You also warrant that everyone barua may write to has given you permission to email them, on a basis that is valid where they live. barua maintains a suppression list per account and puts one-click unsubscribe on every message, honoured the moment it is clicked. None of that substitutes for having had permission in the first place.
Deliverability is shared. Sending to people who did not ask for it damages the reputation of every sender barua handles, which is why the acceptable use policy is binding rather than advisory, and why we can stop sending for an account that breaches it without notice.
Your reporting shows attributed outcomes: what was sent, what was opened, what was clicked, and the purchases that happened inside the attribution window afterwards. Read that last number carefully, because it is the one most easily misread: it counts purchases where the person clicked, and purchases in the window where no click was tracked at all. So it is an honest count of what followed a message, and it is not a count of purchases the message can be shown to have caused.
It is not a causal lift figure, and we will not present it as one. Telling you how much revenue barua caused would need a control group of people held back from every message, and barua does not run one today. If we introduce one we will tell you before it starts, because it means some of your people stop hearing from you by design, and that is your decision rather than ours.
Everything barua holds about your visitors and your customers is yours. We hold it to run the service for you, on your instructions, and for nothing else. It is never pooled with another account's data, and never sold or shared with data brokers. Profiles are built from your site alone. What a person does elsewhere, barua does not learn.
The data processing agreement is where the detail lives: what is held, how it is secured, where it travels, and what happens when someone asks to be erased. On any question about personal data it wins over this page.
barua owns the service itself: the tag, the pipeline, the app, and everything we build. You own your brand and everything you put into barua. If you send us feedback or an idea, we may use it without owing you anything for it, which is the normal arrangement and saves us both a conversation.
When your account ends, we delete your data within 30 days, except where the law requires us to keep something. Two things survive on purpose and are named here so they are not a surprise: suppression records, which keep an address that asked to be left alone off any future send, and the accounting records we are legally required to retain.
barua uses language models from third parties to decide whether a message is worth sending and to write it. Those providers are named in the subprocessor list, with what each one does and where it processes.
barua does not train models on your data or your visitors' data. Not our own models, not in aggregated form, not in de-identified form. The model providers we use are contractually barred from training on it either. If that ever changes, it changes by us telling you first and you deciding whether to stay, never by a quiet edit to this page.
What we do use is our own operational record: counts, timings, error rates, costs, and whether a message was opened. That is how the service is run and improved, and it does not involve your visitors' content leaving the purpose it was collected for.
The acceptable use policy is part of this agreement. It covers where your list came from, what barua may not be pointed at, and the kinds of pages whose mere visit says something about a person that needs a stronger basis than curiosity.
Breaching it lets us suspend sending, suspend the account, or end the agreement, depending on what happened. Where it is safe to ask first, we will ask first.
Plans and prices are on the pricing page, and the plan you are on is the one you agreed when you signed up. Fees are quoted excluding VAT. Norwegian VAT is added where it applies, and where you are a business outside Norway you may be responsible for accounting for the tax yourself.
The meter is known people: someone with an email address, at least one real thing barua can write from, and who is not suppressed or unsubscribed. An address with no history is free, because there is nothing to compose from. A suppressed or unsubscribed person is free, because barua may never write to them again. That second exclusion is what makes unsubscribing lower your bill, and it is a term of this agreement rather than a marketing line.
Messages. There is no per-message charge and no overage of any kind. Sending more inside your plan never costs more, and never moves you up a band. Only how many known people you have moves a plan, and only after two consecutive months over the line.
Support is email, at chris@barua.ai, answered by a person. We do not offer a guaranteed response time and we do not offer an uptime commitment. If you need either in writing, talk to us and we will put a separate agreement in place rather than pretend this one covers it.
barua changes. We add things, we remove things that are not working, and we change how the pipeline decides. If we remove something you depend on, or make a change that materially reduces what you get, we will tell you at least 30 days ahead and you may cancel for a pro rata refund of anything paid for the period after the change.
You can cancel at any time by writing to chris@barua.ai, effective at the end of the period you have paid for. There is no cancellation button in the app yet, so the email is the route and we will not make it slower than a button would be. We can end the agreement with 30 days' notice.
Either of us can end it immediately if the other is in material breach and has not fixed it within 30 days of being told. We can suspend or end it immediately, without that window, for a breach of the acceptable use policy that puts other senders, your recipients, or us at risk.
When it ends, sending stops because nothing barua composes leaves without someone on your side approving it. One thing to know rather than assume: a draft already approved is queued, and stopping approvals does not recall it. We clear that queue as part of closing you down, and there is no separate server-side block today, so if someone on your account still has access and approves something new it will send. Tell us and we will remove the access.
You then have 30 days to ask for a copy of what is held, and we delete it within 30 days of the end. Removing an account is an operator doing it by hand today, not a button, so email us and we will confirm when it is done rather than leaving you to wonder.
We warrant that we will provide the service with reasonable skill and care, and that we have the right to give you the licence in these terms.
Beyond that, the service is provided as it is. We do not warrant that it will be uninterrupted, that it will be free of error, that a draft will be good, that a message will be delivered to an inbox rather than a spam folder, or that using barua will increase your revenue. Deliverability depends on your domain, your list, the receiving mail providers, and how people have reacted to you before. None of those are ours to guarantee.
Nothing in these terms limits a warranty that cannot be limited under Norwegian law.
Neither of us is liable to the other for indirect or consequential loss, lost profits, lost revenue, lost data where a backup would have prevented it, or loss of goodwill.
Each side's total liability under this agreement, for all claims added together, is capped at the fees you paid in the 12 months before the claim arose.
That cap does not apply to: your obligation to pay fees; either side's fraud, wilful misconduct or gross negligence; death or personal injury caused by negligence; or your indemnities under the next clause. Nor does it apply to anything that cannot be capped under Norwegian law.
You will cover us against claims that arise from your side of this agreement: the people on your list and how you got them, the content you approve and send, your lawful basis for the capture, and your use of barua in breach of the acceptable use policy.
We will cover you against a claim that the barua service itself infringes someone's intellectual property rights. If that happens we can also change the service so it no longer infringes, or end the agreement and refund the unused part of what you paid.
Either way, the side asking to be covered tells the other promptly, lets them run the defence, and does not settle without asking.
Each side keeps the other's non-public information confidential and uses it only for this agreement. That covers your data and your commercial terms on our side, and our pricing, roadmap and technical detail on yours. It does not cover information that is already public, that either side already had, or that has to be disclosed by law, in which case the side under the obligation tells the other where it is allowed to.
We would like to say you are a customer, with your logo. We will ask first, in writing, and a no costs you nothing.
We will change these terms occasionally, because the product changes. For a change that materially affects you, we give at least 30 days' notice by email to the account address, and if you do not accept it you can cancel before it takes effect and get back the unused part of what you paid.
Every version carries a date at the top, and the version you accepted is recorded against your account. Ask us for it at any time.
barua is pre-launch, and while signup is gated by an invitation code this clause applies to you. The service will change more than a settled product would, features may appear and be withdrawn, and some things described in our documentation are marked as not yet built because they are not yet built.
Design partner arrangements sit outside the pricing page: they are time-boxed, discounted, and written down separately in exchange for permission to use the measurement results. Where such an agreement conflicts with these terms, that agreement wins for that account.
Norwegian law governs this agreement, without regard to its conflict of law rules. The Oslo District Court (Oslo tingrett) is the agreed first-instance venue.
Before filing anything, write to chris@barua.ai and give us 30 days to sort it out. Most things are a misunderstanding and get fixed in a week.
If you are a consumer rather than a business, nothing here removes the rights you have under the mandatory consumer law of the country you live in, including the right to bring a claim there.
This agreement, together with the four documents named in clause 1 and any order or design partner agreement you signed, is the whole agreement between us on this subject, and it replaces anything said before it.
If a clause turns out to be unenforceable, the rest stands and the unenforceable part is read as narrowly as it needs to be to work. Not enforcing something once does not waive it.
You may not transfer this agreement without our written consent, which we will not withhold unreasonably. We may transfer it to a company that acquires our business, and we will tell you if that happens. Neither of us is the other's agent or partner, and nobody else gets rights under this agreement.
Notices to you go to the email on your account. Notices to us go to chris@barua.ai. Neither of us is liable for a failure caused by something genuinely outside our control, though that does not excuse paying.