Hencob Sentinel

Quick update on Hencob Sentinel, the Android app I've been building to block scam and robocalls.

Since the last update I've gotten the core loop working end to end: local call screening on-device, a growing scam-number report database, account auth with email verification, and a lookup flow that cross-references incoming numbers against the FTC's Do Not Call/complaint data plus user reports. I also wired up the paid tier — Stripe checkout is live, and Plus subscribers get background blocklist syncing so the app stays current without opening it.

The private beta signup portal (magic-link, no password) is live too, feeding two email lists — general waitlist and beta testers — so I can actually communicate with people once they're in.

What's missing right now: testers. Zero so far. That's the point of this post.

If you're on Android and scam calls annoy you, I'd love to get you into the closed beta — it takes two minutes to sign up, and I'm looking for people who'll actually poke at it and tell me what's broken, not just install and forget. First real feedback loop starts now.

Beta signup: https://sentinel-beta-portal.hencob.workers.dev/ Main site: https://hencob.com

Thank you for reading!

Hey IH — wanted to share where things stand with Hencob Sentinel, the scam call blocking app I've been building.

For anyone new: Sentinel is an Android app that screens incoming calls in real time against a crowdsourced + FTC-sourced database of known scam numbers, and blocks them before they ever ring through.

What's changed recently

I spent the last stretch less on new user-facing features and more on the plumbing that lets me actually run this thing:

• Founding beta tier — early testers now get lifetime access, no strings attached, as a thank-you for helping me before launch. It's fully wired into billing so it never gets accidentally overwritten if that account ever touches Stripe.

• Internal admin tooling — I built out a small dashboard so I can manage beta access and review scam reports without hand-writing database commands every time. Sounds unglamorous, but it's the difference between "I can onboard testers in 10 seconds" and "I dread doing this."

• Report moderation — the crowdsourced reporting system (users flag numbers as scams) now has real moderation behind it. I can review individual reports, remove bad-faith ones, and override a number's status manually when needed. Important for keeping the blocklist trustworthy as more people start using it.

• Waitlist pipeline cleaned up — signups on the landing page now flow automatically into my email list, so nobody falls through the cracks between "signed up" and "got an invite."

What's next

Referral mechanics are the next big thing on my list — I want early users to have a reason to tell their (non-technical, most-scam-call-targeted) friends and family about Sentinel, since paid ads aren't really in the cards for a startup consumer security app.

If scam calls are a headache for you or someone in your life, the waitlist is open: hencob.com

Hello, I am Hencob Gaming, I am a solo dev. I started Hencob Sentinel to keep scam calls away, before they ring. Using a cross referenced database between the FTC Consumer Sentinel Network and my own user-sourced list of blocked numbers. This is done with an array of API's, apps, and websites, all talking to each other. This is update 1, thanks for reading!