1. Caregiver access
New caregiver accounts are incomplete, unverified and unavailable by default. The API requires onboarding and administrative approval before a caregiver can become available or receive an assignment. Public caregiver results contain only verified profiles and indicate whether each caregiver is currently available.
2. Booking privacy
Open requests expose the city, area, schedule, duration, child count/ages and limited pets/CCTV/other-adult signals to eligible caregivers. They do not expose the parent name, booking notes or exact address. After assignment, the caregiver receives the care address, whether it matches the verified home, any different-location explanation and relevant household safety disclosures—but never the parent's NIN, proof document or emergency-contact details.
3. Booking integrity
Booking creation, caregiver reservation and the full wallet-to-escrow hold happen in one database transaction. Eligible open requests must have held funds. Assignment requires verified status, current availability, matching city and no conflicting active booking. Status changes are restricted to the assigned caregiver and must follow the order assigned, en route, arrived, in progress and completed. Each transition creates a tracking event, and completion releases escrow atomically.
4. Location
The API accepts caregiver location events only while an assigned booking is in the en-route state. The current browser interface does not collect background location automatically.
5. Limits
Technical controls reduce unauthorised access but do not guarantee caregiver conduct or eliminate childcare risk. Camera monitoring, automated emergency response and a staffed in-app safety channel are not currently provided.