ScreenSync MCP Privacy Policy

Plain-language summary: ScreenSync MCP is designed to be LAN-first and privacy-first. Your screen captures stay on your phone and your own computer, with two exceptions you control: the optional Google Drive fallback (§6), and screenshots that an AI agent you connect requests, which go to that agent's model provider (§9). We (EpsolDev) do not operate cloud servers that receive, store, or view your screen data. There are no ads, no trackers, no analytics SDKs, and no sale of data — ever.

1. Scope of this Policy

This Privacy Policy applies to the ScreenSync MCP Android application ("the App"), the ScreenSync MCP hub software that you run on your own computer ("the Hub"), the ScreenSync MCP browser extension for Chrome and Edge ("the Extension"), and this website (www.screensyncmcp.tech) ("the Site"), all published by EpsolDev ("we", "us"). By installing or using the App, Hub or Extension you agree to this policy.

2. What Data the App Handles

The App handles the following categories of data. "Handles" means processed on your device or transmitted between your devices — not sent to us.

We collect nothing. EpsolDev has no server that receives any of the above. We cannot see your screens, your captures, your device, or your usage.

3. Screen Capture & Consent (MediaProjection)

Screen capture uses Android's official MediaProjection API, which requires your explicit, system-level consent:

• Android shows a system dialog before any capture session can begin. The App can never capture your screen without this consent.
• A persistent system notification is displayed while a capture session is active, as required by Android.
• You can end the capture session at any time from the notification, the app, or the floating bubble.
• Captures are only taken when you trigger them (bubble tap, shake gesture, in-app button) or when an AI agent you connected requests one through your own Hub.

4. Permissions the App Requests, and Why

The App requests no access to contacts, call logs, SMS, location, microphone, or files outside its own storage.

5. LAN Transfer, the Hub & the Browser Extension

• Frames travel from your phone to the Hub over your own local network (HTTP on port 3000 by default).
• Every request is authenticated with a bearer token generated during pairing. Devices without the token are rejected.
• The Hub runs on hardware you own and control. Captures it stores live in its local data directory on your computer, and you can delete them at any time.
• The Hub exposes captures to AI agents only through the Model Context Protocol connection you configure (stdio) — it is not reachable from the public internet unless you deliberately expose it.
• The Extension talks to the hub address you give it (your own computer, port 3000 by default) and sends the pairing token with every request. On its own, the only other request it makes is fetching the public setup guide, a static file on www.screensyncmcp.tech, which our web host logs like any page visit (§13). Pages it opens or fetches for an agent are requests that agent asked for.
• The Extension keeps the hub address, pairing token, per-site permissions, a log of agent actions, and your browser profile's email address and name in the browser's local extension storage on your computer. The profile email and name are shared with your own Hub so it can tell your browser profiles apart. Display preferences (theme, reduced motion, approval chime) may sync through your browser account if browser sync is on.
• While web access is on (it is on for new installs; one toggle or Alt+Shift+S turns it off), a connected AI agent can, through your Hub, take screenshots of your tabs, read page content and act on pages. Its tools can also read browser data such as history, bookmarks and cookies when the agent asks for them. Risky actions on sites you have not trusted wait for your approval, and browser-internal pages are refused.

6. Optional Google Drive BYOS ("Bring Your Own Storage")

• Drive sync is off by default. It exists as a fallback for when your phone and hub are not on the same network.
• If you enable it, you sign in with Google OAuth and grant the App scoped access to upload capture files to your own Google Drive.
• Files go directly from your phone to Google's servers under your account. EpsolDev never receives or proxies them and has no access to your Drive.
• Google's own Privacy Policy governs data stored in your Drive. You can revoke the App's access anytime at myaccount.google.com/permissions and delete the synced folder.

7. Local Storage & Retention

• Captures and thumbnails are cached in the App's private storage and indexed in a local SQLite database.
• Retention is entirely under your control: delete individual captures in the Gallery, clear all history in Settings, or uninstall the App to remove everything it stored on the phone.
• Captures stored by the Hub on your computer remain until you delete them (see the Hub's data folder).
• The Extension's stored settings and action log remain until you remove the Extension, which deletes them.

8. Third Parties, Analytics & Ads

• No analytics SDKs. The App contains no Firebase Analytics, no crash-reporting beacons, no advertising identifiers.
• No ads. The App is ad-free.
• No data sale or sharing. We have nothing to sell — the data never reaches us.
• Apart from the AI agent you choose to connect and its model provider (§9), the only third party involved is Google, and only if you opt into Drive BYOS (§6) or use Google Sign-In.

9. AI Agents You Connect

ScreenSync MCP's purpose is to let an AI agent of your choice view and control your phone and, with the Extension, your browser. Important consequences:

• When your agent (e.g. Claude or another MCP client) requests a screenshot, that image is delivered to the agent — and therefore to the AI provider that operates it, under their privacy terms. The same applies to page content, browser screenshots and browser data the Extension returns to the agent.
• You choose which agent to connect, and you can disconnect at any time by stopping the Hub or toggling the connection off in the app.
• Be mindful of what is on screen when an agent is connected — treat a connected agent like someone looking over your shoulder, because that is exactly the product promise.

10. Security

• Bearer-token authentication on every phone ⟷ hub request.
• LAN-scoped traffic by default; nothing is exposed to the internet by the App or Hub out of the box.
• App-private storage (Android sandbox) for captures and settings.
• No security measure is perfect: protect your Wi-Fi network with a strong password and keep the token secret (regenerate it from the Connect Kit if leaked).

11. Children's Privacy

ScreenSync MCP is a developer tool, not directed at children under 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal information from children — indeed, we do not collect personal information at all. If you believe a child has used the App inappropriately, contact us.

12. Your Rights (GDPR / CCPA & similar)

• Access / portability: all data is already on your devices — you can inspect the SQLite history and hub data folders directly.
• Erasure: delete captures in-app, clear the hub data folder, revoke Drive access, remove the Extension, or uninstall.
• Objection / restriction: since we perform no server-side processing, there is nothing on our side to object to; you control all processing locally.
• If you have any privacy request or question, email us and we will respond within 30 days.

13. This Website

www.screensyncmcp.tech is a static site. It sets no tracking cookies. Fonts and icons load from Google Fonts and CDN providers, whose standard server logs (IP address, user agent) are governed by their own policies. We do not run analytics on this site.

14. Changes to this Policy

If we change this policy we will update the "Last updated" date above and, for material changes, note it in the App's release notes. Continued use after changes constitutes acceptance.

15. Contact

EpsolDev · epsoldev.com · info@epsoldev.com