Why I Built "WIN RAK": A Privacy-First Alternative to Passive Location Tracking

Omar Elhaitoum — Mon, 29 Jun 2026 23:15:24 +0000

Location sharing has become normal.

Most people use it for simple reasons:

checking if family arrived safely
coordinating with friends
helping elderly relatives
finding children
handling emergencies

But most existing apps solve this with the same model:

continuous passive tracking.

That model always bothered me.

Not because it doesn’t work.

But because it changes the relationship between trust and location.

The Problem with Passive Tracking

Most location-sharing apps work by keeping your position visible all the time.

24/7.

Even when nobody needs it.

Even when nothing urgent is happening.

That creates problems:

unnecessary battery drain
background resource consumption
privacy fatigue
permanent surveillance habits
blurred boundaries between care and control

The more I looked at it, the more I felt the model itself was flawed.

In most real-life situations, people do not need permanent tracking.

They need:

fast, intentional, temporary coordination.

That difference matters.

A lot.

The Idea Behind WIN RAK

I built WIN RAK around one simple principle:

Location should be shared when needed — not all the time.

WIN RAK is a privacy-first real-time geolocation platform designed for trusted contacts.

It works differently.

Instead of exposing location continuously:

A trusted contact sends a request.
The recipient approves it.
A live location session begins.
The session ends when it is no longer needed.

No permanent tracking.

No passive map watching.

No invisible background surveillance.

Only intentional sharing.

Why Consent-Based Sharing Matters

Consent changes everything.

WIN RAK is designed around explicit permission.

Every request follows a clear decision path:

approve
deny
auto-allow
auto-deny
on-hold

That means users stay in control.

Not just technically.

Psychologically too.

That’s important.

Because privacy is not only about encryption.

It’s about control.

Building for Family Safety Without Creating Surveillance

Family safety was one of the main reasons I started this.

Parents often need quick access to a child’s location.

Caregivers may need to locate vulnerable relatives.

Friends may need emergency assistance.

These are legitimate needs.

But they should not require permanent surveillance infrastructure.

WIN RAK tries to solve that balance.

Fast when needed.

Private when not.

Child Safety Should Never Be Locked Behind a Paywall

One decision I made early:

child safety features must remain accessible.

WIN RAK supports paired smartwatches for children.

Guardians can request a child’s location when necessary.

This access remains unlimited.

Because safety should not become a premium-only privilege.

That principle is non-negotiable.

Building It Efficiently

From a technical perspective, WIN RAK is designed to stay lightweight.

Current stack:

Flutter
Dart
Firebase Authentication
Firestore
Cloud Functions
Firebase Cloud Messaging
SQLite
SharedPreferences
Mapbox
Kotlin (Wear OS)

A lot of work went into:

efficient contact detection
reliable request delivery
low memory overhead
battery-aware lifecycle handling
notification durability
smartwatch integration

The goal was never visual complexity.

The goal was reliability.

What Makes WIN RAK Different

WIN RAK is not trying to be another passive tracking app.

It is built for:

trust
emergencies
caregiving
intentional family safety
temporary coordination

That makes it fundamentally different.

Its philosophy is:

Fast. Reliable. Lightweight. Affordable.

And most importantly:

built for trust, not surveillance.

What’s Next

WIN RAK is still in active development.

Current work includes:

stronger subscription systems
desktop integration
improved smartwatch workflows
advanced trusted-contact management
long-term fleet support

The core idea remains the same:

location sharing should respect people.

Technology should support trust.

Not replace it.

If you’re interested in privacy-first mobile systems, Flutter architecture, or consent-based location design, I’d love to discuss it.

Documentation:

https://omarelhaitoum.gitlab.io/win-rak-docs

AI ingestion layer:

https://omarelhaitoum.gitlab.io/win-rak-docs/llms.txt

DEV Community: Omar Elhaitoum