Your project data should have a clear purpose.

Account details can include your name, email, country and preferred contact method. An onboarding brief can include location interests, budget band, timeframe, phone or WhatsApp details, requested services and information you choose to provide.

Once an authorised project exists, the workspace can hold project membership, messages, documents, decisions, notifications, milestones, project updates, budgets, payment schedules, readiness checks, maintenance requests, care information and handover or snag records.

They are used to respond to enquiries, qualify a requested property journey, provide authenticated project access, maintain a project record, support decisions, coordinate delivery activity and preserve evidence relevant to the client relationship.

Where consent is specifically requested, the interface records that consent. Other processing may depend on steps you ask us to take, delivery of an agreed service, legitimate operational needs or legal obligations applicable to the eventual contracting entity.

Project data is protected by authenticated access and database row-level security. Project members only receive records that their account is authorised to access. Private project files use non-public storage and temporary signed links rather than permanent public file URLs.

No online system can promise absolute security. Clients should use a strong unique password and should not upload information that is unrelated to the property or service journey.

Information may need to be shared with authorised project participants or professional/service providers involved in the project. Access should be limited to what is necessary for their role. A professional appearing in a workflow is not automatically instructed or retained merely because their role is shown in the platform.

Project and enquiry records should be retained only for as long as required for the client relationship, operational evidence, dispute handling and applicable legal obligations. A final retention schedule must be adopted by the contracting entity before scaled live onboarding.

For access, correction or deletion questions, email hello@mukoko.studio or use the secure project inbox if you already have a My Kumusha project. Where a request cannot lawfully or safely be completed immediately—for example because a project record must be preserved—the reason should be explained.