The short version
Everything your robot produces passes through, and is stored on, a server operated by one person. That is the honest position: unlike a self-hosted install, this is not "your data never leaves your house" — it leaves your house, and it lands here.
What is promised instead: it is not sold, not shared with advertisers, not used to train anything commercial, and not looked at except when you ask for help or when something is broken. You can delete all of it, at any time, from the console.
If that trade is not acceptable to you, that is a completely reasonable position — and the software is open source precisely so you can run it yourself and keep everything at home.
1. Who holds your data
Your data is held by the operator of jibo.io, on a rented virtual server. It is not held by Jibo, Inc. or any successor, and it is not held by a company — there is no company.
2. What this instance stores
- Account details — your email address, a hash of your password, your name as you entered it, and the loops you belong to.
- Robot registration — your robot's identifiers and credentials, so it can authenticate.
- Content your robot creates — photographs it takes, messages recorded for household members, and the answers people give to its questions.
- Voice turns — audio sent for transcription, and the resulting text.
- Operational logs — connection records, request paths, errors, and IP addresses, kept so the service can be debugged and abuse can be identified.
3. Voice, and how turns are processed
When your robot hears its wake word, it streams audio to this server. That audio is transcribed, a response is chosen, and speech is synthesised back. Transcription runs on hardware controlled by the operator of jibo.io, not on a commercial speech API.
Audio is retained only as long as needed to produce and debug the turn. It is not kept as a permanent archive of everything said near your robot.
4. Cookies and local storage
One session cookie, so the console knows you are signed in. A local-storage entry for your light/dark theme preference. The public website and console also use Google Analytics 4 for aggregate usage measurement; it may set analytics cookies. Google signals and ad personalization are disabled.
5. Third parties in the path
Three: two infrastructure providers and one analytics provider:
- The hosting provider for the server itself, which necessarily has physical access to the machine.
- Cloudflare, which proxies the website and therefore sees requests to it, as a defence against abuse. Robot traffic to the API is DNS-only and does not pass through it.
- Google Analytics 4, which receives aggregate website and console page views. Query strings and hash fragments are removed before an event is sent; no account, robot, household or robot-content fields are included.
The infrastructure providers are not given your content for their own purposes. Google Analytics is not used for advertising or ad personalization.
6. No robot telemetry
jibo.io does not send robot audio, transcripts, photographs, messages, household records or account contents to Google Analytics. The public website and console use it only to measure aggregate page views with a sanitized origin and path.
7. Other people in your household
A robot is a shared device in a shared room. Anyone in your loop can see the photographs it took, the messages left on it, and the answers people gave it. Anyone physically present can talk to it. Treat a loop as a household, not as a private account.
8. Children
Jibo was sold as a family device and children will talk to it. This service is not directed at children and does not knowingly create accounts for them; the account holder is the adult responsible for the household.
If a child's recordings or photographs are on this instance and you want them gone, delete them in the console or email [email protected] and they will be removed.
9. Retention and deletion
Content stays until you delete it. Deleting a photograph, a message or your account removes it from the live service; backups age out on their own cycle, so a short window may exist where a copy survives in a backup that has not yet rotated.
Operational logs are kept only as long as they are useful for debugging and abuse handling.
Google Analytics retention is controlled in the operator's Google Analytics property. It receives aggregate website events, not robot or household content.
10. Your rights
Depending on where you live you may have statutory rights to access, correct, export or erase your personal data. Regardless of jurisdiction, this service will honour those requests — email [email protected]. There is no legal department to route it through; it is one person reading the mail.
11. Security
Traffic is encrypted in transit. Passwords are stored hashed, never in plain text. Robot credentials are held so the robot can authenticate, and are never shown in full in the console.
Be realistic about the threat model: this is a hobby service on a single server, not a hardened commercial platform with a security team. It is maintained carefully, but it has not been independently audited. See Security for how issues are handled.
12. Changes
Material changes will be noted here with a new "last updated" date.