Privacy & play notes
Small hands.
Minimal data.
Pressaroo is designed as a supervised cause-and-effect toy, not a social service. The play surface asks for no child identity and keeps the interaction engine in the browser or app.
During play
- No account, sign-in, advertising, payments, or external links.
- No child name, birthday, photo, location, microphone, or camera.
- No gameplay analytics, session replay, or individual keystroke history sent by Pressaroo.
- Mode, world, reactions, and the local session recap stay in the active app session.
What the device may keep
- The browser may cache app files so a returning family can reopen the toy offline.
- A short-lived session flag may help recover from a stale app update; it is not a play record.
- Audio, speech, and reaction state are released when the session ends.
What the network may still do
Opening a hosted website necessarily creates ordinary technical requests. The hosting, browser, device, and network providers may process operational data such as request timing, IP address, or security logs under their own policies. Pressaroo does not add a child profile, ad network, analytics SDK, or gameplay upload on top of that infrastructure.
Device limits are reported honestly
The grown-up handoff checks the current browser or native shell and reports whether fullscreen, Keyboard Lock, or native window controls are available. The Mac desktop app can filter shortcut keys during play after a parent grants Accessibility permission. It does not record or send those keys. The filter ends with the session and releases if the play screen stops responding. Power controls, system gestures, and other displays remain outside this protection. Browser play and the current Windows/Linux builds cannot block all system shortcuts.