Partners, OEM, API/SDK

OEM licensing for devices, white-label instances under a partner brand, and API/SDK embedding. All are planned.

Only limited information from consented families and an allow-listed set of events.

Precise child location, AI companion conversations, health or psychological inference, advertising use, data resale and creating child accounts are all prohibited.

• No direct access to child data.
• Safety and privacy defaults cannot be changed.
• No certification may be claimed unless approved.

Public API, client SDK, server SDK, white-label and OEM licensing are all planned. No sandbox or SLA is available yet.

The path from interest to technical review and enquiry, with its constraints. Only the enquiry form is open.

1. 1
   Interest: clarify the goal

   Why: to judge where the fit is real. How: set out product, region and roles. You get: a shared requirements view. We cannot: hand over an API immediately or guarantee revenue or volume.

2. 2
   Technical review: wait for the sandbox

   Why: to test feasibility. How: wait for the public API, SDK and sandbox. You get: a place on the roadmap. We cannot: share unpublished specs or guarantee a live service.

3. 3
   Enquiry: get an intake record

   Why: so the conversation is trackable. How: submit the enquiry and receive an intake record. You get: a trackable intake. We cannot: promise selection or proceed without telling you.

Partner capabilities are labelled planned; only the enquiry form is open.

• Public partner APIPlanned
• Client and server SDKPlanned
• White-label instancePlanned
• OEM device licensingPlanned
• Sandbox and docs portalPlanned
• Partner enquiry intakeAvailable