Skip to content
← All work

OROQ

live

A privacy-first family-safety suite — Chrome extension and Android app — that filters on-device rather than routing children's traffic through a server.

Role
Product and engineering lead
Period
2024 – present
TypeScriptChrome Manifest V3Android (Kotlin)VpnServiceCloudflare Workers
Context

Parental-control products overwhelmingly work by intercepting a child's browsing at a vendor server. That converts a safety tool into a surveillance pipeline holding minors' browsing history — a category of data no small vendor should hold.

The hard problem

Deliver credible content filtering, enforced SafeSearch and tamper resistance without the vendor ever seeing a URL, across two platforms with entirely different security models.

What I built
  • Built filtering to run on-device, so browsing data never leaves the user's machine and the product has no minors' browsing database to breach or subpoena.
  • Implemented PIN-locked settings and tamper resistance so the control cannot simply be switched off by the person it applies to.
  • Shipped a Manifest V3 Chrome extension under the restricted permission model, plus a one-click Focus Mode for distraction blocking.
  • Built the Android app on VpnService for system-wide filtering, and moved it onto a Google Play organisation account — the classification Google requires for VPN-class apps.
  • Consolidated three overlapping product names into one brand, accepting a short-term ranking hit for long-term clarity.
What it does not do yet

Weekly active users are still in single digits, and the rebrand cost visibility while search ranking rebuilt. The distribution signal that matters is not raw install count — it is that two thirds of installs land on ChromeOS, which is what a K-12 fleet looks like. That is the channel I am now pursuing deliberately.