Skip to main content

When we decide to fire a user

In this guide, you will understand when and why we choose to part ways with a user, and how we protect our team and product vision.

At Voicenotes, we work hard to build something thoughtful, useful, and calm. Most of our users get that—and we’re grateful.
​
But once in a while, we encounter a user whose behavior makes it hard for us to do our job. When that happens, we take a simple but firm stance:

If someone is abusive to our support team, repeatedly rude, entitled, or just persistently difficult to work with, we will cancel their account and ban them from using Voicenotes—permanently.
​

Their notes will still be accessible. They can export them. We won’t hold their data hostage. But they won’t be welcome on the platform again.
​

Why we take this seriously

If you’ve ever watched the backstory behind Voicenotes or heard our founders speak, you’ll know this started as a deeply personal side project. It wasn’t built in a VC boardroom or crafted around a market slide deck. It was something we needed ourselves—then shared, and steadily improved because others found it useful too.

We’re still a small, bootstrapped team. We don’t answer to investors. We build what we believe in. And we care a lot about what we’re making, and the kind of environment we’re building it in.
​

So when a user:

  • Treats our team with disrespect,

  • Believes they’re owed specific features or personalized product direction,

  • Expects us to rewrite our roadmap to fit their whims,

We don’t try to win them over. We let them go.
​

The app won’t be for everyone. That’s fine.

We’d rather lose a paying customer than compromise how we work—or who we work with. That’s not personal. That’s a boundary.
​

So if you’re here and respectful, we’re all in. If not, we’re not interested in doing business together.
​

Thanks for understanding.

Did this answer your question?