Privacy policy
Last updated: October 20, 2026
EZ Software Labs LLC ("we", "us") makes EZHomePing, an app for sharing where you are with the people you choose. This policy says what we collect when you use EZHomePing and our website, why, who else receives it, how long we keep it, and what you can do about it.
EZ Software Labs LLC is a Texas limited liability company. To contact us about your privacy or this policy, email privacy@ezsoftwarelabs.com; about anything else, support@ezsoftwarelabs.com.
The short version
We cannot see where you are. Your phone encrypts your location before it leaves the phone, with keys only the phones in your circles hold. Our servers store that encrypted data and pass it on; they cannot open it, and neither can our staff. The same goes for your places, your alerts, your drives and your circles' names.
We keep what we need to run the service — your account, your phones, who is in which circle — and we can read those.
We do not sell your data, share it for advertising, or show ads. There are no advertising or analytics trackers in the app or on our website.
EZHomePing is offered in the United States, and this policy is written for people who live there.
What we collect, and why
| What | Why |
|---|---|
| Your email address | Sending your sign-in codes, and messages about your account — for example that a copy of your data is ready |
| Your phone number, if you give one | Signing you in by text if an email does not arrive, and — when many accounts are being made from one network or email domain — confirming that a new account is a real person's |
| Your network (the first part of your internet address, never all of it), kept with each sign-in code and in counts of sign-ups and codes, and your email's domain, as a keyed hash in those counts — for 24 hours at most | Noticing accounts being made in bulk, limiting how often codes are sent, and looking into abuse of sign-in |
| Your name | Shown to the people in your circles |
| Your month and year of birth — never the day — and your country | Checking you are old enough for an account, and applying the rules for your age and country. They cannot be changed in the app |
| Your phones: model, system and app versions, when each was last seen, their public keys, and a push token (on Android, Firebase's installation ID) | Delivering your circles' data to the right phones, and waking them |
| Your location, and the alerts you send — an SOS, arriving at or leaving a place, a possible car crash, hard braking, a low battery | Sharing them with your circles. Encrypted on your phone; we cannot read them |
| Your places, and your circles' names | Shown to your circles. Encrypted on your phone; we cannot read them |
| That an alert was sent, its kind (for example an SOS), and when | Waking the right phones quickly. Where it happened, which place, and how low a battery was stay encrypted |
| Which circles you are in, your role, and your sharing settings (paused, how precise) | Running the circles |
| Who left or was removed from a circle you are in, and when | For 30 days after, telling the members who were there, by name, that someone left or was removed |
| Whose low-battery alerts you turned off, and who turned off yours | Telling only the people who still want to know, and showing you who is told about yours |
| Whose phone you asked to hear about when it stops checking in, who asked about yours, and when each was last told — worked out from when your phone last reached the circle, never where it was | Telling them once when your phone has not checked in for two hours, and again when it does; and showing you who asked. Never while you have paused sharing or signed out |
| On the Max plan, your drives: each drive's route, speeds and hard brakes, speeding against posted limits, when your phone was unlocked while the car moved, and a score, made into one record on your phone and encrypted there; we cannot read it. We see only that you drove, the hour the drive began, and roughly how long it was | Showing your drives to you and to the people you choose |
| That you wrote a note on one of your drives — "I was a passenger" — and when. What it says stays encrypted | Leaving that drive out of your score, for everyone who sees your drives |
| Who you chose to see your drives | Handing your drives only to them |
| That one of your drives raised an alert, and which drive — for example three hard brakes in ten minutes. Which rule, and how many, stay encrypted | Telling the people who see your drives, and only them |
| How many locations arrived from each of your phones each day — a count, never a location | Helping support when "the map is not updating" |
| Your subscription, as Google Play or the App Store report it | Giving your circles the plan you paid for. We never see your card |
| Diagnostics you choose to send, and misuse reports you file | Support, and keeping people safe |
| What our staff did with your account, and why | Security and accountability: every staff look at personal data is recorded with its reason |
We do not collect your contacts, photos, messages, or advertising identifiers.
Your recovery phrase never reaches us: your phone can keep a copy of it where you will find it again — on Android in Google's Block Store, which Google encrypts end to end when your phone has a screen lock, and on iPhone in your iCloud Keychain.
Your age, as your app store knows it. Where a law asks app stores to vouch for their users' ages (Texas is the first), your phone asks Google Play or Apple for the age range they hold for you when you sign up, and holds it against the birth month and year you typed. That happens on your phone; the range is never sent to us or kept.
On our website. The contact form sends us your name, email address, topic and message by email; the website keeps none of it. We keep the email as long as we need it to answer you, and 3 years after. The form's page sets one cookie that protects it from forgery; it holds nothing about you and ends when you close your browser. Your account page on the web keeps you signed in and remembers display choices in your browser; it has no trackers either.
Teenagers
From 13 in the United States, a teenager can have an EZHomePing account of their own, linked to a parent or guardian until they turn 18. Nobody under 13 can make an account of their own. We collect the same information from a teenager as from an adult. Their guardian chooses who else sees their drives, can see that they are sharing and with whom, and approves their leaving or pausing a circle; the teenager always sees who their guardian is and what is in force. A teenager cannot own a circle or buy a plan. At 18 the link ends by itself, and we tell them both a month before.
A parent's consent through the App Store or Google Play. Where a law has the store ask a teenager's parent before they use an app — Texas does now, and Utah, Louisiana, Alabama and California will — we follow what the store says. The age range the store gives stays on the teenager's phone: we never receive it. We keep two things, and only for a teenager in such a place:
- whether the parent's consent stands or was withdrawn, and what they answered when we changed EZHomePing in a way the law calls significant;
- the identifier the store gave EZHomePing on the teenager's phone (Apple's app transaction ID, or Google Play's install ID), and only as a keyed hash — a code that matches the store's identifier and cannot be turned back into it — so that when a parent withdraws consent through the store, we can find the account and stop it.
If a parent withdraws consent, the teenager's EZHomePing stops — they share nothing and see no one, and their circles see them as paused — and we tell their guardian. It starts again when the parent gives consent again. Both are deleted when the teenager turns 18 or the account is deleted, and are in the copy of their data they can ask for (the keyed hash apart, which means nothing outside our servers).
Who else receives some of it
We use these companies to run EZHomePing. Each receives only what is listed, only to do this work for us.
| Company | What they receive | Why |
|---|---|---|
| Google Cloud, in the United States | Everything we store, encrypted as described above | Running our servers and keeping their backups |
| SendGrid (Twilio) | Your email address, and each email we send you | Sending email, sign-in codes included |
| Twilio Verify | Your phone number, if you give one, when we text you a code | Texting sign-in codes |
| Google (Firebase Cloud Messaging) and Apple (Push Notification service) | A push token, and a message with no content: a type and an id | Waking your phone |
| Google Play and the App Store | Your purchase, which they process | Subscriptions |
| Anthropic (Claude) | Public school-district calendars (PDF documents), and nothing about you | Reading a district's school year and holidays |
From your phone, not from us. To draw the map and name places, your phone asks map services directly: OpenFreeMap (the map on Android, drawn from OpenStreetMap's data), Apple Maps (the map on iPhone), and Google or Apple — your phone's own address lookup — for street names and addresses. These services receive the area in question and your phone's internet address, not your name or account.
Where a crash or hard braking happened is worked out on the phone that is told of it. On the Max plan the road, the direction, the exits either side and the mile come from the state's road data your phone already keeps (below), and nothing is asked of anyone; otherwise your phone's own address lookup (Google's on Android, Apple's on iPhone), which it already asks for the address, also gives the street's name. No other company is told where it happened.
Speed limits and road names are not asked of anyone along your drive. On the Max plan your phone downloads a whole state's posted limits and road names from us, made from OpenStreetMap's data (© OpenStreetMap contributors, under the Open Database Licence), and checks your drives against them itself. Schools: when you make a place a School, your phone downloads the part of our public directory of US schools around it, about 300 km across, with no account. Our servers' request logs record which state or which part of the directory was downloaded, with the network the request came from, as they record every request (below).
When the law requires it. We may disclose what we hold when valid legal process requires it, as our law-enforcement guidelines describe. They cannot include a location: we do not have one we can read.
If EZ Software Labs changes hands. If we merge with another company, or sell EZHomePing or our business, what we hold would pass to the new owner, and this policy would go on applying to it until it is changed as the last section says.
How long we keep it
- Your locations and alerts: for as long as your circle's plan keeps history — 1 day on Free, 14 days on Plus, 30 days on Pro, 60 days on Max — and a day's margin, then they are deleted within a day. A location older than 61 days is never kept, whatever the plan. When a plan ends or moves to a smaller one, what the new plan does not keep is deleted within a day of the change being final, after the store's grace period.
- Drives (Max): 60 days, as locations.
- Your account: until you delete it. Deletion happens 7 days after you ask, in case you change your mind.
- Sign-in codes: 24 hours after they are asked for. A phone's ended sign-in tokens: 24 hours.
- The stores' messages about a subscription: 30 days.
- Diagnostics you send: 30 days. A copy of your data, once ready: 7 days.
- Misuse reports: until they are dealt with, then 1 year. The record of what staff did: 1 year.
- Email you send us, or a message from our website's contact form: as long as we need it to answer you, then 3 years.
- Our servers' logs: up to 30 days. They record the network part of an internet address, not the whole of it, except in the record of a request that failed, and never a location.
- Backups: up to 30 days. Something you deleted can survive in a backup until that backup is gone.
Every period, and what deletes it: our retention schedule.
Your choices and rights
Whatever state you live in:
- Pause sharing with a circle, or make it approximate, at any time — in the app.
- Choose the alerts you get: you can stop hearing about someone's low battery, and hard-braking alerts, and alerts that someone's phone has stopped checking in, reach you only if you ask for them.
- Leave every circle at once, in the app or on your account page on the web.
- Get a copy of your data from your account page on the web, app.ezhomeping.com/account. Your location history is in it encrypted — only your phone can open it — and the app's Privacy → Save my history exports it readable.
- Correct your name, email address or phone number in the app. Your birth month and year and your country cannot be changed in the app; write to us if one is wrong.
- Delete your account in the app or on the web. It is deleted 7 days after you ask, and completely within 30. Deleting it does not cancel a store subscription: cancel that in Google Play or the App Store.
- Ask us anything about your data, or to do any of this for you: privacy@ezsoftwarelabs.com. We answer within 30 days, and may ask you to confirm the request from your account's email address first.
We do not sell or share personal information, use it for targeted advertising, or use it to make decisions about you with legal or similarly significant effects. There is nothing to opt out of. Your location is sensitive information, and we process it only to share it as you ask, with your consent on your phone; we cannot read it. If we turn down a request about your data, you can appeal by replying to our answer, and we will tell you the outcome within 60 days.
How we protect it
End-to-end encryption for locations, places, alerts, drives and circle names; your phone's sign-in key kept in its secure hardware; your personal details encrypted in our database, with the keys kept apart from it; staff sign in with passkeys, and every look they take at personal data is recorded with its reason.
No system is perfectly secure, and we cannot promise that nobody will ever reach what we hold without the right to. End-to-end encryption protects what it covers, not the facts around it that this policy lists as ours to read. And the phones matter as much as our servers: anyone who can use an unlocked phone in your circle sees what it sees, so keep yours locked and up to date, and remove one you lose. We never have your recovery phrase and cannot recover it for you. If we learn of a breach of security that affects your personal information, we will tell you, and the authorities, as the law requires.
Where it is processed
In the United States. Our servers and their backups are in Google Cloud's data centers in the United States.
Changes
We will post any change to this policy here before it takes effect, and change the date at the top. We may also tell you of a change in the app or by email, but the posting here is the notice. We will not use what we already hold in a way this policy did not allow when we collected it, unless you agree to it first.