Identity · Safety · SaaS · In development

Aahlan Personal & Family

The consumer side of Aahlan — QR-driven identity tags for people, families and business cards, with contact handled in-app rather than by handing out a phone number.

Role: Founder · Product · Engineering
Category: Identity · Safety · SaaS
Status: In development

The problem

A tag on a bag, a car or a child's belongings only works if a stranger who finds it can reach you — and most people will not put a personal phone number on an object they might lose. The privacy cost of being reachable is the reason these tags mostly go unused.

Approach

Put the contact channel inside the app instead of on the tag. Scanning a tag starts a call or a message through the platform; the owner's number is never exposed, and they keep answer and decline control over every attempt.

What it does

Personal identity tags: A scannable tag that routes a finder to the owner without publishing any personal contact detail on the object itself.
Family safety tags: The same mechanism applied to family members, where the person who scans is usually a stranger acting in good faith and speed matters.
Business card privacy: A shareable professional identity that does not require handing over a mobile number to everyone at an event.
In-app video calls: Contact happens through the platform, with answer and decline flows, so the owner stays in control of who reaches them and when.
Account deletion: A real, complete deletion path — table stakes for anything holding identity data, and frequently missing from products in this category.

The hard parts

A stranger has no context: The person scanning a tag has never seen the product before, may not have the app, and is trying to help. The flow has to work for someone with zero investment in it.
Reachability versus privacy: The entire value is being contactable. The entire risk is being contactable. Every design decision sits on that line.

Detail

Product tiers

I structured the ecosystem around free, personal, family and business tiers. I don't document pricing here because it changes independently of this page — the product structure is the durable part.

Why the consumer side exists at all

The enterprise product answers "who is in this building". The consumer product answers "how does someone reach the owner of this thing". They share a mechanism — a scan resolving to an identity — and almost nothing else about who is using it or why.

Stack

Client: Mobile appQR contact experiences
Communication: In-app video callsPush notificationsAnswer / decline flows
Account: Account deletionFamily accounts

Case study

The decisions behind the build

CS-01Building an enterprise visitor management system for Saudi operations

ARTICLEWhy Arabic-first software is more than translating an English UI

All work