Dashboard

Developer overview

How the SafeCircle platform fits together — apps, backend, bot, search and AI — and what is open to integrators today.

2 min read

SafeCircle is a set of small services that share one backend. This section explains how they connect, which parts of the API you can read about, and how data moves from a child's phone to a parent's screen.

No public developer program yet

SafeCircle is in beta. The API described here is the one SafeCircle's own apps use. It is not versioned, not covered by a stability guarantee, and there are no public API keys. Procedures and fields can change between releases. If you want to build on it, write to support@safecircle.tech first.

Platform map

 Child's phone                               Parent
 ┌───────────────────┐                       ┌───────────────────────┐
 │ Child app         │                       │ Dashboard (web)       │
 │ (Android)         │                       │ Parent app (Android)  │
 │ on-device AI model│                       └──────────┬────────────┘
 └─────────┬─────────┘                                  │ session cookie
           │ x-device-token                             │ or bearer token
           ▼                                            ▼
        ┌───────────────────────────────────────────────────────┐
        │ Backend  (Hono + tRPC on Cloudflare Workers)          │
        │ api.safecircle.tech                                   │
        └───┬──────────────┬──────────────┬──────────────┬──────┘
            │              │              │              │
            ▼              ▼              ▼              ▼
      PostgreSQL      D1 (metrics)   R2 (images,     Push (FCM)
      (Hyperdrive)                   feedback)
            ▲
            │ bot API key            signed family link
   ┌────────┴─────────┐              ┌───────────────────────┐
   │ Telegram bot     │              │ Search                │
   │ @safecirclehq_bot│              │ search.safecircle.tech│
   └──────────────────┘              └───────────────────────┘
ComponentWhat it doesTalks to
Child app (Android)Watches visible text with an Accessibility Service and classifies it on the device. Sends an alert only when risk is detected.Backend, with a device token
Parent dashboard (web)Alerts, analytics, children, devices, settings.Backend, with a session cookie
Parent app (Android)Mobile alerts, push notifications, pairing.Backend, with a session bearer token
BackendAuth, data, alerts, push, media, telemetry.PostgreSQL, D1, R2, FCM
Telegram botLinks a Telegram account and shows account, children and alerts on demand.Backend, with a bot key
SearchPrivacy-first metasearch, with optional family safe-search lock.Backend (settings and family links)
AI modelClassifies conversations on the child's device.Runs inside the child app

Backend architecture

Stack, deployment shape and an alert's journey end to end.

API reference

REST routes and tRPC procedures, with inputs and outputs.

Authentication

Sessions, passkeys, 2-step verification, sign-up and device tokens.

Data and privacy

What is stored, what never leaves the device, and how deletion works.

Telegram bot

Linking flow and what the bot can do.

Observability

Metrics, the Grafana stack and the analytics opt-out.

SafeCircle Search

Privacy rules, family lock and running it yourself.

Repositories

Every repo, its stack and its licence.

For how the AI model reaches its decisions, see the AI overview. For setting up the apps as a parent, start with Set up the dashboard.