Remote Privacy Policy

Remote is published by [full name of the individual entrepreneur — to be filled in], an individual entrepreneur registered in Georgia, identification number [identification number of the individual entrepreneur — to be filled in], registered address [registered (legal) address in Georgia — to be filled in], operating under the brand Erti Cloud (“we”, “us”). We are the controller for the data processed by our signaling service. Privacy questions: privacy@erticloud.com.

This policy applies to the Remote apps for macOS, Windows, Linux and iOS and to the signaling service at erticloud.online. Our websites are covered by the Privacy Policy.

Remote keeps its data on your devices. We have no access to it:

• cryptographic device keys, stored in the system keychain or credential store (macOS and iOS Keychain, Windows Credential Manager, Linux Secret Service);
• the list of paired devices with their names, public keys, permissions and access modes;
• the security log and connection history — for example when a device connected and which permission was used;
• settings, such as the selected signaling server, file locations you approved and display preferences.

You can delete this data by revoking devices, clearing the history in the app or uninstalling Remote. Keys in the system keychain may remain until you remove them there.

The content of your sessions — screen images, keyboard and mouse input, terminal input and output, file names and file contents — is transmitted directly between your paired devices over WebRTC, encrypted end to end (DTLS-SRTP) and bound to the device identities created during pairing. If a direct connection is not possible, encrypted traffic may pass through a relay (TURN) server, which cannot decrypt it.

We do not receive, store or have the technical ability to read session content.

To connect devices over the internet, Remote uses a signaling server. Unless you configure your own server, this is our service at erticloud.online, hosted by [hosting provider and location of the Remote signaling server — to be filled in]. It authenticates devices by their keys and forwards connection messages, which are encrypted end to end. In doing so, it processes:

• device identifiers (derived from each device’s public key) and the public keys used to authenticate them;
• the IP addresses your devices connect from;
• when devices come online and go offline, and which device a message is addressed to;
• the size and timing of encrypted messages.

The service cannot read pairing codes, connection details (SDP and ICE candidates), commands, files, screen images or terminal data.

The server keeps operational logs of devices coming online and going offline (with device identifier) and of failed authentication attempts (with IP address). These logs are deleted after [retention period of signaling server logs — to be filled in], unless a specific entry is needed longer to investigate abuse or a security incident.

If a connection is relayed through a TURN server that we operate, that server processes IP addresses, timing and traffic volume, but only carries encrypted packets.

Purposes and legal basis: providing the connection service you request (Article 6(1)(b) GDPR) and our legitimate interest in keeping the service secure and preventing abuse (Article 6(1)(f) GDPR).

If you use your own signaling or TURN server, we do not receive this data; the operator of that server is responsible for it.

• Network address discovery (STUN). To find a direct path between devices, Remote asks a STUN server for your public IP address. The STUN servers are provided by the signaling server; in the default configuration this includes a public STUN server operated by Google (stun.l.google.com), which receives your IP address and the time of the request under Google’s privacy policy.
• Dictation on iPhone. If you use dictation with the system engine, your speech is recognised by Apple’s Speech framework. Depending on the device and language, audio may be sent to Apple for processing under Apple’s privacy policy. You are asked for microphone and speech recognition permission first.
• Offline speech model. If you choose the Whisper engine, the app downloads a speech model once from Hugging Face (huggingface.co), which receives your IP address as part of the download. Recognition then runs entirely on your iPhone.
• Local network discovery. On the desktop, Remote can announce the computer on your local network (mDNS) so that your other devices can find it. Other devices on the same network can see the computer’s name. You can turn this off in the network settings.

Remote does not include analytics, advertising, crash-reporting or telemetry services.

Remote asks the operating system for the permissions its features need — for example Screen Recording and Accessibility on macOS, the camera for scanning a pairing QR code, the microphone and speech recognition for dictation, local network access and notifications. The data these permissions give access to is used only for the corresponding feature on your devices.

Face ID and Touch ID are handled entirely by iOS. Remote only learns whether the check succeeded; it never receives biometric data.

If you download Remote from the App Store, Apple processes data about the download under its privacy policy. If you download it from our websites, our hosting provider records technical data as described in the Privacy Policy.

Our signaling service may be located outside your country. Where required by the data protection law that applies to you, transfers take place on the basis of an adequacy decision or appropriate safeguards, as described in the Privacy Policy.

You have the rights described in the Privacy Policy, including access, deletion, objection and the right to complain to a supervisory authority such as the Personal Data Protection Service of Georgia or the authority in your country.

Because Remote has no accounts, we can only find signaling data by device identifier. To make a request, write to privacy@erticloud.com and include the device identifier shown in the app.

Remote is a tool for managing your own computers and is not directed at children. We do not knowingly process children’s data beyond the technical metadata described above.

Remote uses established cryptographic libraries for authentication and end-to-end encryption, stores keys in the system credential store and checks permissions on the host for every request. Our security model is documented publicly. No independent third-party audit has been performed yet, and no system is completely secure.

If Remote starts processing new kinds of data, we will update this policy before releasing the change and, where required, ask for your consent in the app. Each version is listed in the version history below.