← withbuddi.com

Report abuse.

Every buddi reachable on onbuddi.com belongs to one person, and so does every buddi.si address. If one of them is being used to hurt people, tell us and we will act on it.

Write to us

A person reads every report. We acknowledge it within one business day.

What to report

A buddi at an address like name.onbuddi.com, or an email sent from a buddi.si address, that is used for:

  • spam;
  • phishing, or a page pretending to be someone it is not;
  • harassment or threats;
  • illegal content.

What to include

  • The hostname (name.onbuddi.com) or the address (name@buddi.si).
  • When it happened, as close as you can, with your time zone.
  • For an email, its full headers; for a page, a screenshot and the exact link.
  • A line on what happened. You do not need to know who is behind it.

What happens next

We acknowledge your report within one business day. When a report is credible, we suspend the instance (its onbuddi.com address and its buddi.si mail) while we look into it, so it stops reaching people at once. If the owner broke the rules, the suspension stays; if not, we restore it and tell them why it was paused.

What we can and cannot see

We run the relay that carries traffic to onbuddi.com and the mail edge for buddi.si. Each buddi runs on its owner's own computer, and we do not read the owner's data: their conversations, files and memory stay there. So we handle a report from the relay's logs (which instance, when, how much) and from what the sender's instance itself sent, which is what you saw. That is enough to find the instance and stop it; it is not a window into anyone's buddi.

Law enforcement

Requests from law enforcement go to abuse@withbuddi.com as well, with "Law enforcement" in the subject. Please include the legal basis for the request and how to reach you. Bear in mind what we can see, above: we hold relay logs, not the owner's data.

Security problems

Found a vulnerability in buddi, the relay or this site? Write to security@withbuddi.com rather than opening a public issue, with enough detail for us to reproduce it. We will reply, keep you posted while we fix it, and credit you when it ships if you would like. There is no bug bounty yet.

Last updated 4 October 2026.