About this policy
Last updated: 14 November 2026. This notice covers Chorably: Family Chores, including the current private beta. The beta is for testing with invented child nicknames and chore details; it is not an invitation to enter real children's information before the release checks are complete.
Who is responsible
Chorably is operated by Frans le Roux, trading as Nexlogic, in South Africa. For privacy questions, access, correction, objections or deletion requests, email admin@nexlogic.co.za. The Google account used to administer the Play Store listing is separate from this public contact address. This notice applies to Chorably; other Nexlogic services have their own notices.
Parents and children
An adult creates or joins a family and controls which people and phones can connect. Only a parent, guardian or other person legally authorised to act for a child should add that child or provide their information. Children connect using a parent-approved QR code or short code and do not need a Google sign-in inside Chorably. Google Play may separately require a Google account to install the app. A routine label may reveal health information if you enter it; Chorably is a general routine tracker, not a medical record or clinical monitoring service. Use a nickname and provide only what the family needs; do not enter identity documents, addresses, diagnoses or unnecessary sensitive information. Ask us about a child's information if you believe it was provided without appropriate authority.
Information Chorably processes
Parents can sign in with Google or a verified email address and password. Google sign-in provides an account identifier and verified account information for authentication and invitation matching; we never receive your Google password. Email/password sign-in uses Google Firebase Authentication, which processes your email address, password credentials, verification and password-reset requests. Firebase retains authentication records, including the email address and protected password representation. Chorably does not retain the password on its own server or in its saved family data. We retain a provider-specific account identifier and use a hashed email binding for targeted parent invitations. Adding another sign-in to an existing parent is an explicit action and does not automatically merge accounts with matching email addresses. Family setup includes child nicknames, chore and reward descriptions, selected pictures and preferences; private setup content is encrypted for the family's authorised devices before it is sent to our servers. Activity records include opaque family, member and device identifiers, assignments, schedules, completion and approval states, dates, points, bonuses, penalties and reward requests. These operational records are not all encrypted in the same way as private descriptions. Linked phones store protected local copies, pending offline actions and device credentials. If notifications are enabled, we process a delivery token, category choices and delivery records. Network connections also expose technical information such as IP addresses, request times and errors to the services handling them. If you contact support, we receive the message and contact information you choose to send. Optional in-app feedback sends only your selected bug/feature type, title, description, app version, Android platform label and a random report reference. It does not automatically attach your account, family or device identifiers, contact details, screenshots or diagnostic logs. What you type can still identify someone; do not include passwords, recovery codes, child names or sensitive family details. Feedback is recorded in our private Redmine issue tracker so we can investigate and track it.
When an adult requests to join an existing family, we process the requesting adult's verified email, the intended family creator's email for routing and delivery, a routing hash for verified creators, a device-bound request reference and an encrypted invitation reply. The creator must approve in Chorably before the existing protected connection process can grant access. A notification and optional email help the creator find the same request; opening an email or link does not approve anyone. The email contains the requesting adult's email and a non-secret request link, not child names, family content, points, passwords or family keys. Requests expire after 24 hours. Routine scheduled cleanup removes request records seven days after expiry; the delivery address is removed after mail acceptance or expiry. Family or identity deletion also removes associated request records where applicable. Encrypted backups follow the 30-day retention and deletion-replay safeguards described below.
How we use information
We use this information to authenticate adults, connect approved devices, show each family member the information they are allowed to see, synchronise chores and rewards, record points and decisions, deliver chosen reminders, recover family setup, answer support requests and protect the service from misuse. We do not sell personal information or use family data for targeted advertising. The current app has no advertising SDK, paid subscriptions or Firebase Analytics collection. Chorably does not send family content to AI services for generation or training. Planned monetisation or other new uses are not enabled by this notice; we will update the notice and obtain any required permission before introducing them.
Encryption, offline use and recovery
Private family descriptions and recovery backups are encrypted for authorised family devices. Nexlogic does not hold the private recovery code that you save outside the phone. Neither Google sign-in nor an email/password sign-in or password reset can replace that code. This does not mean that we collect no data or that all service metadata is unreadable to us. Authorised family members and anyone who can unlock a family phone may be able to view the information available to that device. Offline copies and saved actions can remain on a disconnected device until it reconnects or is cleared. Revoking access cannot recall information someone already copied, exported or photographed. Losing all authorised devices and the private recovery code can make encrypted family content unrecoverable.
Notifications and permissions
Scheduled chore reminders can run locally on a phone, including while offline. Optional push notifications use Google's Firebase Cloud Messaging. Our Firebase messages contain generic event and routing identifiers, rather than private child names, chore descriptions or reward descriptions. A linked phone can retrieve authorised activity information and add private names and details locally. Android notification settings and the phone's lock-screen settings affect what other people can see. You can change notification categories and turn notifications off. The parent may use a camera-based QR scanner to connect devices; a child does not need camera access for linking. Chorably does not request precise location or contacts and does not upload photo or video evidence of chores. Optional device PIN or biometric checks use Android's protection facilities; Chorably does not receive your fingerprint or face template.
Providers and international processing
The Chorably application service and its encrypted backups are operated on Nexlogic-controlled infrastructure in South Africa. Cloudflare handles and protects API traffic; it can process connection information and service metadata, and application-layer encrypted family content passes through it as ciphertext. Google provides parent authentication, including Firebase Authentication for email/password accounts, Google Play distribution and optional Firebase Cloud Messaging; Google can process account, device, connection and notification-delivery information under its terms. This public policy page is hosted with the Nexlogic website on Afrihost; visiting it creates ordinary website connection records. Email providers handle messages sent to our support mailbox. Google, Cloudflare and other delivery infrastructure may process information outside South Africa. Encryption does not remove the need to account for that processing. We restrict the information sent to these services to what is needed for their stated roles. Information may also be disclosed where required by law or necessary to investigate security incidents. We do not give unrelated families access to your family records.
Retention and deletion
Family setup, activity and points history are retained while needed to provide the family's service, unless removed through an authorised deletion request. A reset of test history clears the selected history while keeping setup; it is not account deletion. Uninstalling the app or disconnecting a phone also does not delete server records. Routine notification jobs have a seven-day cleanup window; inactive notification registrations expire after 90 days unless renewed. Routine encrypted container backups and database restore files expire after 30 calendar days and are removed by the next successful corresponding backup run. This is separate from the small deletion-prevention journal, which must survive old backups so deleted profiles cannot return. Retired encrypted storage blocks are reclaimed by the backup system rather than instantly overwritten. A pending in-app feedback copy expires after 30 days on the phone and in the delivery queue. Delivered reports remain in our private issue tracker while needed to resolve and document the report; request removal of identifying text through the privacy contact. Authentication records remain while needed for your account; deleting the app does not delete your Firebase account. A specific legal or security hold may require limited records to be kept longer; we will explain any applicable exception when responding to a request. Encrypted recovery setup is replaced as authorised and invalidated when a child's permanent deletion makes the old snapshot unsafe. Permanent child deletion disconnects that child's devices and removes their server-side profile, private deliveries and activity through a background process; acceptance of a request is distinct from completed deletion. Minimal opaque deletion markers and security or legal records may need to be retained to prevent restoration of deleted information, establish what was authorised, or meet legal obligations. They are not a restored child profile. A restored backup must have applicable deletions reapplied before it serves users. We cannot erase copies someone independently saved outside Chorably, or reach a disconnected phone until it reconnects.
Your choices and requests
Parents can manage linked devices, notification preferences and family settings inside the app. A family creator or explicitly authorised delegate can request permanent deletion of a child after fresh confirmation of their sign-in. For access, correction, deletion of your Chorably account or associated family data, or if you cannot use the app, email admin@nexlogic.co.za with the subject "Chorably privacy request". We will verify identity and authority before disclosing or deleting information. Do not email passwords, Google sign-in codes or private recovery codes. We will explain the scope, status and any necessary retained records; your request must not improperly erase another person's independently held account or rights. You may also raise concerns with South Africa's Information Regulator. Requests concerning Google's own account or Play records should also be directed to Google.
Changes to this notice
We will update this page when Chorably's data handling changes. Material changes will also be explained in the app where appropriate, and we will obtain consent where required before a new use. Contact admin@nexlogic.co.za if anything in this notice is unclear.
Request Chorably account or data deletion · Google privacy · Cloudflare privacy