Android Private — Data handling

This is Michael's private gateway between his connected AI client and his Android phone. It exposes screen inspection, app discovery and UI interaction, including taps, scrolling and text entry. The same UI controls can cause messages, orders or purchases in an app; the AI client must act within Michael's explicit task instructions.

Requested screen text, screenshots, app names and interaction parameters pass through Michael's DigitalOcean server to the connected AI service. For ordinary UI operations the gateway does not store screen contents, screenshots, typed text or tool-response bodies. Request-body and access logging are disabled in the supplied deployment. The AI service and apps on the phone handle their own data under their respective settings and policies.

When explicitly requested, the video feature records a short fragment of Instagram with device audio and no microphone. The owner-approved Movies folder is read-only to the MCP app; the cloud gateway fetches only the new recording identified during that capture. A separate private worker on Michael's DigitalOcean server extracts sampled frames and automatically transcribes speech locally. Downloaded video, audio and processing intermediates are removed after processing; resulting frames and transcripts are retained for at most 15 minutes and are sent to the connected AI service when requested. Original recordings remain on the phone.

The phone temporarily serves the captured file using an unguessable private download URL which expires after one hour. The gateway keeps this URL out of tool results and logs. If the phone loses connectivity during recording, automatic stopping may not be confirmed; the owner can stop Screen Recorder on the phone.

The server stores the Android endpoint and bearer credential in its private configuration. That credential is not included in the plugin package. OAuth client metadata, consent grants, hashed tokens and their expiry/revocation state are stored to operate authentication. Access tokens expire after 15 minutes; refresh tokens expire after 30 days and rotate on use.

Only the owner can approve a connection using the owner password. Connections can be reviewed and revoked on the owner page. Revocation stops that OAuth connection; it does not erase records already held by the AI service or apps on the phone. Stopping the MCP server on the phone prevents further phone access.