NimnyBot App Privacy Policy

Scope and current account status

This policy applies to the NimnyBot Mobile Companion for iOS and the connected NimnyBot services it controls. It does not replace the separate Website Privacy notice for the public informational website.

The current pre-release application uses robot pairing and an authorized household-device binding. A production consumer account-registration service is not yet finalized. If account creation or additional account authentication is introduced before release, this policy and the App Store privacy disclosures will be updated before that data is collected.

Setup, pairing, and secure access

Setup may process a one-time QR or manual setup code, nearby Bluetooth signals, a selected Wi-Fi network and its credential, a home or household label, robot and household identifiers, and an owner-device identifier. Setup codes and Wi-Fi credentials are used to complete pairing and network setup and are not kept in ordinary application screens or setup history.

The application keeps the device-to-robot binding and required access credentials using operating-system protected storage so the authorized device can reconnect. Disconnecting the phone or revoking its household access removes or invalidates that binding.

Family and child profiles

An authorized owner or guardian may create and manage household profiles. These records may include a name, role, date of birth, language settings, permissions, household relationships, profile identifiers, and privacy choices. Child profiles are kept separate within the household and are subject to owner or guardian controls.

The Mobile Companion is an owner and guardian surface. It is not intended to let a child independently create a public account or publish a profile.

Learning and progress

Nimny Learning may process learner profile identifiers, Mission and activity status, schedules, progress, responses, saved work, help or attention states, and related learning context. The Mobile Companion presents parents and guardians with summaries and controls; the child Learning Web provides the larger-screen learner workspace.

Learning information is used to continue the learner's experience, show progress, provide appropriate support, and keep the robot, Learning Web, and parent view synchronized.

Conversation, microphone, and AI processing

When a person starts a voice interaction, the application may process microphone audio, conversation text or transcripts, prompts, responses, language and voice choices, and the household or task context needed for the interaction. The microphone is not used by the application for hidden background recording.

NimnyBot may use local processing or an AI provider selected by the owner. Current provider choices include local processing, OpenAI, and Anthropic. When an owner enables a cloud provider, the content needed to answer a request may be sent to that provider through the configured NimnyBot service. Provider processing and retention are also governed by the owner's provider account settings and the provider's terms and privacy notice.

If an owner enters a provider API key, the app sends it to the configured credential service, clears the entry field after the save attempt, and does not intentionally keep or display the plaintext key in ordinary app storage.

Camera, Live View, and media

The phone camera is used to scan a one-time setup QR code when the user chooses that setup method. The application receives the decoded setup value and does not intentionally retain the QR camera image.

Owner-authorized Live View may transmit video, audio, session state, and control messages between NimnyBot and the authorized device. Live View and recording state are visibly disclosed in the product. Camera, microphone, and Live controls are subject to native permissions, household authorization, and session revocation.

Tasks, routines, and connected services

Tasks, routines, reminders, approvals, and approved digital workflows may process the instruction, schedule, status, result, and authorization history needed to carry out the requested action. Consequential actions remain subject to applicable permissions and approvals.

Connected services are optional. Their availability and data practices depend on the service selected by the owner and the permissions granted for that connection. NimnyBot does not use a connection for an unrelated purpose merely because the service is available on the device.

Calendar, reminders, and contacts

With explicit operating-system permission, the application can read only the calendars and reminder lists selected by the user and can read contact names and birthdays. The current device bridge does not read contact phone numbers, email addresses, postal addresses, or notes, and it does not modify calendars, reminders, or contacts.

Bounded event, reminder, or contact fields are sent to the authorized NimnyBot household service to provide reminders and family context. The phone keeps the selected source identifiers and last synchronization time until the connection is removed. Access can be revoked in iOS settings or by disconnecting the source in NimnyBot.

Diagnostics and service information

The application and connected robot services may process app and software version, robot and device identifiers, connectivity state, permission state, battery and robot status, request and response status, error codes, timing, and bounded technical logs. This information is used to operate, secure, troubleshoot, and improve reliability of the product.

The current application dependencies do not include an advertising SDK or a third-party behavioral analytics SDK. No cross-app advertising or tracking integration is present in the current pre-release application.

Where information is processed

Depending on the feature, information may be processed on the iPhone, on the paired NimnyBot, over the household's local network, through an authenticated remote connection, or by a connected service or AI provider selected by the owner. The application uses only the information needed for the requested feature and its security, status, and recovery requirements.

Retention and deletion

The product does not apply one universal retention period to every category of information. Device bindings and local preferences remain until they are removed, revoked, reset, or replaced. Household profiles, learning records, tasks, routines, recognition data, and connected-service data remain only as needed for the enabled feature, household continuity, security, and applicable legal obligations.

Where available, an authorized owner or guardian can disconnect a phone, remove a connected source, revoke native permissions, delete recognition data, remove a family member's robot data, or request deletion of learner work. External providers may retain information under their own account settings and policies.

Your choices and requests

You can decline optional permissions, revoke them in iOS settings, remove optional connections, and stop using remote or cloud-provider features. Some core functions may be unavailable when required permissions or an authorized robot connection are absent.

To ask about access, correction, deletion, or another privacy matter, use the official Contact page. A request may require verification that the requester is authorized for the relevant household or profile.

Security

NimnyBot uses safeguards appropriate to the supported flow, including operating-system protected credential storage, authenticated connections, and encrypted transport. No method of storage or transmission is completely secure, and product safeguards will continue to be validated as the engineering prototype progresses.

Changes to this policy

This policy may be updated as the application, connected services, or legal requirements change. The effective date above identifies the current version. Material changes will be reflected here before the affected release or data practice is introduced.