Back
Stanfeld Remote Assist Privacy Policy
Last Updated: November 3, 2026
This policy explains what personal data Stanfeld Remote Assist (the website at help.stanfeld.dk and the Stanfeld Remote Assist desktop app, together "the Service") processes, why, and for how long. The data controller is Stanfeld Consulting ApS, CVR DK39579553, Breeltehøj 21, Hørsholm, Denmark (privacy@stanfeld.dk).
1. How the Service works, in short
The person who needs help (the "receiver") gets a one-time code (OTP) and gives it to the person helping (the "helper"). Our signaling server uses the code to introduce the two devices to each other. After that, screen sharing, chat and (if the receiver allows it) remote mouse and keyboard control run directly between the two devices over an encrypted WebRTC connection. If a direct connection is not possible, the encrypted traffic is passed through our relay (TURN) server, which cannot read it.
2. Data we process
- IP addresses: our servers see your IP address when you connect. The signaling server logs it together with connection events (for example "helper connected", button clicks such as "share screen"), and the helper's IP address is shown to the receiver so they can see who is connected.
- Helper name: the name a helper types (letters and digits, up to 30 characters). It is shown to the receiver and kept in the server's memory only while the session lasts; it is not written to the logs.
- One-time codes and session tokens: kept in the server's memory only. OTPs expire after 2 minutes or when the session ends; a reconnect token (so a helper can rejoin after a network drop) expires after 10 minutes; relay credentials expire after 5 minutes. None of these are written to disk.
- Network addresses for the direct connection: as soon as the helper has entered the code, the two devices exchange the network addresses needed to connect directly (your public IP address and, for devices on the same network, local addresses). This is how WebRTC works, so the receiver's IP address also becomes visible to the helper's device, before anything is shared.
- Screen content, chat and remote input: sent directly between the two devices, encrypted end to end by WebRTC (DTLS/SRTP). We do not receive, store or have access to it. Exception: when a chat message is sent before the direct connection is up, or the other side uses an older version of the app, that message is relayed by the signaling server over an encrypted (TLS) connection. It is passed on immediately and never stored or logged.
- Session recordings: the app asks the receiver for approval before a helper can record. The recording is made and saved on the helper's own device; it never passes through or is stored on our servers. "Record your screen" on the website records only your own screen and saves the file on your own device.
- Desktop app log: the desktop app writes a technical log file (debug.log) on your own computer to help with troubleshooting. It is replaced each time the app starts and is never sent to us automatically.
The Service uses no cookies, no third-party analytics and no advertising; the only usage data is the server log described above. The website loads no content from third parties: fonts and icons are hosted on our own server.
3. Why we process it (legal basis)
- To provide the Service you asked for (GDPR Art. 6(1)(b)): pairing the two devices, showing who is connected, relaying connection data and, when needed, encrypted traffic.
- Security and abuse prevention (GDPR Art. 6(1)(f), our legitimate interest in keeping the Service safe and working): logging connections, limiting repeated wrong codes, troubleshooting.
4. Your control during a session
- Your screen is not shared until the receiver clicks "Share Screen". Chat is available as soon as the helper has joined.
- Remote mouse and keyboard control and session recording each require the receiver's explicit approval, and can be stopped at any time. In the desktop app, a keyboard shortcut shown on screen takes back control instantly.
- Either side can end the session at any time.
Please close anything sensitive before you share your screen, and only give your code to people you trust: anyone with the code can see what you share, and someone using modified software could record it without asking.
5. Who we share data with
- The other participant: the receiver sees the helper's name and IP address, and the two devices learn each other's network addresses when connecting (section 2). Screen content and chat go to the other participant only.
- No one else: we do not sell or rent personal data and use no third-party service providers for the Service. The website, signaling server and relay server are operated by us on servers in Denmark.
- Authorities: only where we are legally required to.
6. How long we keep it
- Server logs (including IP addresses): 30 days, then deleted automatically.
- Codes, tokens, helper names: in memory only, for the lifetime of the session (see section 2).
- Screen content, chat, remote input: not stored by us.
7. Security
All connections are encrypted (HTTPS/WSS for the website and signaling, DTLS/SRTP for WebRTC). One-time codes are random 8-digit numbers, valid once and for 2 minutes, with limits on repeated wrong attempts. Access to server logs is restricted.
8. Your rights
Under the GDPR you have the right to access, rectify and erase your personal data, to restrict or object to its processing, and to data portability. To exercise them, email privacy@stanfeld.dk. Because we only keep IP-based logs for 30 days and do not link them to names or accounts, we may need the IP address and approximate time of your session to find your data. We reply within one month.
You can complain to the Danish Data Protection Agency (Datatilsynet), www.datatilsynet.dk.
9. Children
The Service is not intended for users under 16. If you believe a child has used it and we hold their data, contact us and we will delete it.
10. Changes
If we change how we process data, we update this page and the "Last Updated" date above.
11. Contact
Stanfeld Consulting ApS
Email: privacy@stanfeld.dk
Address: Breeltehøj 21, Hørsholm, Denmark
CVR: DK39579553
Back