OpenMob safety

The full version, with approvals, permission modes and data handling, is docs/safety.md in the OpenMob source. This page covers what your phone's app links to.

Faster mode

Off by default. While it's on, OpenMob may send small screenshots (768 px) of what the agent is looking at to TypeSafe (Jev), a second AI service, to recognise screens faster: on screens with no readable text (games, canvas pages) and on sparse game screens (a few labels around a play area a game draws itself), a loading screen is waited out without asking the main model, and the wait ends as soon as the screen is ready.

Sparse screens are games only. A screen with a few labels counts as sparse only in a game: an app whose package name says it is one (a "game" package, chess, Tetris, sudoku, solitaire, or a known game maker such as Supercell or King), an app on the server owner's games list, or a screen drawn by a game engine (Unity, Unreal, Godot, Cocos). Any other app's labeled screens are never sent: not video calls, photo editors, notes, browser pages, Google Lens or video players, and never camera, photos, messaging, email, social, contacts, files or document apps, or account sheets. The cost: a canvas outside a game, such as a browser game in Chrome or a drawing app, gets no Faster mode on its labeled screens, and neither does a game OpenMob doesn't recognise until it is on the games list.

Jev taps. On a game's menu, pop-up or game-over screen, Jev may also tap a routine control (Play, Continue, a pop-up's X) without the main model. For that, your request's text goes to TypeSafe with the screenshot. Jev never taps when the screen shows a price, money or confirm words, an offer, an ad, a reward or in-game currency anywhere on it; at most 3 in a row; and each tap goes through the same checks, and the same phone gatekeeper, as any other tap. A tap that leaves the game counts as a miss. Never in drive sessions, Ask every step or Plan first, and Jev never finishes a task.

Faster mode sends screenshots of what the agent is looking at to TypeSafe, a second AI service, so it can recognize screens faster. On routine game screens, TypeSafe may also tap a start, continue or close button itself, through the same checks as the agent's taps; for that, your request's text goes with the screenshot. Banking, wallet and password apps, and screens the phone blacks out, are never sent. OpenMob blocks banking apps and detected card and ID numbers, but it can't recognize every sensitive image. You can turn this off at any time.

Approvals given before 2026-10-17 count as off. The warning grew (Jev taps, the request text), so turn Faster mode on again on the phone, and approve drive keys again, to keep using it.

• Only you turn it on, on the phone, in the OpenMob app's Faster mode card, with your screen lock: Turn on for this session or Always on this phone. An API key, the dashboard, a drive client or the server's settings can't turn it on.
• This session only lasts until you disconnect (the app's Disconnect or the notification's Stop) or the phone has been idle for an hour (no task or drive session). A network blip of up to 5 minutes keeps it on, once the phone re-confirms the grant you signed.
• Always on this phone lasts until you turn it off or disconnect (the app's Disconnect or the notification's Stop). A network drop or a restart keeps it on.
• Turning it off is one tap, no lock: in the app, on the ongoing notification ("Faster mode is on" → Turn off Faster mode), on the dashboard, or over the API. It takes effect from the next look.
• Never sent, even when it's on: banking, payment, wallet and password-manager apps and any app blocked for the task; black or secure screens, unidentified windows and system dialogs the phone hides; the lock screen; screens with a password field; screens whose text shows a card number, a Social Security number or a one-time code; the notification shade; and screens with readable text, except sparse game screens. Camera, photos and gallery, messaging, email, social, contacts, files, document and PDF apps, Google Play services and account sheets are never treated as sparse game screens, and neither is any app that isn't a game (see above).
• A server without OCR sends nothing. Before an image goes out, the server reads the screen's words to check for card and ID numbers. A server that can't (OCR is macOS-only today) never sends one; the dashboard says "Faster mode is on but inactive on this server".
• Drive sessions (an outside agent at the controls) send nothing unless you approved that API key on the phone, with your screen lock.
• Every change is logged, with who and when, and every step records whether a screenshot went to TypeSafe.
• What it can't promise: the server enforces all of this. A compromised server could ignore it and send screenshots anyway, as it could with any screenshot it handles.