Privacy Policy

1. Who is responsible

LocalClip is developed by Blasmani Titi, who publishes on Google Play as Web Business Tools. For any privacy request or question about this policy you can contact webbusinesstoolspro@gmail.com.

2. Scope

This policy covers the LocalClip Windows app, the LocalClip Android app (including the LocalClip Board keyboard) and this website. It explains what information the apps handle, where it is stored and what never leaves your devices.

3. Our privacy model: local first

LocalClip was designed so that your content travels directly between your own devices. There is no LocalClip cloud, no LocalClip account and no LocalClip server that receives your clipboard, screenshots or files. Synchronization happens over your local Wi-Fi network, or in direct mode, where your PC creates its own access point (an ad hoc network) and your phone joins it by scanning the QR code. Direct mode needs neither a router nor an internet connection; if your PC does have internet at that moment, Windows can share it with your phone through that access point, as explained below.

4. Information LocalClip processes

The content you copy: clipboard text, screenshots, images and files. Once your two devices are paired, LocalClip picks up what you copy on your PC automatically; you do not approve each item one by one. Sending to your PC what you copy on your phone is a separate setting that stays off until you turn it on. Files are the exception: they are sent only when you choose to send or share them. This content is processed only to deliver it to your other device and to show it in your local history.

Pairing and connection data: device names, internal device identifiers generated by LocalClip, and the pairing credentials created when you scan the QR code. These exist so that only the devices you explicitly linked can talk to each other. In direct mode, your PC stores the name and password of the access point it creates, so that it can bring the same network back up, and your phone stores them too, in the app's own private storage, so that it can reconnect without scanning the QR code again.

Basic technical data on your devices, such as settings and transfer history, stored locally so the app can work.

5. Information LocalClip does NOT collect

We do not read, upload, sell or share the content you sync. We do not build profiles from your clipboard or files. Your synchronized content is never sent to the developer or to any LocalClip server, because none exists.

6. Transfers between your devices

Over your local Wi-Fi network, content goes from one of your devices to the other through your own network, once you have paired them with the QR code. It is not relayed through any LocalClip server, because none exists.

In direct mode, your PC creates its own access point (an ad hoc network) and your phone joins it by scanning the QR code. You need neither a router nor an internet connection. Your PC generates the name and the password of that network: the password is shared only through that QR code, but the name is broadcast over the air, exactly like that of any other Wi-Fi network, so any device within range can see that the network exists.

If your PC has an internet connection when you turn direct mode on, LocalClip first tries to create that access point through Windows' Mobile Hotspot feature: when that works, it shares that connection with your phone and it replaces the network name and password configured there with the ones LocalClip generates. If Mobile Hotspot is not available, or if your PC has no internet connection, LocalClip creates a plain access point instead: your phone gets no internet access through it and your Mobile Hotspot settings are left as they were.

Whichever of the two connections you use, once pairing is complete clipboard text and screenshots are encrypted with AES-256-GCM using the pairing key that your PC generates and delivers to your phone inside the QR code. That encryption also carries an authentication tag: if an encrypted message were altered on the way, the receiving device rejects it.

Files are different: LocalClip does not encrypt them, at any size and over either connection. They travel only over your local link, protected by the pairing token and by the network itself, and when a file arrives its SHA-256 hash is compared with the one announced by the sender, so you know it arrived complete and unaltered. Because their content is not encrypted, avoid sending files over networks you do not trust.

The content always goes straight from one of your devices to the other over your local link. LocalClip does not send it to the internet or to third-party servers.

7. The LocalClip Board keyboard

The keyboard runs on your device. What you type is delivered to the app you are typing in, and LocalClip never transmits it to us or to your PC. The only exception is the optional AI features described below, which send text to a third-party provider only if you add your own API key and only when you invoke one of them. Fields marked as sensitive (such as passwords) disable suggestions and clipboard offers, and nothing you type in them is learned or stored.

Local prediction dictionary. When the “Predictive text” option is on (it is on by default), the keyboard learns from what you type in order to suggest the next word, and that learning is saved on your phone. Each time you press the space bar it records the last word you typed, the pair formed by that word and the one before it and, when there are at least three words, the trio; for each combination it keeps a counter and the date it was last seen. It does not keep whole sentences, and it discards words that are only digits, that contain no letters, or that contain an at sign or a slash (email addresses, links, file paths). Nothing is learned in fields marked as sensitive, and a phrase is discarded before being learned if it matches the patterns of an API key, a long token, a numeric one-time code or a card number. Once the dictionary goes over 5,000 entries, the combinations seen only once that have gone unused for more than 30 days are deleted. It is kept in the app's own private storage, it never leaves your phone, and it is never sent to your PC, to the developer or to any third party. Turning off “Predictive text” stops any further learning, and clearing the app's data or uninstalling the app erases what has already been learned.

The keyboard includes optional AI features. Some of them run on your own device. Others work only if you add your own API key for a third-party provider (currently Google Gemini): in that case, and only when you invoke one of those features, the text you have selected or, if you have not selected anything, the text in that field before the cursor (up to 10,000 characters) is sent to the provider you configured and is processed under that provider's own terms and privacy policy. If you have added a key, this also happens when one of the features that run on your device cannot process the text there (for example, because it is too long). With a free Gemini key, outside the European Economic Area, Switzerland and the United Kingdom, Google uses that text to improve its products and people may review it, so do not use these features with sensitive or personal text. If you do not add a key, no text leaves your device. The key you enter is stored encrypted on your device.

Automatic screenshot detection (optional, off by default). The keyboard offers a “Save screenshots to clipboard” setting. It is off by default, and turning it on requires you to grant the images permission. While it is on, the keyboard watches the system image store and, whenever a new image appears, it asks Android only for the screenshots added in the last 30 seconds (images whose file name or folder marks them as screenshots) and receives at most 10 per check, with their details (identifier, file name, folder, size and date); other photos are not returned to the keyboard. Versions before 1.3.2 read the details of the images added in the last few minutes to work out which ones were screenshots and kept at most 120 per check. Images identified as screenshots are added to your local clipboard history and, if a device is paired and connected, are sent to your PC automatically, without asking you again. The rest of your gallery is neither added to the history nor sent anywhere. Turning the setting off stops both the detection and the sending.

8. Local storage

History, settings, pairing credentials and received files are stored locally on your devices. Clipboard history is kept for a maximum of 48 hours and is then removed automatically, with one exception: on Android, the items you pin in the keyboard's clipboard are not subject to that limit and stay until you unpin or delete them. The API keys you may add on Android for the keyboard's optional AI features are encrypted with a key held in the Android Keystore. You can delete history and files at any time from the app. On Android, if you have Android's backup to your Google account turned on, Android may copy LocalClip's settings, pairing data, recent history and received files, among other app data, into that backup; the keyboard's clipboard, its prediction dictionary and your API keys are left out. LocalClip never receives that backup.

The keyboard's local prediction dictionary described above is kept in the app's own private storage, with its own limits: once it goes over 5,000 entries, the combinations seen only once that have gone unused for more than 30 days are deleted.

9. Permissions the apps request

On Android, LocalClip requests: access to your local network and to the Wi-Fi state, and the ability to change them, to find your PC and to join the access point in direct mode; a foreground service and a wake lock, so that a transfer is not interrupted and your phone does not go to sleep halfway through; permission to start when the phone is turned on, so that synchronization with your paired PC resumes by itself; notifications, to show transfer status; vibration, for keyboard feedback; nearby devices (Bluetooth), only if you allow it; the camera, only to scan the pairing QR code; and access to your images. Bluetooth is used only to exchange short signals with your paired PC (for example, that there is something waiting and the phone should reconnect over Wi-Fi); each signal, encrypted with the pairing key, carries only its type, an internal device identifier generated by LocalClip and the time, and never your clipboard, screenshots or files. LocalClip does not request location permissions.

The images permission is used only by the optional screenshot detection described above: while it is on, the app reads the details of the screenshots you have just taken (before version 1.3.2, of your most recent images, to tell which of them were screenshots), including screenshots that you did not select one by one. When you choose an image or file yourself, LocalClip uses the Android system picker, which does not need this permission.

The Android app also declares internet access, Google Play billing and, on phones that have it, access to the system's on-device AI service. Internet access is not used to synchronize your devices, which stays on your local network: it is there for the ads, for measuring ad campaigns, for purchases, for the optional cloud AI features if you add your own API key and for the diagnostics that Google ML Kit, the library behind the on-device AI features, sends to Google. Billing is so that Google Play can process the optional subscription, and the on-device AI service is used by the keyboard's AI features that run on the phone itself.

Windows declares these capabilities: full trust for the desktop app; private network access; Bluetooth, for the short signals with your phone described above; and access to the radios, only to check whether Bluetooth and Wi-Fi are on (the app never turns them on or off). It also adds a firewall rule that allows the incoming local connections your phone makes. Each permission is used only for the feature it enables.

The Android app additionally declares the advertising identifier permissions, used by Google AdMob and by the TikTok measurement SDK, as described in the advertising section below. It also declares the basic phone state permission, which the Google AdMob SDK requires and LocalClip itself does not use, and access to the Google Play install referrer, which the TikTok SDK uses to tell which ad campaign an installation came from.

10. Advertising and purchases

The Android app may show ads served by Google AdMob and offers an optional premium subscription, weekly, monthly or annual, billed through Google Play, that removes the full-screen ads; the other ads are still shown. AdMob may process advertising identifiers under Google's own privacy policy. The subscription is managed by Google Play, and payments are processed entirely by Google Play; LocalClip never sees your payment details.

To measure its ad campaigns on TikTok, the Android app includes the TikTok App Events SDK (TikTok for Business). It is only switched on outside the European Economic Area, the United Kingdom and Switzerland, and only while the app is open. It sends TikTok the advertising identifier, an identifier generated by the SDK, basic device and app information (model, operating system, language, screen size, user agent, app version, the store it was installed from, network type and IP address), the Google Play install referrer, and these events: installing and opening the app, returning after two days, the first pairing with a PC, and a premium purchase with its price, currency and order number. It never receives anything you type, copy or sync, nor screenshots of the app. TikTok processes this data under its own privacy policy (https://www.tiktok.com/legal/privacy-policy). You can limit it by resetting or deleting your advertising ID in your phone settings.

11. Third-party services

Distribution is handled by Google Play and Microsoft Store, advertising by Google AdMob, and ad campaign measurement by TikTok (TikTok App Events SDK). If you enable the keyboard's optional AI features with your own API key, the provider of that key (currently Google Gemini) processes the text you send it. The keyboard's AI features that run on the phone use Google ML Kit, which, according to Google, sends Google device and app information, identifiers and usage data (such as performance, the size of the text, the configured languages and error codes) for diagnostics; the text itself is processed on the phone. These services have their own privacy policies that apply to the data they process.

12. Security

Once pairing is complete, clipboard text and screenshots travel between your paired devices encrypted with AES-256-GCM, with a 12-byte nonce and a 128-bit authentication tag, using the 32-byte key delivered inside the QR code; that tag is what detects any tampering along the way. LocalClip does not encrypt files, at any size and over either connection; their integrity is checked instead by comparing the SHA-256 hash of the received file with the one announced by the sender. Pairing requires physical access to both devices, because it can only be done by scanning the QR code. No method of transmission is completely secure, but LocalClip's local-only design keeps your content off the internet by default.

13. Retention and deletion

You control your data. Deleting an item from history, unpairing a device or uninstalling the app removes the corresponding local data. Clipboard history expires on its own after 48 hours; on Android, the items you pin in the keyboard's clipboard are the exception and stay until you unpin or delete them. The keyboard's local prediction dictionary, apart from the pruning described above, stays until you clear the app's data or uninstall the app, and stops growing as soon as you turn off “Predictive text”. We cannot delete data for you because we never receive it.

14. Minors

LocalClip is not directed to children under the age required by your local law.

15. Your rights

Depending on your jurisdiction you may have rights of access, correction, deletion, portability and objection. Because your data lives on your own devices, you can exercise most of them directly in the app. For anything else, write to webbusinesstoolspro@gmail.com and we will respond as soon as possible.

16. Changes to this policy

We may update this policy when the apps gain new features. Material changes will be reflected on this page with a new revision date.