Retrace Enterprises Presents

NOD

A private safety net for welfare checks, with missed check-in escalation, and explicit emergency actions.

Local-first
No cloud account or backend required.
Trusted circle
Manual contacts and transparent alert logs.
Explicit emergency actions
No silent calling or continuous tracking.
Check in Remind Escalate Log outcomes

Guided Check-In Flow

Simple enough for daily use. Clear enough when a check-in is missed.

NOD centers on one important action: the user confirms they are OK. If that does not happen, the app moves through a visible escalation path instead of pretending to be a rescue service.

01

Daily check-in

The user taps "I'm OK" on the Today or Check In screen. A note or mood can be added, but the core action stays large and direct.

02

Local reminders

Missed windows trigger local reminders, including a stronger second reminder. Quiet hours can suppress early reminder noise.

03

Trusted circle

Configured contacts are used for later-stage welfare alert attempts, with per-contact permissions and visible priority ordering.

04

Emergency contact

The final stage targets emergency contacts through the configured delivery gateway and records each attempt in the alert log.

Safety Boundaries

Designed to be helpful without becoming surveillance.

NOD's product direction is deliberately restrained. It gives people a check-in path and a trusted-contact escalation trail, while avoiding claims or behaviors that would make it feel like medical monitoring.

No continuous location tracking

Location is only considered for explicit emergency sharing and uses permissioned device APIs.

No silent contact access

Trusted contacts are entered manually, avoiding broad address-book harvesting.

No automatic emergency calls

Dial actions open the phone dialer. The user stays in control before any call is placed.

No delivery overstatement

Alert logs distinguish configured, attempted, and not-sent outcomes so the app stays honest.

Application Surface

Seven core screens with one user-centered information architecture.

Today

Current state and quick actions

Status, schedule summary, "I'm OK", remind-later, and emergency access live together so the daily path is obvious.

Check In

Deliberate confirmation

Optional note and mood capture without making the primary OK action harder.

Escalation

Stage visibility

Current stage, next escalation timing, cancel controls, and recent alert log entries.

Circle

Trusted contacts

Priority order, relationship data, and alert permissions for missed check-ins and emergencies.

Schedule

Timing policy

Daily, multiple, or day-specific windows, quiet hours, pause mode, and escalation delays.

Emergency

Confirmed actions

Call flows and trusted-circle alerts require confirmation before sensitive actions proceed.

Settings

Profile and accessibility

Large text, high contrast, reduced motion preference, notification settings, and local data tools.

Who It Serves

A lightweight routine for people who need a welfare signal, and the people who care about them.

NOD is suited to people who prefer living alone, those who are non-verbal, and their families and neighbours.

It is not positioned as emergency dispatch, a medical device, or a guaranteed monitoring service.

Current Build

Functional demo, with production hardening clearly identified.

This is an Android Java MVP with Room, WorkManager, local notifications, explicit emergency interactions, and a guarded delivery gateway. The next phase is quality, safety, and consent hardening before real-world production use.

Version 0.1.0
Platform Android
Architecture Local-first MVP
Delivery Guarded gateway
Needs validation, lifecycle architecture work, accessibility audit, dependency review, and consent-backed messaging before production use.

FAQ

Plain answers for a safety-adjacent app.

What does NOD do?

NOD helps a user record scheduled welfare check-ins. If a check-in is missed, it progresses through reminders, trusted-contact alerts, and emergency-contact alert attempts.

Does NOD track people continuously?

No. The app avoids continuous location tracking and broad contacts access. One-time location sharing is tied to explicit emergency action.

Does NOD call emergency services automatically?

No. Dial actions open the Android dialer and require the user to place the call. The app should not be described as a guaranteed rescue system.

Is messaging production-ready?

The current build includes a guarded alert delivery gateway. Real messaging needs consent, provider setup, delivery semantics, input validation, and regional/legal review before production deployment.