Your data, in plain English
Last updated: October 18, 2026
On this page
We collect as little as we can. Here's what RemoteAccessApp keeps about you on our servers, where it lives, how long we keep it, and what we never see. The full details are in our Privacy Policy; what you can ask us to do with it is in Your data rights.
What we keep
All of this is stored on our own server in Australia, and copied into backups that are deleted after 14 days.
| What | Why | How long |
|---|---|---|
| Your email address | It's your sign-in name. It's the only personal detail we need | Until you delete your account |
| Email confirmation | Whether your email address is confirmed, one-time codes for the links we email you (stored only as one-way hashes; each works once, for 24 hours to confirm your address or 30 minutes to reset your password), your "new sign-in" email setting, and one-way codes of the kinds of app and networks you've signed in from, so we can tell when a sign-in is new | Link codes: until used or expired. The rest: until you delete your account |
| Two-factor authentication, if you turn it on | Whether you use two-factor authentication, your encrypted authenticator secret and hashed backup codes, so sign-in can ask for a code. We can't read your backup codes | Until you turn it off or delete your account |
| Your name, if you give it | So we know what to call you | Until you remove it or delete your account |
| A scrambled version of your password | A one-way hash, so we can check your password but never read it | Until you delete your account |
| IP addresses | From when you create your account, sign in, and when your PCs and Consoles connect. For security and to prevent fraud | Sign-up IP: while you have an account. Sign-ins: up to 30 days after last use. PCs: the latest one only, until removed. Security log: 90 days |
| Approximate location | The country, region and city an IP address points to, looked up in a GeoIP database. We see it in our admin dashboard, for account management, security and fraud prevention. It's rough, and never GPS | No longer than the IP address it comes from |
| Your license | Which Consoles are activated on it. For each one: an anonymous hardware fingerprint, the app version, when it last checked in and from which IP address | For the life of the license |
| Your PCs | Their Windows computer name, the Windows user signed in on them, when they were last online, their last IP address, and any friendly name you give them | Until you remove the PC or delete your account |
| One-time help codes ("Get help") | So someone you asked can help on your PC, once, after you allow it: a one-way hash of the code (never the code), your PC's name, the IP address it was asked from (to limit codes per network), the helper's account and when the code was made, used and ended. You don't need an account to get one | A day after the code or the help session ended |
| Your PCs' network cards | Their hardware (MAC) addresses and local networks, stored encrypted, so you can wake an offline PC up from another of your PCs on the same network | Until you remove the PC or delete your account |
| Scrambled hardware identifiers | One-way keyed hashes of your PCs' machine ID and network card addresses, so a ban for abuse can cover the PCs an account used. We can't read the originals | Up to a year after we last see them, or until you delete your account |
| Trusted networks | The IP address ranges you allow, if you set any | Until you remove them or delete your account |
| Your saved hosts | Host names, addresses, ports and user names, so they follow you to every Console. Never passwords or keys | Until you delete them or your account |
| Your saved passwords and SSH keys, if you save them (Pro) | End-to-end encrypted with a key from your account password (a key's passphrase too, if you choose to remember it). We store them but can't read them | Until you delete them or your account |
| Your PCs' health, with monitoring alerts on (Pro) | About once a minute: CPU and memory use, free space per drive (by letter only), how long the PC has been on, whether Windows waits for a restart, and whether an update failed. Never files, programs or anything from your sessions | Only the latest report, in memory, gone within minutes. Never written to disk |
| Your alerts (Pro) | Your alert rules, quiet hours and time zone, and the alerts that fired (the PC's name, what happened, when) | History: 90 days. Settings: until you delete your account |
| Notification subscriptions, if you turn them on (Pro) | The push address your browser gives us and its encryption keys (stored encrypted), with a label like "Chrome on Android" | Until you turn notifications off or remove the device |
| PC management, if you use it (Pro) | The tags you give your PCs; your scheduled tasks (name, what they run - for a script, its text, stored encrypted -, which PCs or tags, when, time zone); and for each action (a script's text is stored encrypted here too) a short result per PC: who started it, when, its state, exit code and the last few KB of its output (stored encrypted). Lists of a PC's available updates and installed apps are kept only as the latest result of a check | Results and run history: 30 days. Tags and schedules: until you delete them, the PC or your account |
| Your team | Its name, the email addresses you add, and which PCs and hosts you share with each person | Until you remove them or delete your account |
| Team roles and permissions (Pro) | Each person's role (Admin, Technician, Member, Viewer or a role the team's owner made, with what it allows) and what they may do on each shared PC (view, control, files, Windows tools, the command prompt and scripts, management jobs, manage access). The PC itself enforces them | Until changed, the person leaves the team, or the team is deleted |
| Your team's audit log (Pro) | Who did what in your team and when: sessions team members started and ended on its PCs (how long, and how many files - a number only), management jobs they started, invites, joins, removals, role and permission changes (refused ones too), the team's own roles, and downloads of the log. The email of the person a change was about. Never passwords, invite codes, file names, commands or anything on screen, and no IP addresses. Readable only by the team's owner and roles allowed to see it. If someone deletes their account, their entries show "Former member" and their email is removed from the log | Deleted after 1 year, or with the team |
| PC history notes, if you write them (Pro) | Notes about a PC, who wrote each one and when, and, for a note written during a session, an automatic summary: when it started and ended and counts of what was done (like "Sent 3 files to the PC"). Never file names, what was typed or anything on screen. Encrypted on our server, but not end to end: everyone the PC is shared with needs to read them, in the app or on the website. Readable by the PC's owner and the team members it's shared with. If an author deletes their account, their notes show "Former team member" | Until deleted, the PC is removed or its owner's account is deleted. Up to 1,000 per PC |
| A security log | Sign-ins, sign-ups, password resets, PCs added or removed, account changes (including team roles and permissions), notes added or deleted (never their text), PC management actions (what kind, how many PCs, each result; never a script's text or output), with IP addresses. A PC pausing connection-password attempts after 5 wrong tries (which PC and account, no IP address). | Deleted after 90 days |
| Session records | A short record of every session through our relay, with or without an account and for help codes: when, how long, who connected (or that it was a guest), which PC (its name and system) and its owner, which relay, how it connected (app, browser or AI assistant), the app version, how much data each way, how many files (a number only), and the networks at both ends shortened to /24 (IPv6: /48), never full IP addresses. For browser sessions, also frames per second and round-trip time. Never what happened in the session | Deleted after 90 days |
| Connection records | A short record of the connections you open without our relay: SSH, SFTP, FTP, RDP, VNC, serial and web panels in the Console, the browser terminal, and SSH from an AI assistant. The kind, where it came from, how it was routed, what protects it, when, how long, how much data each way, and how it ended. Never the server's name or address, user names, passwords, keys, commands, output or file names | Deleted after 90 days |
| PCs and Consoles used without an account | For a PC: its name, operating system, the IP addresses it registered and was last seen from, and when. For a Console: the name it gives itself, when it was created and the IP address it was created from. Each connection (which PC, which Console, when, from where) | Connections: 7 days. The PC and Console: while they use no-account mode |
| Your activity log download (Pro) | Your activity from the security log, as a CSV or JSON file. A team's owner also gets members' sessions on the team's PCs and admins' team changes. IP addresses only for your own sign-ins | Not kept: made when you ask for it |
| Your privacy choices | Whether you said yes to product news by email and to product analytics, and when | Until you delete your account |
| A copy of your data, if you ask for one | A ZIP of your account's data, made after you confirm your password, for you to download | Deleted 7 days after it's ready |
| Payment records | Once you subscribe: Stripe's IDs for you and your subscription, its status and period end, and each payment's amount, currency, date and reference. You pay in Stripe's payment form: your card details stay with Stripe, and we never see them | 5 years, as tax law requires (without your name or email once your account is deleted) |
| SSH servers you trusted, if you use the browser terminal | Each server's name, port and public key fingerprint, so a changed key is caught. Never a password | 90 days after you last use the terminal |
| Server logs | IP addresses and pages requested (never the part after "?"), to keep things running | Website logs 14 days; app server logs overwritten after a short time |
| Service statistics | Counts of how the service is used (accounts, PCs, sessions and their length and data, sign-in failures, sign-ups, subscriptions, pages requested, response times, countries, desktop, phone or tablet and the browser family, the name of the website a visitor came from, such as a search engine, and a link's campaign tags, such as "newsletter"). Never your email, name, IP address or browser details: to count unique website visitors, the IP address and browser family are turned into a code that changes every day (weekly and monthly totals use their own codes, which never leave our metrics server). Bots and our own visits are left out | Detailed: 30 to 90 days. Daily totals: 2 years. The website's request file they're made from (IP address and browser details): 4 days at most |
Emails we send you
Only the emails your account needs. News about RemoteAccessApp only if you say yes to it (and you can say no again any time):
A welcome email when you sign up, which asks you to confirm your email address (you can ask for it again).
A password reset link, when you ask for one.
Security emails: your password was changed; a new sign-in from an app or network we haven't seen before (at most 3 a day, and you can turn these off); two-factor authentication was turned on or off; your trusted networks changed.
Monitoring alerts, if you turn them on (Pro): only to a confirmed address, at most 5 a day, never in your quiet hours.
If you delete your account: when it will happen and how to cancel, then a last email once it's done.
The download link, if you ask for it on our website: one email with only the link to the download page. No account needed, and we don't keep your address (only a counter in memory, for up to a day, so nobody can use it to flood an inbox).
They go out through Resend, our email provider in the United States. Resend receives your email address and what each email says (for example the link, or the kind of app that signed in and roughly when). Our own statistics only count emails by kind, never who they went to.
Notifications on your phone or computer
If you turn on "Notify me on this device" (Pro), your browser's push service (Google, Mozilla, Apple or Microsoft) delivers short notifications from us: alerts about your PCs, "someone wants to connect to your PC", a new sign-in, and, if you want, a remembered browser connecting. They say only the PC's name and what happened, never an IP address, and they're encrypted so the push service can't read them. Turn any of them off on the Alerts page.
What we never see or keep
Your screen in the apps. Sessions are end-to-end encrypted. Our relay forwards data it can't decrypt, and nothing that happens in a session is recorded (only that it took place, for the session records above).
What you type, click, say or run during a session.
Your chats, clipboard or files. They're encrypted end to end and never stored by us.
Passwords to your servers (RDP, SSH, SFTP, FTP, VNC). They stay on your PC, or are end-to-end encrypted if you sync them.
Tracking in the apps. No ads, trackers or analytics that follow you in the apps. Our service statistics stay on our own server and are about the service, not about you (and with product analytics off, your account isn't even counted as you). The "I'm not a robot" check on the sign-up form is Cloudflare Turnstile: Cloudflare, which already delivers our website, looks at signals from your browser and device to tell people from bots, and our server checks its answer with Cloudflare before creating the account. The check on our other forms runs on our own server, with no third-party service and no tracking cookies.
Trackers on our website, unless you allow them. The only ones are Meta's ad-measurement pixel and the tawk.to live chat, on the public pages only. In the EU, the EEA, the UK and Switzerland, neither loads until you say yes; anywhere, "Cookie settings" at the bottom of every page turns them off. See the Cookie Policy.
Files you share from your phone to one of your PCs: they stay in your phone's browser until you send them, then pass straight through to your PC.
Our free tools (what's my IP, port checker, speed test): nothing is stored. The port checker only ever connects to your own IP address.
One exception: when you use RemoteAccessApp in a web browser, our website acts as your Console, so your session passes through our website server. It's handled in memory only to pass it to your browser, and never recorded or stored. Only two numbers go into the session record: frames per second and the round-trip time to your browser. The same goes for the SSH terminal in the browser: our website (or a nearer server of ours) runs the SSH connection, so your password or key and what you type pass through it in memory for that session only, never stored or logged. On our main website, your browser's connection also goes through our network provider, Cloudflare.
The person at the other PC
- Unless unattended access is on, the PC asks the person there to allow each session, and shows nothing until they do.
- Unattended access can only be turned on at the PC itself, by the person there or with their agreement on that PC. While it's on, your Consoles can also show a small, low-resolution preview of that PC's screen.
- During every session the PC shows a "remote session active" banner, and the person there can chat back, switch off mouse and keyboard control, or quit RemoteAccessApp.
- The person there can also require a connection password before anyone connects (on top of the Allow prompt). It's set only at that PC and kept only there, as a one-way hash: we never see it, and it's never sent over the internet (the apps and the website prove it to the PC instead). "Remember me on this device" keeps a token on the PC and on that device only, and it stops working when it expires, is removed at the PC, or the password changes. Five wrong tries pause attempts for a while, and if alerts are on, the owner is told and the security log notes it (no IP address).
- PC management (Pro: scripts, scheduled tasks, Windows updates, apps) follows the same rules: the PC asks the person there first unless unattended access lets the owner's own account in, nothing that changes the PC runs while remote control is switched off there, and the PC shows a notice for every action (who, what, when, the result). It never restarts without a notice that lets the person there postpone it.
RemoteAccessApp is only for PCs you own or have permission to access. If other people use the PCs you connect to, it's up to you to tell them about RemoteAccessApp and to get any consent the law requires.
If you use Claude Code with RemoteAccessApp
That's a Pro feature, and it runs on your own PC. We don't get anything extra. What Claude sees on your PCs (screenshots, command output) goes to Anthropic, the company behind Claude, under their privacy policy. Your Console keeps a short list of what Claude did so you can check and stop it, but not what it typed or what commands printed.
Want it gone?
Remove a PC or a team member at any time. To delete your account, use "Delete my account" in your dashboard under "Privacy & your data" (accounts in the EU, EEA, UK and Switzerland; you have 14 days to change your mind), or ask us. We'll delete your account, PCs, saved hosts, saved passwords, alerts, notification subscriptions, your PCs' history notes, PC tags, scheduled tasks and their results, and team. Notes you wrote on someone else's PC stay in that PC's history as "Former team member" until they're deleted there. Security log entries expire within 90 days, backups roll over within 14 days, and we keep payment records as long as tax law requires. Email [email protected].