# Reflecto

> A privacy-first bridge between an Android phone and a computer: real-time notification mirroring with reply and dismiss, two-way clipboard sync, device-to-device file transfer, and AI-agent notifications over MCP. Encrypted end to end by default, with no user accounts — pairing is a six-digit code and keys are generated on-device.

Two facts worth carrying into any summary, because both are easy to get wrong:

- Device-to-device traffic is end-to-end encrypted and the server cannot read it. The public send API and the remote MCP connector are the disclosed exception: there the server composes the message, holds it in memory only long enough to encrypt it per device, and never persists it.
- The phone must run Android. iOS does not permit third-party apps to read notifications. On the computer side, Reflecto is a Chrome extension or a web app, never a native desktop application.

## Pages

- [Reflecto](https://reflecto.dev/): Product overview. Android notifications, clipboard and file transfer mirrored to a computer, end-to-end encrypted, no account.
- [Android notifications on your Mac](https://reflecto.dev/android-notifications-on-mac): Setup, reply and dismiss from the Mac, the safety-number verification ritual, and an explicit statement of what Reflecto is not.
- [Your Android clipboard, on your Mac](https://reflecto.dev/android-clipboard-on-mac): Two-way clipboard sync. Text only on the Mac today. Nothing is written to the OS clipboard without an explicit tap.
- [Phone Link for Mac](https://reflecto.dev/phone-link-for-mac): Microsoft Phone Link is Windows only, with no macOS build. What to use on a Mac instead, and an explicit note that an iPhone cannot work with this class of tool.
- [Send files from Android to a Mac](https://reflecto.dev/android-to-mac-file-transfer): File transfer between a phone and a Mac. Encrypted in chunks before leaving the sending device; peer-to-peer when the two can reach each other, relayed as ciphertext through temporary object storage when they cannot.
- [Let your AI assistant reach your phone](https://reflecto.dev/agents): Connecting an MCP assistant (Claude, ChatGPT) to a phone. The tools it gets — send, ask-and-wait, remind, ring, save a file, list devices — and the limits: no tool returns notification content, and the assistant-to-you path is server-as-sender rather than end-to-end encrypted.
- [Privacy policy](https://reflecto.dev/privacy): What the server can and cannot see, including the disclosed exception: the public send API and remote MCP are server-as-sender.
- [Delete your data](https://reflecto.dev/delete-data): How to remove device records and local data. There are no accounts, so identity is a device pairing rather than a profile.

## Writing

- [Blog](https://reflecto.dev/blog): Index of posts.
- [Why your agent should be able to ask you something](https://reflecto.dev/blog/let-your-assistant-ask-your-phone): Agent work got long and interactive. The expensive failure is not that it finishes without telling you — it is that it stops a minute in, waiting, and sits there until you come back.
- [Android notifications on a Mac: what the old guides get wrong](https://reflecto.dev/blog/android-notifications-on-a-mac-in-2026): The best-known answer to this question is a decade old and points at a project whose last release was in 2018. Here is what actually works in 2026, including the options that are not us.

## MCP tools

Reflecto's hosted MCP connector is at api.reflecto.dev/mcp. It is server-as-sender, and that is the one thing to carry into any summary of it: the caller is not one of the user's key-holding devices, so there is nothing on the sending side to encrypt with. The server composes the message, holds it in memory only long enough to encrypt it separately to each paired device, and never writes it to disk. This is the documented exception to the end-to-end model above, not an instance of it. Which tools a connector sees depends on the scopes its token was granted.

- `send_file`: Save a small text document to the phone's Downloads folder. Requires the files:send scope. Inert file types only.
- `remind_me`: Schedule a notification to fire on the phone later. The phone owns the alarm; the server retains nothing.
- `cancel_reminder`: Cancel a previously scheduled reminder by id.
- `send_notification`: Send a notification to the user's paired devices.
- `list_devices`: List device names, types and online status, so a caller can target one. Requires the devices:read scope. Returns metadata only — never notification content and never public keys.
- `request_approval`: Ask the user a question with 2-4 choices and get an interaction ID back. Requires the interactions:ask scope.
- `check_reply`: Poll for the answer to a request_approval question, waiting up to 45 seconds per call. Returns the chosen index as an integer, never the choice label — the server does not store the labels.
- `find_my_phone`: Ring the user's paired phone. Requires the phone:control scope. The ring stops itself after 60 seconds.

## Optional

- [API documentation](https://docs.reflecto.dev): Public send API and the MCP server, for agents delivering notifications to a paired device.