Homey — Privacy Policy
Last updated: 20 September 2026
The short version
Homey holds what a household puts on its shopping list, what is on the family calendar, what is planned for dinner, the recipes it has saved, and the names of the people involved. It shows no adverts, contains no third-party analytics, and sells nothing to anyone.
Homey is for adults. Everyone who uses it holds their own account, created with their own email address. There are no accounts for children, no way for an adult to create an account on somebody else's behalf, and nothing in the app is directed at children.
What is collected
When you create an account
| Data | Why | Where it lives |
|---|---|---|
| Email address | To sign in and recover the account | Supabase Auth |
| Password | To sign in; stored only as a hash | Supabase Auth |
| Display name | So the household can tell who added what | profiles.display_name |
From the household itself
| Data | Why |
|---|---|
| Household name and its 8-character join code | To let people join the right house |
| Shopping items: what, how much, who added it, who ticked it off, when | The shopping list |
| Calendar entries: what is happening, when, where, an optional note, who added it | The family calendar |
| Dinners: the date, the meal, the ingredients written for it, who wrote it | The weekly dinner plan |
| Recipes: the title, the link it came from, ingredients and method | The recipe importer |
All of it is typed or pasted by the household. None of it is inferred, bought, or brought in from anywhere else, with two exceptions, and both of them start with something you did:
- When you paste a recipe link, the server fetches that page to read the ingredients off it. It saves nothing until you say so, and the page is one you chose.
- When you type where a calendar entry is, the server asks Google Places to suggest the rest of the address, and sends it what you have typed so far to do it. Nothing is sent until you have typed three characters, nothing is sent while you are still typing, and nothing is saved unless you pick a suggestion or write the place out yourself. The field is optional, and places this household has used before are offered without asking anybody.
What is not collected
- No advertising identifiers, and no adverts
- No third-party analytics or tracking SDKs
- No device location. The app never reads GPS or network location, asks for no location permission, and could not find you if it wanted to. What it does hold is the odd address somebody has typed into a calendar entry themselves — “the Harpers’”, or a street address picked from a suggestion — stored exactly as it was written and treated like any other thing this household typed.
- No contacts, camera, microphone or photo access — the app requests none of these permissions, and contains no code that could use them.
- Nothing from children, because children have no accounts
What the app asks Android for
Homey itself asks for one permission: internet access, without which it does nothing. The installed app carries six more that were declared by the Expo libraries it is built on rather than by Homey. They are listed here because the store listing shows them and nobody should have to guess why.
| Permission | Why it is there |
|---|---|
| Internet | The whole app: every list, date and recipe lives on the server |
| View network connections | expo-updates, to tell whether it can reach the update server |
| Read and modify storage |
expo-file-system. Capped at Android 12L, so on
Android 13 and newer they do nothing at all
|
| Vibrate | Haptic feedback |
| Display over other apps | Declared by a library, not by Homey, which never draws over another app |
| A receiver permission named after the app's own id | Internal to AndroidX. No other app can hold it |
None of these collect anything. Homey has no code that reads your files, your location, your contacts, your camera or your microphone, and none of the permissions above give it a quiet way to start.
This list was read off the merged manifest of an actual release build rather than off the source, because a library can add a permission to an app without its author writing a line.
Who can see what
Only members of your own household, and this is enforced by the database rather than by the app hiding buttons. A request for another household's data returns nothing, even when it is made directly against the API with a valid account.
Members of a household see everything in it: the shopping list, the calendar, the dinner plan, the saved recipes, and the member list.
Nobody else. Homey has no public profiles, no sharing outside a household, and no way to look up a person.
Where data is stored
Supabase (PostgreSQL), in ap-northeast-1 (Tokyo, Japan).
Supabase acts as a data processor; see
supabase.com/privacy. Data
travels between your devices and Supabase over an encrypted connection,
including the live updates that make a change on one phone appear on
another.
Nothing is stored anywhere else. One service is reached without storing anything: Google Places, which is asked to complete an address while it is being typed, and answers with suggestions. It is sent the characters typed into that one field and nothing else — no account, no household, no name, and none of the other things on the calendar. The request is made by our server rather than by your phone, so Google is not handed your device's address either. See policies.google.com/privacy.
How long it is kept
- Shopping items stay until someone removes them, or until the finished shop is cleared.
- Calendar entries, dinners and recipes stay until someone in the household changes or removes them.
- Deleting a household deletes its lists, items, calendar, dinners and recipes with it.
Deleting your account
In the app, open You from the top corner and choose Delete account. Your account, your display name and your sign-in go straight away; there is no grace period and no undo. If you no longer have the app installed, ask at our account deletion page, or write to juamandudz1590@gmail.com from the address you signed up with, and it will be done within 30 days.
A household is deleted along with its last keyholder. If you are the only keyholder of a household, deleting your account permanently deletes that household for everyone in it — its shopping list, calendar, dinners and recipes. The app names every household this affects, and says how many other people lose it, before you confirm.
A household nobody owns could never be renamed, handed on or cleared up again, which is why one is not left standing; to keep a household, make somebody else a keyholder first. Where a household survives, what you added to it stays and simply loses your name — the shopping still belongs to the people still shopping.
Ordinary encrypted database backups may hold a copy of deleted data for up to 30 days before they age out. They are never read except to recover from failure.
Security
- Every table is protected by row-level security, written so that the database refuses the request rather than trusting the app to ask nicely. There is a test suite of 39 assertions whose only job is to prove those rules hold.
- Passwords are handled by Supabase Auth and never stored in readable form.
- Attribution — who added an item, who ticked it off — is stamped by the database from your session, never accepted from the app.
- The key that can bypass these rules exists only on the server, and is never shipped inside the app.
Your rights
Depending on where you live you may have the right to see, correct, export or delete your data, and to withdraw consent. Write to juamandudz1590@gmail.com and we will respond within 30 days.
Changes
If this policy changes in a way that affects what is collected or who can see it, the app will say so before the change takes effect.
Contact
Homey is run by Ricci Juaman, an individual in Australia, not a company.