UrusFamily privacy notice
UrusFamily stores family data only to run the app. We show no ads and never sell data. Kid profiles are created by a parent or guardian who gives consent. You can access, correct or delete your data at any time under Malaysia's Personal Data Protection Act 2010.
What are your rights under PDPA 2010?
- Access: ask for a copy of your personal data, or export family data from Settings.
- Correction: fix data in the app, or ask us to correct it.
- Withdraw consent: delete your account or, as owner, delete the family.
- Send requests to privacy@urusfamily.com. We reply within 21 days.
Which third parties do we use?
| Supabase | Database hosting, sign-in and storage, in the Singapore region. |
|---|---|
| Google Sign-In | Only if you choose to sign in with Google. Shares name and email. |
| Sign in with Apple | Only if you choose to sign in with Apple. Shares name and email. |
| Google Play and App Store | Process purchases. We never receive card numbers. |
No ad SDKs, third-party analytics or trackers. Usage and error records stay in our own database.
What stays on your phone?
- Documents vault files stay on the phone that holds them and are never uploaded.
- Private notes are encrypted on the phone with a key we do not hold.
- A saved email and password stay in the phone Keychain or Keystore.
Full notice
The text below is the same notice shown in the app.
Who we are
UrusFamily is a family app for housework, points and shared goals. For the data you keep in the app, UrusFamily is the data user under the Personal Data Protection Act 2010 (Act 709).
This notice explains what data we process, why, who can see it, how long it is kept and your rights.
What we store
Account: email and password (stored hashed, we cannot read it). If you sign in with Google or Apple, that provider shares only your name and email with us, never a password. Apple private relay emails work too.
Family: the family name, each member's display name and avatar, role, daily target, profile PIN (hashed), and a birthday if you enter one.
Activity: chores, points, badges, goals, the virtual wallet, grocery lists, notes, the calendar and other features your family switches on.
We do not collect GPS location, biometrics, phone contacts, or a child's email or phone number.
Purpose
Data is used only to run the app for your family: showing chores, counting points, syncing between family members' phones, sending the reminders you choose and supporting your account.
We never use family data for advertising and never sell it to anyone.
Children's data and parental consent
Kid profiles have no account or email. A kid profile is created only by a parent or legal guardian, who consents on the child's behalf. The date and time of that consent is stored on the kid profile.
Kid screens show no ads and send no child data to third-party analytics tools.
Disclosure
Family data is seen only by your family members, according to their role. For example, extended family do not see wallets or notes.
We disclose data to service providers who run the app for us, such as database hosting, under contracts that require confidentiality. Where servers are outside Malaysia, we only use providers with comparable data protection.
We do not disclose data to anyone else unless the law requires it.
Storage and retention
Data is kept while your family or account is active. When the owner deletes the family, data is removed from the main database immediately and from backups within 30 days.
After deletion we keep only anonymous counts (number of members and the age of the family) as proof the deletion happened.
We do not keep photos. A chore proof photo is deleted as soon as it is checked, and at most 72 hours after upload. A share proof screenshot is deleted after it is reviewed, and at most 14 days after upload. Documents vault files never leave the phone that holds them and are never uploaded to our servers. Only the title, type, whose document it is, expiry date, reminder, note and the name of the phone holding the file sync to parents. If the app is deleted, the files on that phone are lost.
Daily ibadah logs are kept for 13 full months, then combined into monthly totals for each member and the daily logs are deleted. A hafazan teacher's name is kept only on the phone that recorded it.
Other records are kept only as long as they are needed, then deleted automatically: "Sampai rumah" check-ins after 7 days; invites 30 days after they expire or are used; app usage and error records after 90 days; problem reports 180 days after they are handled; referral link opens after a year; a rejected or withdrawn share post link after 90 days. Usage and error records carry only a random app id that changes every year, never your name or email.
For affiliates, bank details are asked for only when a payout is due. The account number is deleted after 90 days without payout activity, and the name and MyKad number are deleted 15 months after the tax form (CP58) deadline for the last payout. Payment records with no family details are kept for 7 years because tax law requires it.
Security
Data travels over encrypted connections. Each family is isolated on the server, so other families cannot read your data.
Private notes (notice details, family meeting outcomes, house rule consequences, hafazan notes and task notes) are encrypted on your family's phones with a key that is never sent to us, so we cannot read them. Only parents hold the recovery code. If every phone and that code are lost, those notes cannot be recovered.
Access and correction
You can view and correct most data directly in the app. Parents can export a copy of the family data from Settings.
You can also ask for access or correction by email. We will reply within 21 days.
Your choices
You can withdraw consent at any time by deleting your account or, for the owner, deleting the family. Without consent we cannot run the app for you.
Contact us
For questions, access or correction requests, or complaints about personal data: privacy@urusfamily.com
Changes to this notice
If this notice changes in substance, the app will ask for your consent again. If the BM and EN versions differ, the BM version applies.