Remote Coder is published by an independent developer based in India, who decides what the apps collect and is the data controller for it. The contact for anything on this page — including a request to see or delete what we hold — is hello@remotecoder.dev. What you may do with the app is a separate document: the terms.

Remote Coder connects your phone to your own computer directly. Everything that makes up a session — the screen you are looking at, every pointer move and keystroke you send, the terminal output, the sound, and any file you pull off the machine — travels over an end-to-end encrypted peer-to-peer link between those two devices.

None of it is collected, stored, or seen by us. On a local network there is no server in the path at all. When you connect from outside your network, a relay forwards the connection — and it forwards sealed bytes: it holds no key, so it cannot read what passes through it, and it keeps no copy.

Your computer’s access password is never sent anywhere either. The apps prove knowledge of it without transmitting it, and the phone stores what it derives in the platform keystore — Keychain on iOS, an encrypted store on Android.

The apps report crashes and basic usage so that a bug reaches us without you having to describe it. This works the way every third-party analytics service works — the app sends requests over the network to that company’s servers — so the two services are named here rather than described in the abstract: Firebase Crashlytics and Google Analytics for Firebase, both operated by Google. There is no third one.

• 01Crashlytics — stack trace, device model, OS and app versionon a crash
• 02Analytics — screen names as you move through the appper screen
• 03Analytics — first open, session start, app and device detailsautomatic
• 04Analytics — an app instance identifier Google assignsper install
• 05Analytics — a coarse region, derived from the request's IPper request
• 06Your account identifier, attached to bothalways

The account identifier is what lets us answer a specific person’s report instead of staring at an average. The coarse region is derived by Google from the address the request arrives from; we do not receive your IP address and cannot look one up.

No custom events are recorded at all. The apps contain the ability to log one and do not use it: nothing reports that you signed in, connected to a machine, opened a terminal, ran a command, or bought anything. What Analytics receives is what it collects on its own, plus the name of the screen you are on.

Neither service carries session content. No screen image, no keystroke, no terminal output, and no file name is in a crash report or an event. Collection is off entirely in development builds. Both retain what they hold on Google’s own schedule.

There is no advertising and no tracking. No ad network is present in either app, no advertising identifier is requested on iOS, and on Android the advertising-id permission is actively removed from the build — a check in continuous integration fails the build if a dependency ever merges it back in. Nothing is shared with data brokers, and nothing is used to profile you across other companies’ apps or sites.

If you ask your computer to buzz your phone when a long-running command finishes, the phone registers for notifications. A small service of ours stores one row per app install so it knows where to send the buzz: the notification token, your account identifier, the platform (iOS or Android), and when it registered. Signing in on that device as somebody else moves the row rather than adding one.

The notification itself names the computer and says a session wants attention. It does not carry the command, its output, or anything from the screen.

The account and its connection log stay until you delete them. Crash reports and analytics events age out on Firebase’s own retention schedule. A notification registration is dropped when you turn notifications off, when the token stops working, or when that install signs in as somebody else.

• 01Delete a paired computerin the app
• 02Turn off notificationsin the app
• 03Delete the whole accountthe account page
• 04Ask us tohello@remotecoder.dev

Deleting the account removes it and everything filed under it, including the connection log. Purchases live with Apple or Google and are restored by signing in to the same store account, so deleting here does not destroy something you paid for.

Depending on where you live you may also have the right to see a copy of what we hold, correct it, restrict or object to our holding it, or receive it in a portable form. Write to hello@remotecoder.dev and it gets done. There is one of us, so it gets done by a person rather than by a portal — and if you think it was not, you can complain to the data protection authority where you live.

Why we are allowed to hold it. For the account, the connection log and the purchase, because there is no app without them: we are performing the contract you entered when you installed it. For crash reports and analytics, because a tool that cannot be debugged cannot be maintained — a legitimate interest, narrowed to what serves it, which is why no advertising identifier is collected and no profile is built. Where your law requires consent instead, the app asks for it before collecting.

Where it is held. On infrastructure run by Google and Cloudflare, which means it may be processed outside India and outside your own country, including in the United States. Both operate under the standard contractual terms that make those transfers lawful, and both are bound to process it only on our instructions.

Remote Coder is a developer tool and is not directed at children. We do not knowingly collect anything from a child under 13. If you believe a child has made an account, write to hello@remotecoder.dev and it will be deleted.

If this policy changes in a way that matters, the app and this page will say so before the change takes effect. Every revision is in the public git history of the site.