Oneira can connect to services you choose, which means privacy depends partly on choices outside the hardware. Before linking an account or tool, identify the data, destination, permission, retention, cost, and exit path. A connection should be understandable before it becomes convenient.
Name the data and destination
Ask what leaves the device or app: a frame, audio, text request, account identifier, tool result, or another record. Then identify every operator that receives it, including JML and any selected connected service. Avoid vague diagrams that collapse several companies into one cloud icon.
Review permission, retention, and cost
Check whether the tool can read or write, which account it can access, how long each operator keeps data, and whether activity trains a model. Confirm rate limits, subscription terms, and usage fees. Hardware purchase does not automatically include unlimited access to every third-party service shown as compatible.
Test the stop path before trusting the start path
Learn how to remove a connection, review service data controls, disable a mode, and report unexpected activity. Begin with a low-risk task and check the result. A system is not truly user-controlled if connecting takes one tap but disconnecting requires guesswork.
The short version
- List every operator that receives data from a connected request.
- Check permissions, retention, training use, limits, and fees.
- Verify the revoke and disconnect flow before granting sensitive access.