Your team today
Messages · end-to-end encrypted
Today
Cancel alert
Enter your PIN
Demo PINs: 1234 cancels. 9876 is the duress PIN. It looks like a normal cancel on this screen, but tells ops you are under duress.
Report to ops
Safe havens on this route
Principal · SPARROW
Operations
24/7 · Live Ops controller S. Novak · 14:06Active details
Alerts
Log
Check-ins · every 15 min
Updates today
Itinerary
What this account can see
- ✓Arrival and departure updates
- ✓Today's itinerary
- –Live location or route
- –Team names and messages
Set by ACERO with Mr. Laurent's agreement. Ask your ACERO contact to change it.
Questions or concerns
Answered 24/7
One private channel between your clients and your team, hosted by ACERO.
Who sees what
Four roles, four levels of access
The main difference from consumer apps like Life360 is that nobody sees more than their role needs. The principal never sees other clients, family never sees a live location, and only the ops room sees every detail.
| Principal | Protection team | Ops room | Family & PA | |
|---|---|---|---|---|
| Live vehicle location | Own movement | Their detail | All details | No |
| Arrival time and route status | Yes | Yes | Yes | Arrived / departed only |
| Team names, vehicle, code word | Yes | Yes | Yes | No |
| Encrypted messages | With their team | With their principal | All threads | No |
| SOS / silent alert | Sends | Receives, acknowledges, sends | Receives, escalates, resolves | Told by ops if needed |
| Check-ins and reports | No | Sends | Monitors, pings | No |
| Location history | Own trips, 30 days | Current task only | Full, per retention policy | No |
Security model
Built for clients who cannot be tracked by anyone else
Architecture
How the pieces fit
On the phones
- One iOS and Android app (React Native) with three modes: principal, team, family
- Ops dashboard in a web browser
- Background GPS only while on duty or on a movement
- Encrypted local storage, passkey sign-in
→ encrypted connection (TLS 1.3, certificate pinning)
ACERO server · self-hosted
- API and real-time service (WebSocket)
- PostgreSQL with PostGIS for movements, routes and geofences
- Alert engine: SOS, geofence, stationary vehicle, overdue check-in
- Encrypted messaging service
- Map: Google Maps, or a self-hosted OpenStreetMap map styled to look like Google (decision below)
- Audit log and encrypted backups
Outside services · minimal
- Apple and Google push: wake-up signal only, no content
- Google Maps, if chosen: map display, routing and traffic. Google receives the map areas viewed and the routes requested
- SMS and voice fallback for SOS when there is no data signal (optional provider)
- Later: in-vehicle GPS trackers and hardware panic buttons
Build plan
From prototype to live clients
Prototype
This page. Agree the screens, roles and alert rules with your team and one or two trusted clients.
MVP
iOS and Android app, ops dashboard, live movements, SOS, messages, check-ins and family status, on your own server.
Pilot
Two or three clients on real details. Penetration test and fixes before wider rollout.
Extend
Vehicle trackers, watch SOS, low-signal and satellite fallback, flight and itinerary sync.
Time estimates are rough and assume a small team: two developers and a part-time designer.
Decisions for ACERO
Questions to settle before the MVP
- Map provider. Google Maps is familiar to clients and has the best live traffic and routing. In exchange, Google receives every map view and route request, which can reveal where a client is going. A self-hosted OpenStreetMap map can be styled to look like Google and keeps all of that private, but has weaker traffic data. The prototype shows both: the Google-style drawn map, and real Google Maps in the local version.
- Hosting region and provider. Which country client data must stay in, and whether you run your own hardware or a private cloud.
- Client phones. Clients use their own phone, or ACERO issues a dedicated, managed device.
- SOS escalation. Who is alerted, in what order, and when local emergency services are called.
- Retention. How long movement history is kept, and who can hold it for an incident.
- Family access. What each family member or PA may see, and who approves it.
- Legal. Consent and privacy notices under the laws where your clients live, for example PIPEDA in Canada or GDPR in Europe.