Remote Coding

Privacy Policy

Effective date: 21 June 2026 · Last updated: 1 July 2026

Remote Coding (“we”, “us”, the “Service”) lets you reach the command-line terminals on your own computer from any web browser. This policy explains what we collect, why, how long we keep it, and the choices you have. We tried to keep it short and honest — if anything is unclear, email [email protected].

The one thing to know first. Everything you type into a terminal, and everything it prints back, runs on your own PC and is relayed in real time to your authenticated browser. We do not record, store, or log the contents of your terminal sessions. The Service is the bridge; your machine does the work.

1. Who we are

This Service is operated by the Remote Coding team. The web app is hosted at remote-coding.com. You can reach us at [email protected].

2. What the Service does (and where your data lives)

You install a small agent on a PC you own and sign in with your Google account. The agent connects out to our broker over an encrypted connection (TLS/WSS) and links that PC to your account using a private pairing token that you control. When you open a terminal in the browser, your keystrokes are relayed to the agent, which runs them in a real shell on your PC and streams the output back. We never execute your commands in the cloud, and no one else can attach to your PC.

3. Information we collect

At a glance — the data types we collect

This summary maps to the App Privacy (Apple App Store) and Data safety (Google Play) labels for our apps. None of this data is used to track you across other companies’ apps or websites, and none of it is sold. Details on each item follow below.

Data type	Why we collect it	Linked to you	Used for tracking
Email address	Create & secure your account (app functionality)	Yes	No
Name	Account, if provided by your sign-in	Yes	No
Payment info	Premium subscriptions — processed by Stripe/Apple; we never store card numbers	Yes	No
Purchase history (plan status)	Unlock the paid features you’re entitled to	Yes	No
Approximate (coarse) location	Security / fraud prevention & aggregate analytics — city-level, derived from IP	Yes	No
Identifiers	Account ID; IP address in security/audit logs	Yes	No
Crash data	Diagnose crashes — opt-in, off by default	Yes	No
Performance & diagnostics	App version, OS & performance with a crash report — opt-in, off by default	Yes	No
Files you upload	Relayed to your own PC in real time, then auto-deleted within 24 hours	Yes	No

a. Account information (from Google, Apple, or email sign-in)

When you sign in with Google we receive, and store, your email address, your name, and a Google account identifier (sub). We do not receive your Google password. This is what identifies your account and your devices.

b. Pairing token

Each PC is linked to your account with a private pairing token we generate for you. We store it to authenticate your agent. Treat it like a password; you can rotate or remove a device at any time.

c. Usage & diagnostics (to run the service and your plan)

We keep a small amount of operational data, mostly counters and timestamps — not the contents of your work:

Bandwidth used (bytes relayed up/down and for window mirroring) — to meter plan limits.
Session activity — when sessions open/close, how many, which shell type, and session duration.
Device & platform — the operating system of the PC your agent runs on (Windows / Linux / macOS), and the browser/device type you sign in from (e.g. desktop, Android, iOS), derived from your browser’s user-agent string.
Connection events & timing — agent connect/disconnect, last-seen time, login events, and relay latency, so we can keep the Service healthy.

d. Payment information (only if you subscribe)

Paid plans are processed by Stripe. Stripe handles your card details directly — Remote Coding never sees or stores your card number. We store only your Stripe customer and subscription identifiers and your current plan, so we know what you’re entitled to.

e. Files you upload

If you upload a file from the browser into a shell, it passes through our server only to reach your PC. Uploaded files are stored temporarily and deleted automatically within 24 hours.

f. Support messages

If you email us or send a message/feature request from the app, we receive your message and your email address so we can reply. Account and product emails (sign-up welcome, occasional product tips) are sent via Google (Gmail); inbound email to our domain is routed by Cloudflare. Every product email has a one-click unsubscribe link.

g. Security & audit logs

To protect accounts we log security-relevant events — failed logins, account lockouts, and which resources a session attached to — together with the IP address, account, and resource involved. We do not log passwords, pairing tokens, or the contents of your terminal sessions.

h. Cookies

We use a small number of cookies. A strictly necessary cookie keeps you signed in (your session) — the Service can’t work without it. We also use two optional analytics cookies that remember only, in aggregate, how you found us (a referral source) and a once-per-day visit marker — never your activity inside the app. The optional cookies stay off until you accept them in the cookie banner, and you can decline with no loss of functionality. We do not use advertising or third-party tracking cookies.

What we never collect: the contents of your terminal input or output, your files’ contents (beyond the temporary relay described above), your Google password, or your card number. Terminal output is held only in a small in-memory buffer to let you reconnect, and is not written to disk or logs.

4. How we use information

To provide the Service: authenticate you, link your devices, and relay your sessions.
To enforce plan limits and bill paid subscriptions.
To keep the Service secure and reliable (abuse prevention, diagnostics, uptime).
To respond to your support requests.

We do not sell your personal information, and we do not use it for advertising.

5. Third-party processors

We share the minimum necessary data with service providers who help us run Remote Coding. Each handles data under its own privacy terms:

Provider	Purpose	Data involved
Google	Sign-in (OAuth)	Email, name, account ID
Stripe	Payments & subscriptions	Card data (held by Stripe), billing IDs
Google (Gmail)	Sending account & product email	Your email & message contents
Cloudflare	Encrypted connectivity, network & inbound email routing	Connection metadata, inbound email
Hosting provider	Running the broker servers	Service data at rest

6. How long we keep data

Account data — while your account is active; deleted on request (see §8).
Usage/diagnostics & events — kept for operational and billing purposes, then pruned periodically.
Uploaded files — deleted automatically within 24 hours.
Security/audit logs — retained for a limited period for abuse prevention.
Terminal session contents — never persisted.

7. Security

All connections between your browser, our broker, and your agent are encrypted (TLS/WSS). Access is gated by Google Sign-In and your private pairing token. The agent only runs on the machine where you installed it, only while you choose to run it, and you can uninstall it at any time — when you do, the connection is gone. No system is perfectly secure, but we work to protect your data and limit what we collect in the first place.

8. Your choices & rights

Access & deletion — use Account → Delete my account in the app to deactivate your account immediately, or email [email protected] to access, export, or permanently erase your data.
Manage cookies — accept or decline the optional analytics cookies in the cookie banner at any time.
Remove a device — uninstall the agent or rotate its pairing token at any time.
Cancel billing — manage or cancel your subscription from the billing portal; Stripe stops future charges.
Sign out — end your browser session at any time.

Depending on where you live, you may have additional rights (e.g. under GDPR or CCPA) to access, correct, export, or delete your data, and to object to certain processing. Contact us to exercise them.

9. Children

Remote Coding is a developer tool intended for adults and is not directed to children. It is rated for users 16 years and older. We do not knowingly collect personal information from children under 16; if you believe a child has provided us data, contact us and we will delete it.

10. International transfers

We and our processors may handle your data in countries other than yours. Where required, we rely on appropriate safeguards for those transfers.

11. Changes to this policy

We may update this policy from time to time. We will revise the “Last updated” date above and, for material changes, take reasonable steps to notify you.

12. Contact

Questions, requests, or concerns about privacy: [email protected].