Functional prototype · Evidence confidence: High

Sentinel Phone Security

A mobile-first browser security and privacy dashboard for checking suspicious URLs, domains, IP/network context, tracking exposure and security incidents.

Phone security toolPrivacy dashboardProgressive web app
Project IDPG-037
Repositoryblinky-guard
StageFunctional prototype
ConfidenceHigh
Also known as
Sentinel ShieldSentinel AIBlinky Guard

01 · Purpose

The problem

People need a clear place to inspect suspicious links and understand browser-visible privacy or network signals without being promised device-level protection a web app cannot provide.

02 · Experience

How it works

Users authenticate through Supabase, run URL and domain checks, inspect VPN/IP/network panels, review anti-tracking findings and incident records, and can unlock gated analytics and investigation panels through the existing Stripe-backed Pro subscription flow.

Users
  • Phone users
  • Privacy-conscious users
  • Security administrators
Technology identified
  • React 18
  • TypeScript
  • Supabase Auth and database
  • Supabase Edge Functions
  • Stripe
  • Vite PWA
  • Browser privacy and network APIs

03 · Functional evidence

What actually exists

Verified working / present13
  • Protected Supabase authentication flow
  • URL scanner
  • Domain reputation checker
  • VPN status detector
  • IP intelligence panel backed by geo-lookup
  • Anti-tracking audit panel
  • Threat feed, analytics and incident log UI
  • Email-threat and network-topology panels
  • Stripe checkout, customer portal and subscription-check functions
  • Free/Pro gating
  • Installable PWA configuration
  • Admin tooling
  • Live Lovable reference
Partially verified3
  • Several security panels interpret browser-visible or stored signals rather than providing operating-system-level enforcement
  • Security efficacy and third-party intelligence quality require live end-to-end validation
  • Background behaviour remains subject to browser and PWA platform limits
Designed / planned3
  • Production security review
  • Runtime verification across iPhone and Android
  • Clearer evidence labels for simulated, local and remote signals
Unknown / requires verification3
  • Production subscription state
  • Live third-party service availability
  • Current active user count

04 · Development

What remains

Finish / verify
  • Several security panels interpret browser-visible or stored signals rather than providing operating-system-level enforcement
  • Security efficacy and third-party intelligence quality require live end-to-end validation
  • Background behaviour remains subject to browser and PWA platform limits
Planned
  • Production security review
  • Runtime verification across iPhone and Android
  • Clearer evidence labels for simulated, local and remote signals
Resolve unknowns
  • Production subscription state
  • Live third-party service availability
  • Current active user count

05 · Commercial

Business model

Free security tools with a Stripe-backed Pro subscription path; current revenue and production checkout state are unverified.

06 · Intellectual property

IP position

Original dashboard, workflows and presentation; underlying network/browser signals and third-party data are not proprietary.

This archive records what the available project evidence says. It does not infer legal registration, patent grant, trademark ownership or regulatory status where that has not been verified.

07 · Assessment

Strengths and limitations

Strengths

  • Broad working tool surface
  • Mobile-installable PWA
  • Existing auth and subscription architecture
  • Honest browser-level security use case

Limitations / risks

  • A browser app cannot replace operating-system security, antivirus or a VPN
  • Some panels require runtime services and permissions

08 · Evidence

What this record is grounded in

  • GitHub repository: simonmowatt1-sudo/blinky-guard
  • Repository README / project brief where available
  • Implemented home route where available
  • Published Lovable URL recorded from repository metadata

A published URL means the project metadata records a deployment address. It is not represented as runtime-tested unless a separate verification pass confirms that deployment.

09 · Genealogy

Connections

Archive principle

Unknowns stay unknown until evidence changes them.
Back to Project Galaxy