Legal.

Six documents. They are written the way the rest of barua is written, because a promise you cannot read is a promise nobody can hold us to. Some of what they say is machine-checked against the code, so a change to how long replays live or to which companies touch your data fails a test until these pages catch up. The rest is a contract, which no test can check, and saying so is better than implying otherwise.

Status: draft 1.0, version , prepared 30 August 2026. These documents are not in force yet. They take effect when barua AS is registered and each page carries an effective date in place of this line.

The documents

The short version

If you run a site with barua on it, you are the controller and barua is your processor. Your visitors are your visitors. Your customers are your customers. barua holds their data to do one job for you, deletes it on your word, and never uses it for anyone else's site.

barua does not train models on your data or your visitors' data, and the model providers barua uses are contractually barred from training on it either. That is a commitment, and it is the one you should check us on hardest, because most of this category reserves the right in a sentence you have to hunt for.

Two duties sit with you rather than with us, and they are named in the terms rather than buried: having a lawful basis for the capture (including consent where the law where your visitors live requires it), and having permission to email the people on your list. barua gives you the switches for both. It cannot know whether you flipped them.

Asking about any of it

Write to chris@barua.ai. A countersigned PDF of the data processing agreement and a question about a clause go to the same place, and a person answers.

If you were emailed by a site running barua and want your data gone, the fastest route is the unsubscribe link in that email, then the privacy page, which explains erasure and who to ask.