A companion robot went silent when its maker closed

What happened

A companion product's continuity depends on more than the device or account surviving. Moxie Robots, the community site now running the child companion robot Moxie, states on its story page that maker Embodied Inc 'shut down' in 2024, after which 'Moxie slept' for roughly a year because the robot depended on the company's cloud service to function. Inflection AI's The Future of Pi, dated 26 August 2024, describes a different outcome after its own strategic pivot toward enterprise AI: the company states it remains 'committed to keeping consumer Pi available and free', while planning to 'implement a cap on message volume for free users'.

What the documents show

Moxie's cloud dependency meant that when its maker stopped operating, the physical device itself went silent, with no continued function documented until a separate community effort restored a pairing service roughly a year later. Inflection's post shows a company narrowing a product's scope, capping usage, while explicitly stating a user 'should continue to have access' to existing conversations, a materially different outcome from a companion going silent entirely. Character.AI's own terms of service add a third data point: the company 'reserves the right' to change its data-retention practices 'at any time' and states it has 'no responsibility or liability' for data loss.

The mechanism

A cloud-dependent companion, whether a hardware robot or a chat app, stores its personality data, memory and conversation history on the company's own servers rather than on the user's device. When that company stops paying for or operating those servers, the companion stops functioning regardless of whether the physical hardware or the app itself still exists, unless a separate party operates a replacement backend, which is what the Moxie community site describes doing after roughly a year.

What it leaves open

None of these documents states how much advance notice, if any, users typically receive before a shutdown, or whether an export was offered to Moxie or Pi users before either company changed course. That is a gap in what these specific documents record, and any broader claim about the industry from it would be editorial, not documented.

• Does the company's terms of service disclaim responsibility for data loss or discontinuation?
• Is any user data or personality profile stored locally, independent of the company's servers?
• Has the company, or a successor, published a continuity or export plan before a shutdown happens?

A companion that depends entirely on a remote server is only as durable as the company willing to keep paying for that server, a fact these three documents illustrate from three different positions: a full stop, a narrowing, and a standing disclaimer.