# Nearly – Family Location Sharing Without the Data Harvesting

> Source: <https://discuss.privacyguides.net/t/nearly-family-location-sharing-without-the-data-harvesting/37803?page=2#post_34>
> Published: 2026-06-23 20:27:14+00:00

Thanks everyone, lot to catch up on.

** @unseen / @ph00lt0** - I’d welcome Nearly going through that testing once it’s open to independent review.

[@Expert4870](https://discuss.privacyguides.net/u/expert4870)

AI: I use it, but only for debugging and boilerplate, plus website touchups (probably the “llmism” you spotted). The architecture, patterns and services are all mine. Some parts are even borrowed from past projects, long before LLMs took the stage.

Phone number is optional contact identifier for quick contact when getting an SOS from the child. Encrypted blob since the E2EE update.

Comparison table: one fix to the Nearly row. Full client-to-client E2EE shipped in June, and a direct APK is next.

** @The_Centurion** - Fits the Life360 use case. Worth noting: parents only see the child, not each other. There’s no parent-to-parent visibility right now which is nice idea.

** @overdrawn98901** - Strategy is what’s already live: a subscription covering infrastructure. No company or investors to buy out, just me, and I won’t sell.

To flag what’s easy to miss in a long thread: as of post 25, Nearly is client-to-client E2EE, not just TLS. Geofencing runs on the child device, and location, history, zone names, device and phone number are all encrypted blobs the server can’t read. Keys are exchanged during local pairing, never leave your devices, with a verification code against tampering. Still closed-source and solo, so the claim rests on trusting me until the design gets independent review.

** @Footprint** - Thanks. Android only for now, no iOS timeline I can commit to. Glad Zood works for you in the meantime.

/Martin