Privacy policy: easysync for Android
Status: 25 October 2026. This policy applies to the app me.easysync.mobile.
It does not cover the website easysync.me, and it does not cover Google Play, which has its
own policy for what it processes about your installation. The desktop app has
its own policy.
1. Who is responsible
Monozeros GmbHHirschenstrasse 18, 9200 Gossau, Switzerland
E-mail: support@easysync.me
2. In short
easysync sends clipboard text and files between your own devices. The app has no account, no advertising, no analytics and no tracking service, and it sends no data to us. The one exception is the official relay (section 4): we operate it. If you add it, your phone asks it for an access key, an empty request that the relay answers with a random key. The relay then sees technical connection data of your phone and keeps a fingerprint (a hash) of that key. It cannot read what you send. Everything you send is encrypted on your phone and can be read only by the device you send it to.
3. What the app handles, and where it stays
| Data | What happens to it |
|---|---|
| Clipboard text and files you choose to send | Encrypted on your phone and sent to your paired device, directly or through a relay. We cannot read it, also not on the official relay. The app deletes its copy of a received file 7 days after the transfer ends (sooner if its storage limit is reached), whether or not you saved it; a copy that you saved or shared to another app is yours. Received text is not kept as a history. Files that you share into the app from another app are copied into the app’s own storage until they are sent. |
| The keys of this phone and the pairing data | Stored on the phone only. The keys are protected by the Android Keystore. They are removed when you choose “Reset this device” or uninstall the app. |
| The device name and the public key of this phone | Sent to the devices you pair with, so that they can recognise this phone. They are never sent to us. |
| Relay address and access key or token | The form for adding a relay offers the official relay (wss://relay.easysync.me) as a preselected choice. If you keep it and add it, you enter nothing: the app asks the relay for an access key by itself (section 4). The key is a random value, stored on the phone only, protected like the other keys of the app, never shown on screen and never passed on to the devices you pair. If you choose “Another relay”, you enter the address and the access token yourself. The app connects to a relay only after you have added it. The address and the key or token are removed with “Reset this device” or when you uninstall the app. |
| Camera | Used only while you scan a pairing code. The images are not stored or sent. |
| Connection while the screen is off | While the app is running and at least one device is paired, it runs a foreground service of type “data sync” that helps keep the phone connected with the screen off (section 5). Android may stop it (after 6 hours in 24 on Android 15) or suspend the connection. It shows an ongoing notification with a fixed text and a Stop button, which ends it; Settings has the same control. The service stores and sends nothing of its own. |
| Notifications | Created on the phone, only if you allow them. They never contain pairing digits, links or clipboard text. |
| Network information | The app reads whether and how the phone is connected (Wi-Fi, mobile data) and finds your own devices on the local network, to connect. This stays on the phone. For finding devices on the local network the app asks for the permission “Nearby Wi-Fi devices”, which it does not use to find your location. |
4. Relays, and the official relay
A relay is a server that passes encrypted data between your devices when they cannot reach each other directly. A relay cannot read your clipboard text or files. It can see technical data: the IP addresses of your devices, when and for how long they connect, how much data they send, and that these devices talk to each other.
The official relay at relay.easysync.me is operated by the
project, by the company named in section 1. In the form for adding a relay the app
preselects it for convenience; the app has no built-in connection to it, and it connects only
after you have added the relay. If you use it, we process the technical data named above and,
while the service of section 5 runs, also the times at which your phone is online. The relay
cannot read the content of what you send.
If you choose “Another relay”, the relay is run by whoever you named, and its operator is responsible for the technical data it sees, not we.
4.1 How your phone gets its access key from the official relay
A relay accepts only devices that present an access key. For the official relay your phone
gets one by itself, without an account and without any input from you. When you add the
official relay, the app sends one request over HTTPS to relay.easysync.me. The
request has no content: no name, no device name, no phone model, no app version, no
identifier and no cookie. The relay answers with a random access key of 32 random bytes. The
key is stored on your phone as described in section 3, and the phone presents it each time it
connects to the relay. Nothing is sent to Google or to any other third party for this: there
is no Play Integrity check, no push service and no other Google service in the process.
| Data | What happens to it |
|---|---|
| Your IP address and the time of the request | The relay sees them, as for every connection. It keeps the address in memory for 24 hours to limit how many access keys one network address can request (for IPv6 addresses it keeps the first 64 bits). It does not write the address to disk. The relay program does not log it; for the logs of the server see section 4.2. |
| The access key | The relay does not store the key. It stores a SHA-256 hash of it, the day on which the key was created and the day on which it expires, in a file on its server. It stores no IP address, no device data and no other identifier with them. |
| The access key at every connection | The phone presents the key each time it connects to the relay. The key belongs to your phone only, so while it is valid the relay can see that connections come from the same phone, also when the phone changes its network or address. The relay keeps no list of connections of its own; the system logs of the server are described in section 4.2. |
| The last day of use | A key that is not used expires, currently after 30 days of not being used (the operator can change this; there is no fixed maximum age). Every use moves the expiry day forward. The stored expiry day therefore shows, to the day, when a key was last used. The relay cannot tell whose key it is. |
Limits and control. The operator limits how many keys one network address can request per day and how many are issued per hour and in total; these limits are settings of the operator and change. The operator can switch the issuing of new keys off, can end all keys that were issued so far at once, and can block single keys by their hash. When a key has expired or was ended, the relay refuses it. The app then notices, waits a random time and sends the same empty request again to get a new key; it shows a short message in the relay list while it does so, and when a limit or a pause applies it tries again later by itself.
What the key is not. The key is not proof that a request comes from the easysync app: anyone can send the same request. The relay uses the key to limit abuse and to cut off misuse, not to identify you, and we do not claim that only easysync apps can connect to it.
Your choices. You can use another relay or none; the app works without the official relay. “Remove” in the relay list deletes the key from your phone. The relay then cannot match the stored hash to you and forgets it when it expires. “Reset this device” and uninstalling the app delete the key from the phone as well.
4.2 Retention and logs of the official relay
The relay program itself writes no application-level log of connections and never writes payloads, access keys or pairing identifiers to a log; it writes start-up messages, errors and numeric counters (for example errors and rate-limit hits, never addresses or keys). The web server in front of it keeps no access log. Its operational log records start-up, certificate and error events, not individual requests; it contains neither a visitor’s IP address nor the requested address or headers. Only if debug logging were switched on, which it is not, would requests with IP addresses appear. What a relay sees is described for every operator on the page “What the relay sees” in the documentation.
We keep these logs, that is the journal of the relay server and the log of the web server in front of the relay, only for a short time. The relay server is run by a hosting provider in Switzerland. The file with the key hashes is not part of a backup. The relay stores only a hash of the access key, never the key itself.
5. Staying connected with the screen off
With the screen off, Android freezes an app within minutes, and the phone would be offline for your other devices. To help prevent this, the app starts a foreground service of the type “data sync” once the app is running and at least one device is paired. Android requires an ongoing notification for it (“easysync is syncing in the background”). It is silent, hidden on the lock screen and has a Stop button. You can stop the service there, or in the settings of the app, at any time; it stays stopped until the app is started again.
From Android 15, the system ends a service of this type after 6 hours within 24 hours; the phone is then offline for your other devices until you open the app. Android may also suspend the network connection of the app by itself (Doze), for example when the phone lies still, unplugged, with the screen off, so the connection is not permanent. The service does not read the clipboard: that works only while the app is on screen. It does not collect or send any data of its own; the effect is that the connection to your devices, and to the relay if you use one, stays open longer while the service runs.
6. What we do not do
No account. No advertising and no advertising ID. No analytics, crash-report or tracking library. The app does not sell data. The app does not read the clipboard in the background; it reads it only when you tap to send. Pairing screens and the view of received text are excluded from screenshots and from the app switcher where Android allows it.
7. Children
The app is not meant for children under 18.
8. Applicable law and your rights
The app sends no data to us itself; the only data about you that we process because of the app is the technical connection data of the official relay (section 4), if you use it, and e-mails you send us. On your phone you can erase everything the app stores with “Reset this device” in the settings, or by uninstalling it.
What we cannot look up. The official relay stores a hash of the random access key of your phone, the day it was created and the day it expires (section 4). It does not know which phone or person a key belongs to, and the app never shows the key, so neither you nor we can find the entry that belongs to you. An entry ends by itself when its key expires. The IP address that the relay holds in memory for 24 hours is not stored and cannot be looked up afterwards. Requests about the data of section 4 therefore can be answered only in general terms. We treat the key hash and the IP address as personal data.
Legal basis. We process the IP address and the key hash on the official relay because we have an overriding private interest in operating and protecting the service: the relay cannot work, and cannot be defended against abuse, without them. The data is processed in Switzerland.
If you write to us by e-mail, we process your e-mail address and your message only to answer you. We delete them once your request is dealt with, unless a legal duty requires us to keep them. We do not pass them on, and we do not use them for advertising.
The controller is the company named in section 1, in Switzerland. This policy follows the Swiss Federal Act on Data Protection (FADP). Where the General Data Protection Regulation (GDPR) also applies to you, for example because you use the app in the European Union, the rights below apply as well.
Under the FADP you can ask us whether we process personal data about you and receive the information you need to assert your rights (Article 25), ask us to correct it, delete it or stop processing it (Article 32), and, where the law provides for it, ask to receive the data that you gave us in a common electronic format (Article 28). We generally answer requests for information within 30 days. You can report a violation to the Federal Data Protection and Information Commissioner (FDPIC), Feldeggweg 1, 3003 Bern, edoeb.admin.ch.
Under the GDPR you have the right of access (Article 15), rectification (16), erasure (17), restriction of processing (18), data portability (20) and objection (21), and the right to lodge a complaint with a supervisory authority (Article 77).
To use a right, write to support@easysync.me. We may ask you to prove who you are before we give out information.
9. Changes
If the app changes in a way that touches this text (for example a library that sends data, or a change in what the official relay processes), we update this policy before the version is released. The date at the top shows the latest change.
10. Contact
support@easysync.me. Security problems: security@easysync.me.