Randhawa & Bhullar for iOS · Last updated August 2026
We do not collect any data. There are no accounts, no analytics, no advertising, no third-party SDKs, and no servers of ours anywhere. Everything the apps store belongs to you and stays in places only you control.
Randhawa reads your location and saves it as a dot in a file on your device. It does this each time you open the app, and, since version 3.2 and with your permission, each time your phone notices you have gone somewhere while the app is closed. That second part is called the trail, and it is how the map is meant to be made; here is exactly what it does and does not do.
It asks before it listens. When you first open Randhawa, the intro screen says in plain words that the map will draw itself, and tapping Begin brings up iOS's own location prompt. Nothing is read until you answer. If you allow, iOS grants background access provisionally and, some time later, asks you again on its own whether to keep allowing it. If you choose "While Using" at either point, Randhawa falls back to marking a dot only when you open it. If you were already using Randhawa before 3.2 with location set to While Using, the app shows you one card explaining the trail and asks; nothing changes until you say yes and iOS asks you too. You can turn the trail off in the menu under Trail, or set Location to While Using or Never in Settings, and it stops at once.
What the trail listens to. Two low-power signals from iOS: significant location changes, which arrive after you have moved a few hundred meters, and visits, which arrive when you settle somewhere. It does not use continuous location tracking, it does not keep your phone awake, and it does not poll on a timer. The cadence you choose in the Trail screen is a maximum, not a schedule: it sets how close together two dots are allowed to be, and if you do not go anywhere, nothing is recorded. Dots the trail places are stored exactly like the ones you place by opening the app, in the same file on your device, and go nowhere else unless you have turned on iCloud sync. You can delete every dot the trail placed, and keep the ones you placed by opening the app, with "Forget the trail" in the same screen. "Erase everything" deletes it all.
The map is drawn from that file and nothing else. Since 3.2 Randhawa also draws lines between dots that are close together in time, to show how you moved, and colours today's dots and lines orange. Those lines are drawn on your screen from the dots already on your device; nothing new is recorded to draw them.
Export. "Export your map" in Randhawa's menu writes everything the apps hold, dots, memories and their photos, into a single file and hands it to the iOS share sheet. It goes only where you send it. We never see it.
Both apps can save memories you write yourself: a note, optionally a photo, with a time and (in Randhawa) a place. Memories are stored on your device, in a container shared by the two apps so each can show what the other saved. Photos are chosen through Apple's system photo picker, which runs outside the app, so the apps never get access to your photo library, only to the single photo you pick; or, since Randhawa 3.2 and Bhullar 2.2, taken with the camera, which the apps use only when you tap "Take a photo" and which writes the photo to the memory, not to your photo library.
Bhullar's time grid stores nothing at all. Every dot is computed on your device from the current date. Bhullar never asks for location permission and records no location of its own. You can tap a dot to see what that stretch of time held; to do that it reads the moments and memories Randhawa already saved in the shared container on your device. Its widgets read the same memories to colour the days you kept something.
Sync is off until you switch it on. When you do, your dots and memories are kept in your own private iCloud database (Apple CloudKit), tied to your Apple Account. We cannot read it: Apple does not give developers access to anyone's private database, and we run no servers of our own. Sign into iCloud on a new phone and your data comes back. Erasing your map inside the app also deletes the iCloud copy. Apple's handling of iCloud data is governed by Apple's privacy policy.
Map tiles and place names come from Apple's MapKit and geocoding services, requested by iOS itself under Apple's privacy policy. Turning a coordinate into a place name sends that coordinate to Apple: Randhawa does this when you save a memory or open a place on the map, and Bhullar does it when you open a dot that has places in it. Neither result is sent anywhere else, and our code sends nothing else over the network.
Both apps are suitable for all ages and collect no data from anyone, including children.
If this policy ever changes, the updated version will be posted on this page.
Questions? Email contact@prabhchintan.com.