Nearly – Family Location Sharing Without the Data Harvesting

Hello All. Earlier in this thread I said full E2EE wasn’t feasible because the server needed plaintext location for doze wake-ups and geofencing. I reworked nudging service and geofencing rules are now pushed from child device. Location (history), device name, phone number and smart-location (zone) names are now encrypted blobs the server can’t read. The keys are set during local-network pairing and never leave your devices. Pairing is automatic where possible; if that fails on some networks there’s QR pairing, and a manual code as last resort. After pairing you can compare a verification code on both devices to confirm there was no tampering in between. To be straight about what I can still see: your account email and timezone offset (ex. UTC+02), plus the basic connection metadata any server receives (IPs, timestamps). What I can’t read is your actual location or history - it’s ciphertext to me. So a subpoena or a breach has no location data to hand over or steal. That was the whole point. Still solo and closed-source - that part hasn’t changed, and I won’t pretend it doesn’t mean the E2EE claim rests on trusting me until I can get the design independently looked at. Happy to walk through any part of how it works. The E2EE build is live on Google Play. A direct APK from nearly.family is next. /Martin