The Privacy Advantage: Client-Side vs Server-Side Blocking

When you install a browser extension to filter content, you are trusting it with access to the web pages you visit. At NoGrok, we take that trust seriously. That's why we built our architecture to be strictly Client-Side. But what does that effectively mean for you?

Server-Side Blocking (The Wrong Way)

Many "smart" blockers work by sending the content of the tweets you see to a remote server. That server analyzes the text for spam and sends back a "block" or "allow" signal.

The Risks:

• Data Leakage: Your private browsing feed is being streamed to a third-party server.
• Latency: Waiting for a server response makes the scrolling feel sluggish.
• Downtime: If their server goes down, your protection stops.

Client-Side Blocking (The NoGrok Way)

NoGrok operates differently. We ship the entire "brains" of the detection engine inside the extension itself.

// Simplified Logic
function processTweet(tweetText) {
  // All logic runs right here in your browser's memory
  if (localPatternMatcher.test(tweetText)) {
    hideElement();
  }
}

The Benefits:

1. Zero Data Exfiltration: We literally cannot see your data. It never leaves your machine.
2. Instant Speed: Decisions are made in milliseconds, faster than the frame rate of your screen.
3. Offline Capable: While you need internet for X, NoGrok itself doesn't need to call home to work.

Conclusion

In an era of mass surveillance and data harvesting, we believe security tools should decrease, not increase, your digital footprint. By choosing NoGrok, you are choosing a tool that is mathematically incapable of spying on you.