Skip to content
WLOCAuthorized iOS location testing

Owned-device nearby, family, and fitness privacy rehearsals

How can family-location apps test owned-device location states?

Family-location apps must respect consent while handling offline devices, denied permissions, low battery, delayed updates, and stale member locations.

Solution

Solution

The practical alternative: use owned devices and safe public points to test member maps, last-updated times, consent messaging, and recovery flows. Every run should be based on explicit consent and devices the tester controls. Remove temporary family members or test data as needed, then return devices to normal location behavior.

Problem

Problem

Family-location apps must respect consent while handling offline devices, denied permissions, low battery, delayed updates, and stale member locations. Testing with real family addresses exposes privacy and makes edge cases hard to reproduce. Inspect a family tile you administer on a phone you own; this is not a hide-from-guardian tutorial and must not name a real child’s commute.

Use WLOC in 3 steps

Use WLOC in 3 steps

  1. Prepare safe points for owned devices.

    Use public locations that do not reveal home addresses and label online, offline, and boundary states.

  2. Check member visibility and freshness.

    Verify map position, last-updated time, permission-off prompts, and low-power or offline states.

  3. Clean up and restore real location.

    Remove temporary family members or test data as needed, then return devices to normal location behavior.

Important boundary

Important boundary

WLOC is not a jailbreak. The current testing Profile includes a certificate and a VPN tunnel, and it does not require a separate third-party VPN client. Saving a target, Gateway acceptance, or a submitted Restore does not mean the target app adopted the location or that the device is already restored. WLOC does not promise to override every app's permissions, cache, or anti-cheat checks.