Privacy policy
Last updated 13 October 2026
This policy explains what personal information Home Manager collects, why, who it is shared with, and how you control it. It covers the website at mylahm.com and the Home Manager Android app.
Who runs Home Manager
Home Manager is a private household management app developed and run by Liam Kelly in Queensland, Australia. It is not a public service: accounts exist only for members of one household and the people they invite, such as workers and contractors. Questions and requests go to the contact address at the end of this policy.
What we collect
- Account details: your name, email address, household role and a one-way hash of your password (the password itself is never stored). Each sign-in records the time, your IP address and your browser or device type.
- Household records you add: tasks, schedules, assets, documents, photos, issues, shopping lists and messages to the Home Manager assistant.
- Location: precise location from your phone, only if you turn location sharing on, and the names and positions of any places you add, such as work. The Android app can collect location in the background. See “Location” below.
- Notification details: the delivery address your browser or phone issues for notifications (a Web Push subscription or a Firebase Cloud Messaging token), and which notifications you have turned on.
- Paired device details: when you pair a phone with your account, its public device key, device model, Android version, app version and the result of Google Play Integrity's check that the app and device are genuine.
- Home system events: status and events from the household's alarm, cameras, gates and smart home equipment, and a log of who armed, disarmed or opened what and when.
- Camera and files: only photos you choose to take and files you choose to upload. The app does not access your camera or files in the background.
Location
Location sharing is off until you turn it on in the Android app. Before Android asks for permission, the app explains what will be collected. You can decline and still use the rest of Home Manager.
When location sharing is on, Home Manager uses your phone's precise location, including when the app is closed or not in use, for these purposes only:
- Arrive and leave home: Android's geofencing tells the app when you cross the boundary around home. Home Manager records whether you are home or away and when that last changed, and can use it for household automations you have set up, such as security reminders.
- Your places: if you add places such as work or school on the family map, Android's geofencing also tells the app when you arrive at or leave them, so the family map can say “At work” instead of “Away”. Adding places is optional and each person adds their own.
- Family map: when a household member who also shares their location opens the family map, your phone is asked for a fresh position, which is shown on the map. The map is drawn by Google Maps.
If you enable Approaching home, your paired phone reports crossings of your alert boundary and, in Distance mode, your smaller opening boundary. Home Manager records the person, time, decision and outcome, without coordinates. Your chosen car's Bluetooth identity stays on your phone. Depending on your selected mode, Home Manager can disarm the house and trigger the gate and garage.
Optional arrival tracking is a separate choice on your Android phone and starts off. While your selected car is connected, it checks fresh precise positions locally for up to six hours per drive, with a persistent notification and Stop tracking control. These tracking positions are not uploaded or saved as a route. Only boundary crossings go to the arrival service, without coordinates. This uses more battery than boundary alerts alone. Stop tracking pauses it until the selected car disconnects or you explicitly resume it; removing location permission, turning sharing off or unpairing also stops it. Tracking never replaces the required arrival screen, car connection or other opening checks.
If you enable Leaving home, your phone can report an outward crossing of the 100 m departure boundary or verified loss of a saved home Wi-Fi connection while connected to your selected car. Fresh camera checks can start a 10-second automatic closing countdown for open entrances. Stop on the notification or camera screen cancels future trip actions. Security presence remains a separate personal choice: fresh checks help decide whether to run an owner-reviewed Fibaro Away scene. Its listed effects can arm Fibaro alarm groups, lock doors and schedule lighting or climate actions. A later, separate Inception Arm security prompt requires an explicit choice. Stop cannot recall effects already sent to Fibaro, including its delayed actions.
The phone compares home Wi-Fi identifiers locally against hashes configured by the owner; it sends only home, away or unknown and the settings revision. The owner also configures a home occupancy radius, initially 25 m, which is separate from the departure trigger. Phone evidence is not a physical headcount. Missing consent, uncertain location or home Wi-Fi contact from a paired phone block Away and the Arm security offer. By default, a missing phone also blocks them. The owner can explicitly assume a named active owner or coordinator is away while they have no paired phone; the person, approving owner and approval time are stored separately. This can allow Fibaro Away's alarm and lock effects without that person's phone evidence. Pairing a phone ends the exemption and restores all normal presence checks. The assumption and household switch never grant another person's presence consent.
Home Manager keeps only your latest position and, if you added places, which of them you are at now. Each new position replaces the previous one; coordinate trails and place-visit histories are not stored. The security log retains arrival and departure decisions with the person, departure time, choice and outcome, including ignored, refused, cancelled or expired prompts where no control occurs. These decision records remain when location sharing stops. Your latest home Wi-Fi signal is removed with your stored position; network identifiers and coordinates are not copied into departure logs. The security log also records when you turn sharing on or off, when you add, rename or remove a place, and when someone refreshes the family map, but never a position or a place's name.
If Android reports that a position came from a mock location app, Home Manager refuses it and stores nothing from it; the security log records only that a mock location was refused.
Your position and home or away status are visible only to household owners and coordinators who are sharing their own location too. Where your places are is visible only to you; those people see only the name of the place you are at, and only while you are there. Workers, contractors and app review accounts cannot see anyone's location. Your location is never sold, never used for advertising, and never sent to the Home Manager assistant or any other AI service.
Separately, if the household requires it, the website may ask for your current position once when you sign in as a visitor, to confirm you are at the property. That position is checked and not stored.
To stop location collection, turn location sharing off in the app, remove the app's location permission in Android settings, or unpair the phone. Turning sharing off or unpairing deletes your stored position. Your places stay until you remove them on the family map, and are deleted if your account is deleted or can no longer use the app.
Optional News24 fullscreen and Android Accessibility
Android Accessibility lets a service inspect app controls and press them. Home Manager uses it only for its optional News24 fullscreen helper in BINGE. Before enabling it, read and accept the separate in-app disclosure, enable Home Manager News24 fullscreen in Android settings, and choose whether to use automatic fullscreen. You can decline and still open BINGE and use its fullscreen button manually.
After a native Play or Check tap, the helper inspects BINGE playback controls for up to 20 seconds. It checks control identifiers and classes, visibility, whether a control can be pressed, and player and screen bounds. Play makes a fresh read-only check before pressing the verified fullscreen control at most once. Check only inspects. A link cannot start automation. Locking, returning to Home Manager, leaving BINGE, interruption or the deadline stops the attempt.
This helper does not read screen text or account details, or press sign-in, subscription or purchase controls. It does not save or send screen data to Home Manager, AI services or anyone else. Your agreement and automatic-fullscreen choices are saved locally on the device; control proof and active attempts are not restored. Withdraw your agreement in the native panel or disable the service in Android Accessibility settings to stop using it.
How we use information
- To run Home Manager for your household: sign-in, tasks, schedules, records, security and smart home features.
- To send the notifications you have turned on, such as security alerts, reminders and task updates.
- To keep accounts and paired devices secure, including checking that a paired phone runs the genuine app, and to investigate misuse.
- To answer your questions through the Home Manager assistant when you choose to use it.
Home Manager has no advertising and no third-party analytics or tracking.
Who information is shared with
Home Manager does not sell personal information. It is shared only with these service providers, so that Home Manager can work:
- Amazon Web Services hosts the website and stores its data in Sydney, Australia.
- Google delivers notifications to Android phones and Chrome (Firebase Cloud Messaging), carries requests for a fresh position when the family map is opened (the request itself contains no location), draws the family map with Google Maps, runs Play Integrity checks and distributes the app through Google Play. While the family map is open, Google Maps receives the positions and places shown on it and the area being viewed.
- Your browser's push service (for example Google, Mozilla, Apple or Microsoft) delivers website notifications. Home Manager encrypts notification content so the push service cannot read it.
- xAI provides the AI model behind the Home Manager assistant. When you use the assistant, your messages and the household records it looks up to answer are sent to xAI. Location is never included.
Information may also be disclosed where Australian law requires it.
How information is protected
All connections use HTTPS. Passwords are stored as one-way hashes, stored credentials for home equipment are encrypted, and each paired phone keeps its device key in the Android Keystore, where it cannot be copied off the phone. Each person sees only what their household role allows, and security actions are logged.
Keeping and deleting information
Information is kept while your household uses Home Manager. The household owner can revoke your access at any time, which blocks your account on every device and stops notifications to your devices. Unpairing a phone deletes its device key and notification token and stops location collection from it.
To ask for your information to be corrected or deleted, contact the address below. Your account, stored position, places, paired devices and notification details will be deleted. Records the household needs to keep, such as the security log, may be retained with your name removed where practical.
Children
Home Manager is not directed at children. A child in the household can use it only with an account set up by the household owner, who is responsible for the child's use of it.
Changes to this policy
When this policy changes, the date at the top is updated. Significant changes, especially about location, are also announced in the app before they take effect.
Contact
Email liamkelly0207@gmail.com for privacy questions or requests.