Inside Mailbutler
How we introduced an AI bot for tier-one customer questions
Learn how we implemented an AI-powered support bot to improve our response times, reduce agent workload, and deliver round-the-clock answers to customer questions.
Former Tanzanian, now happily repatriated European, back in my birth-place of Berlin. I enjoy the little things in life, as well as traveling, hiking and spending time with good friends.
Privacy is not something we “implement.”
It’s something we believe in.
From the very beginning, Mailbutler was built on a simple conviction: technology should support people, not take advantage of them. And that belief guides every product decision we make — especially around features like email tracking, which naturally raise questions.
In my earlier article, Inside Out: How Mailbutler Respects Your Privacy, I explained how we architect our system around minimal data, transparency, and respect. In this follow‑up, I want to go a level deeper. I want to explain:
Because compliance is important — but values are what shape how we build.
Email tracking can easily be misused or misunderstood.
Many tools collect more data than necessary. Some profile recipients. Others store detailed behavioral logs.
We do none of that ❗️
To us, the ethical question always comes before the technical one. I have rejected opportunities, features, and data practices that would have helped us grow faster — simply because they conflicted with our values or would have chipped away at user trust.
We build tracking, yes. But we build it with intention.
Before getting into GDPR roles, here is the cornerstone of our tracking architecture:
Not even their email addresses.
Instead, every recipient is represented internally by a non‑reversible unique identifier. This identifier allows per‑recipient tracking — without giving us any knowledge of who the person actually is.
Only your email application knows which identifier belongs to which recipient — and that's by design.
Your recipients remain your private relationships, not ours.
Some users prefer seeing names, initials, or subject lines in their Mailbutler dashboard. Others prefer full anonymity.
We respect both. So we let you choose.
You can optionally add:
These labels are stored only so you see a more meaningful UI.
They are not required for tracking to work.
They are not processed beyond your own visualization.
They do not change how our system treats recipient data.
Mailbutler does not use this optional information for any processing or profiling. And tracking works perfectly without it.
To understand compliance, we must explain the GDPR roles clearly.
As the sender, you decide:
This gives you responsibility — not only technical, but legal and ethical.
We provide the tools; you decide how to use them.
Our role is to:
We do not decide why you track or who you track — you do.
And because we do not store recipients' personally identifiable information (PII), our processing footprint is extremely small.
The GDPR distinction between controller and processor ensures accountability and clarity:
This structure aligns perfectly with our values: You stay in control of your communication relationships, and we remain a privacy‑conscious facilitator.
Mailbutler could technically store more data.
We could track more details.
We could build features on top of that data and market them as powerful insights.
But I founded Mailbutler on the belief that values matter more than profits.
Privacy matters.
Trust matters.
Integrity matters.
And I will always choose those over quick gains.
Because in the long run, a company that respects people will always build something more meaningful — and more sustainable — than a company that simply extracts what it can.
Email tracking doesn’t need to be intrusive.
It doesn’t need to compromise anyone’s privacy.
And it certainly doesn’t need to be built around sensitive personal data.
With the right architecture and the right values, you can build tools that are both powerful and respectful — and that’s what Mailbutler stands for.
You remain in control.
We remain committed to privacy.
And most importantly, we remain committed to our values — even when choosing that path is harder.
If you ever have questions about how we protect data, how GDPR applies to your use case, or why we make certain architectural decisions, reach out.
Transparency isn’t a legal requirement for us.
It’s part of our identity.