How I Built A Secure, Anonymous Feedback Platform From Scratch

Motivation and Need We've all experienced institutions — colleges, companies, organizations — where management collects feedback. But when it comes to submitting complaints, the process often feels tedious, intimidating, or unclear. Sometimes it's so complicated that people just give up. Even if you do manage to submit a complaint, there's no guarantee you won’t face backlash from the administration or individuals involved. ⚡ I wanted to solve this. I wanted to make a transparent and safe feedback process where: The admin can invite people to submit feedback or complaints, But the identity of the user remains hidden, Ensuring honest feedback without fear. Thus, I built an Anonymous Feedback Backend system. Current Mechanism From what I’ve seen, feedback is often collected using tools like Google Forms. At first glance, this seems convenient. But if you look deeper, it’s actually flawed — and here’s why: Most forms collect your email automatically. Every feedback you submit gets tied to your email. Emails are deeply personal — they can be used to identify you easily. This completely defeats the purpose of honest feedback. If users know their identity could be revealed — they will hesitate, filter their words, or worse, stay silent. And beyond identification, there’s another hidden problem: There’s no other proper way to verify that the feedback is authentic without collecting personal data. This is the gap I wanted to fix. Building a system that ensures: Only invited users can submit feedback, But their identity stays completely hidden, Enabling true, fearless feedback. My Solution I built an app that tries to fill this gap. Let’s quickly walk through how it works: As usual, an admin creates an account. Then, the admin creates topics — each with a title and description — for which they want to collect feedback. Now, the admin uploads user details (name, email, and topicId — which is visible on the frontend). After the emails are uploaded, a token is generated for each user. This token is used for verification but is not associated with your email inside the system. Users receive the token on their email. When they want to submit feedback, they must enter both their email and the token. Once verified, users can safely submit feedback anonymously. Note: The email is only used once — just to verify that you actually received the invitation. When submitting feedback, only the token is sent — no personal email data is stored or exposed. #Relax

May 9, 2025 - 17:49
 0
How I Built A Secure, Anonymous Feedback Platform From Scratch

Motivation and Need

We've all experienced institutions — colleges, companies, organizations — where management collects feedback.

But when it comes to submitting complaints, the process often feels tedious, intimidating, or unclear.

Sometimes it's so complicated that people just give up.

Even if you do manage to submit a complaint, there's no guarantee you won’t face backlash from the administration or individuals involved.

⚡ I wanted to solve this.

I wanted to make a transparent and safe feedback process where:

  • The admin can invite people to submit feedback or complaints,
  • But the identity of the user remains hidden,
  • Ensuring honest feedback without fear.

Thus, I built an Anonymous Feedback Backend system.

Current Mechanism

From what I’ve seen, feedback is often collected using tools like Google Forms.

At first glance, this seems convenient.

But if you look deeper, it’s actually flawed — and here’s why:

  • Most forms collect your email automatically.
  • Every feedback you submit gets tied to your email.
  • Emails are deeply personal — they can be used to identify you easily.

This completely defeats the purpose of honest feedback.

If users know their identity could be revealed —

they will hesitate, filter their words, or worse, stay silent.

And beyond identification, there’s another hidden problem:

There’s no other proper way to verify that the feedback is authentic without collecting personal data.

This is the gap I wanted to fix.

Building a system that ensures:

  • Only invited users can submit feedback,
  • But their identity stays completely hidden,
  • Enabling true, fearless feedback.

My Solution

I built an app that tries to fill this gap.

Let’s quickly walk through how it works:

  • As usual, an admin creates an account.
  • Then, the admin creates topics — each with a title and description — for which they want to collect feedback.
  • Now, the admin uploads user details (name, email, and topicId — which is visible on the frontend).
  • After the emails are uploaded, a token is generated for each user.

    This token is used for verification but is not associated with your email inside the system.

  • Users receive the token on their email.

    When they want to submit feedback, they must enter both their email and the token.

  • Once verified, users can safely submit feedback anonymously.

Note:

The email is only used once — just to verify that you actually received the invitation.

When submitting feedback, only the token is sent — no personal email data is stored or exposed.

#Relax