How to use

The whole city district plus the places Karachiites actually drive out to: Sandspit, Hawksbay, Cape Monze and Mubarak Village on the coast, Manora, Hub River Road, the Northern Bypass, Gadap, Taiser Town, Bahria Town, Port Qasim and the Razzakabad / Gharo road. There is far less published data out there, so those outer zones are deliberately conservative — treat them as "isolated road, thin policing, few people around after dark" rather than a measured incident rate.

Only if you ask for them. Tap the bell, choose an area, and pick what you want: nearby alerts (a new report lands in or next to your area) and/or risk spikes (your area is heading into a much riskier window in the next few hours). At most one push every 20 minutes, so it never turns into spam. Turn it off in the same place. On iPhone, add the app to your Home Screen first — iOS 16.4 or newer.

A quiet, anonymous track record for each device. File a report, and when other people confirm it ("Still there"), your level climbs: New → Contributor → Trusted. A trusted reporter's report can show on the map without waiting for a second device. If people keep flagging your reports as wrong, your reports stop counting. No account, no name — just the anonymous device id the app already uses, and you can reset it any time by clearing site data.

Yes — open the alert and tap This looks wrong at the bottom. Enough flags and the report drops off the map, and the device that filed it loses standing. It's one flag per person per alert, so it can't be brigaded by one angry user.

Three layers. The seed comes from public reporting — Dawn, The News, Tribune, and CPLC's monthly Karachi crime statistics, last refreshed against 2025–2026 figures. On top of that, community reports from people inside the city nudge the score up. Separately, 🚦 usual jam spots mark corridors that published traffic reporting says choke at predictable hours. Full source list on the About page.

To show you what the app does. A handful of entries are logged from published news — a jewellery-shop robbery in Gulistan-e-Jauhar, a robbery encounter in Surjani, the DHA pipeline-leak closure, the Rabi-ul-Awwal procession diversions, the weekend Malir River bridge closure. Each one carries a note naming its source. Everything else you see is either the published-source risk model or the recurring-jam layer. Real community reports take over as people start using it.

Karachi's habitual chokepoints — Sohrab Goth, NIPA, Numaish, Shahrah-e-Faisal at Drigh Road, Korangi Causeway and a dozen more. They appear only during the hours those spots are usually heavy, and disappear outside them. They are a pattern, not a live report: nobody reported them today. They never touch the 0–10 score.

It's the same 0–10 scale drawn out, with a dot showing where this area sits right now. Left is worse: 0 is the highest risk, 6 is where "elevated" starts (below 6 the map tints the area), and 10 means no elevated pattern for this hour. The short tick on the bar marks that 6. Tap Why this number? in the zone sheet for the full working.

Tap any zone on the map and hit the Follow star, right next to Share. You can follow up to three (home, work, parents') and they show up in Today with the hours to avoid. It's saved on your phone only — no account, nothing sent to us.

Hit Share anywhere — a zone, a route, Today, the city page, or after you reach somewhere safely — and you'll see the picture before it goes out. Pick WhatsApp (square), Status (tall) or LinkedIn (wide), then Send with the link. The picture, a ready-made line of text and a Karachi Watch link always travel together, so whoever gets it can open the exact same area. Nothing personal is in the picture.

A zone only turns "reported" once two different devices submit within 30 days. Each crime submission is GPS-checked — you must be inside the zone or within 500m of it — and rate-limited per device. Weight decays over 30 days.

This is the reason the map never marks any area as safe. Only elevated, high, and very-high risk zones are tinted — everywhere else is plain map, on purpose. A green "soft-target" heatmap would help the wrong people, and no Karachi street is genuinely risk-free anyway. What the map does show is where a pattern is worse than usual right now, so you can plan around it. Every zone card also leads with the same "stay alert" habits, elevated or not.

Same reason. A snatcher's map is not something we're going to publish. Zones are ~700m across — block-level, so one incident in Block 6 doesn't flag all of Federal B Area, but still useless to someone trying to pick a corner.

Depends what you're reporting. Crime and accidents: inside the zone or within 500m of it, checked by GPS — that's what keeps fake pins out. Jams, road closures, dharnas, processions, flooding: anywhere inside Karachi. These affect the whole city and are usually public knowledge, so you can flag one you heard about on the other side of town. The catch: if you're not at the spot, your alert only appears once a second person reports it too.

They're live road alerts, separate from the crime layer. A dashed pin is unconfirmed (one report); a solid pin has been confirmed by two or more people. A faded pin is something scheduled that hasn't started yet. Jams, floods and accidents clear after ~3 hours (6 if confirmed); closures, dharnas and events after ~12 hours (24 if confirmed). Tap a pin and hit Still there to keep it alive or It's clear now to retire it. Road alerts never move the 0–10 risk score.

Install it as a PWA (Chrome / Safari → "Add to Home Screen"). The last map view and scores are cached, so you get a usable snapshot even on patchy signal.

Not yet — push alerts for "your area's risk just spiked" are on the roadmap. Android (Chrome) and iOS 16.4+ both support PWA push once we ship it.

Email iamnomisg@gmail.com with the area name and, if possible, a link to a news source. Corrections ship within a day or two.

Yes. We store a hashed device ID for rate-limiting only — no name, no phone number, no login. Reports are never shown individually to other users, only aggregated per zone.