Legal
ClickTray - Privacy Policy
Effective date: August 27, 2026 Product: ClickTray Provider: Clearware, LLC, a Delaware limited liability company ("Clearware," "we," "us," or "our") Contact: info@clearware.co | https://clicktray.io
The short version (plain-language summary)
This summary highlights the key points. The full policy below controls.
- ClickTray runs on your device. The macros you record, the profiles you save, the screen regions you capture and the settings that go with them stay on your computer. We don't upload them.
- We don't collect what you type, click or capture. Our crash and usage reporting is built with a code-level filter designed to strip out URLs, file paths and filenames before anything is sent, and it never carries key names, typed text, cursor coordinates, window titles or screen captures in the first place.
- How ClickTray is funded - bandwidth sharing. While ClickTray is installed, it shares a slice of your idle internet bandwidth when it can through a bundled partner network (Massive) to relay other parties' traffic. Only one Clearware app shares on a device at a time, so this may not run at all if another Clearware product already holds the slot. When it is running, it runs in the background and keeps sharing even after you close ClickTray, until you uninstall. It does not read or upload your data. See Section 3. This is disclosed in the EULA and shown by an always-visible status indicator in the app and by Massive's own system-tray icon.
- To operate the network, Massive processes some device data (such as your IP address, an anonymous device identifier, city-level location, device specifications, and bandwidth statistics). Massive is an independent data controller for that processing under its own privacy policy. See Section 3.
- What we do collect is optional and anonymous: crash reports, basic usage counts, and a one-time install signal. You can turn each of these off.
- We don't sell your personal information.
- You have rights to access, delete, and control your data - see Sections 12-13.
1. Who we are
Clearware, LLC develops and distributes ClickTray, a free Windows desktop utility app. This policy explains what information the Software and our related services handle, how, and your choices. It applies to the ClickTray application and the clicktray.io website's interactions with it. It is incorporated into the End User License Agreement.
2. Our core principle: local-first
ClickTray is designed to keep your data on your device:
- Input synthesis and capture are on-device. Clicking, key pressing, macro recording and replay, and the pixel and image conditions all run through libraries bundled with the app, against your own screen and your own input devices. Nothing that happens in a session is sent to us or to any Clearware server.
- Your macros, profiles and settings are local. A recorded macro is a JSON file in your own profile folder; a captured screen template is an image beside it; preferences are stored on your device via a local settings store. We don't have a copy. ClickTray keeps no job-history database, because none of its four utilities produces a file or a queue row - they are sessions you start and stop.
- No account required. ClickTray does not require you to create an account or give us your name, email, or other identifying details to work.
3. The bandwidth exchange (how the app is funded)
ClickTray is free because, while it is installed, it shares a slice of your device's idle, unused internet bandwidth when it can through a bundled third-party network operated by Massive and/or its partners (the "Exchange"). Your connection relays third-party internet traffic. This is how we generate revenue instead of charging you or showing ads.
Only one Clearware app shares on a device at a time. The Exchange currently allows a single connected client per machine. If you have more than one Clearware application installed, only one shares bandwidth at any moment; a sibling app that does not currently hold the slot keeps retrying and takes over automatically once it frees up. On a device where a sibling app already holds the slot, ClickTray may share nothing for as long as that lasts.
The Exchange runs in the background, including after you close ClickTray. The Massive agent starts with your Windows user session and keeps sharing while you are logged in, even after you close or quit ClickTray, until you turn sharing off or uninstall. It shares only for the logged-in Windows user; it is not a system-wide service and does not run for other users of the device or at the Windows sign-in screen.
The Exchange does not access your data. Specifically, it does not read, upload, or share your files, your macros or captured templates, your browsing or search history, the sites you visit, your credentials, cookies, keystrokes, or screen contents. It relays other parties' traffic - not yours.
What Massive processes to operate the network. To route traffic, Massive processes a limited set of device data: your IP address (during active sessions), an anonymous device identifier, city-level location, device specifications, and connection and bandwidth statistics. Massive retains this data on a capped schedule (currently up to 60 days) and is an independent data controller for it, governed by Massive's own terms and privacy policy, not ours. See:
- Massive license: https://www.joinmassive.com/en/terms
- Massive privacy policy: https://www.joinmassive.com/en/privacy
- Massive SDK privacy policy: https://www.joinmassive.com/en/monetization-sdk-privacy-policy
- Massive FAQ: https://www.joinmassive.com/faq
Resource use. Sharing uses network bandwidth and a small amount of CPU. ClickTray does not itself instruct the Massive agent to keep your computer awake; depending on your system and the agent's own default behavior, participating may keep your device awake or reduce how often it sleeps while sharing is active, and otherwise defers to your operating system's normal power and sleep settings. ClickTray's own Stay Awake utility is a separate, explicitly user-started feature and is unrelated to the Exchange.
Your control. You can turn sharing off at any time from ClickTray's Settings, ClickTray's tray menu, or Massive's own system-tray icon; a stop from Massive's icon is honored and the app will not restart sharing behind you. Note: ClickTray's utilities do not run while sharing is off (see the EULA Section 4). To end participation permanently, uninstall the app, which stops and removes the Massive agent.
4. Information the Software collects
Everything below is optional, off-switchable, and designed to carry no personal identifiers, URLs, filenames, or content.
| Data | What it is | Purpose | Default | Third party |
|---|---|---|---|---|
| Crash reports | Anonymized error type and stack trace with URLs, file paths, filenames, and local variables scrubbed out before sending | Diagnose and fix crashes | On (opt-out) | Sentry |
| Usage analytics | A small, fixed set of events: app launched, the bandwidth exchange changing state, and the app-update lifecycle (update available/downloaded/applied/failed). The only details attached are the module id, a coarse error category, the update channel (stable/beta) and a public version number | Understand how reliably the app runs and whether updates are being adopted | On (opt-out) | Aptabase |
| Install-attribution signal | A one-time first-launch ping containing a random install identifier created by the installer (a UUID) - no name, email, or device profile | Measure how many downloads become active installs | On (opt-out) | Clearware (clicktray.io) |
| Update checks | A request to our update server to see whether a newer version exists | Deliver security and functionality updates | On (needed to update) | Clearware / update host |
How the "no PII" design is enforced. In the Software, every analytics event passes through an allow-list that permits only the fixed event names and the non-identifying properties above; anything else is dropped. Every crash report passes through a scrubbing step that removes user/identity fields and redacts URLs, Windows and Unix file paths, and filenames from the text before transmission. This is a design safeguard, not an absolute guarantee.
Nothing about a session is reported. There is no analytics event for starting, stopping or configuring a utility, and no field anywhere in the telemetry allow-list that could carry a key name, a typed string, a cursor coordinate, a window title, a macro's contents or a captured image. That is a property of the event schema, not a filter applied afterwards.
5. Information we do NOT collect
We do not collect, and the Software is built not to transmit:
- the keys you press, the text you type through the auto-typer, or the contents of any macro you record;
- the coordinates you click, the windows or applications you point ClickTray at, or their titles;
- the screen regions you capture as pixel or image conditions, or any other image of your screen;
- the names or contents of the macro and profile files on your disk;
- your browsing history or the websites you visit;
- your name, email address, passwords, payment details, or precise location;
- persistent cross-site advertising identifiers.
6. How we use information
We use the limited, anonymous information we do collect only to:
- keep the Software stable (diagnose crashes and errors);
- understand which features are used and how reliably, to prioritize improvements;
- measure install activation in aggregate;
- deliver updates.
We do not use it to build advertising profiles or to identify you.
7. Cookies and tracking
The ClickTray desktop application does not use advertising cookies or cross-site trackers. The website does, and rather than describe that in the abstract, here is the exact list of what runs on clicktray.io and why:
| What | Who runs it | What it does | How long it lasts |
|---|---|---|---|
| Google Analytics 4 | Google, as our analytics provider | Counts page views and navigation so we can see which pages lead to a download | Per Google's retention settings (Google privacy policy) |
| Microsoft UET tag | Microsoft Advertising | A conversion-tracking tag — an advertising cookie — that tells Microsoft when a visitor who clicked one of our Microsoft/Bing ads reached the site | Per Microsoft's retention schedule (Microsoft privacy statement) |
Microsoft click id (msclkid) | Us, first-party | When you arrive from one of our Microsoft ads, the ad's landing URL carries a click id. We store it in your browser (local storage plus a first-party cookie) so a download you make later can be matched back to the ad that produced it | 90 days from your most recent ad click, then it expires. A newer click replaces an older one |
Google click id (gclid) | Us, first-party | When you arrive from one of our Google ads, the ad's landing URL carries a click id. We store it the same way, for the same reason | 90 days from your most recent ad click, then it expires. A newer click replaces an older one |
Anonymous install id (st_iid) | Us, first-party | A random identifier (a UUID) with no name, email, or device profile attached, used to join "visited the site → downloaded → installed" into one count | The cookie lasts 180 days and is refreshed each time you visit; the copy kept in your browser's local storage stays until you clear this site's data |
What we send to the ad platforms, and what we do not. When a download or install happens, our server reports that conversion to Microsoft Advertising and to Google Ads. The Microsoft report contains exactly: the Microsoft click id, the random install id, your browser's user-agent string, the name of the event (for example download, install, or first_open), and a number we assign to weight how meaningful that event is. The Google report contains the Google click id, which conversion it counts as, when it happened, a value, and a transaction id built from the random install id so the same event is never counted twice. Neither contains your IP address, your email address, your phone number, or any hashed version of them. That is not an accident of implementation — we never store a full IP address anywhere in this measurement chain (only a truncated prefix), and we deliberately declined to start collecting any of those in order to improve ad matching.
This is measurement, not targeting. These identifiers exist to count conversions from ads we already paid for. We do not use them to build advertising audiences, we do not run remarketing or dynamic remarketing, and the consent signal we send Google explicitly withholds permission to personalise ads from these conversions. If we ever adopt any of that, this policy changes before it is switched on, not after.
Your controls. The site and the download work with all of this blocked. Your browser's cookie and tracking-protection settings, or any ad/tracker blocker, will stop the Google and Microsoft tags loading and prevent either click id being stored — nothing on clicktray.io depends on them. You can also use Google's and Microsoft's own opt-outs, linked in their policies above.
The cookie notice. Where consent is required — the EEA, the UK and Switzerland — clicktray.io asks before any of this runs. Until you answer, the Google and Microsoft tags are held in a no-storage mode in which they neither read nor write cookies, and the click ids and install id described above are not stored at all. Choosing Decline keeps it that way, and a download you make afterwards is counted only against the campaign, with no identifier attached and nothing reported to Microsoft Advertising or Google Ads about you. Your answer is remembered in your browser and travels with you; declining here stays in force even if you later visit from elsewhere. You can reopen the notice at any time from Cookie settings in the site footer.
Changing your mind later. If you accepted and then decline — from Cookie settings at any time — we do two things, not one. Your browser's copies of the click ids, the install id and the stored campaign record are erased, and we also tell our own server to stop reporting you, because a click id recorded while you were consenting would otherwise still be sitting there. From that point no further conversion of yours is sent to Microsoft Advertising or Google Ads. Reports already delivered to those platforms are subject to their retention schedules, not ours.
8. Legal bases for processing (EEA/UK users)
Where the GDPR or UK GDPR applies, we rely on these legal bases:
- Legitimate interests - for anonymous crash and usage reporting and aggregate install measurement, to keep the Software secure, stable, and improving, balanced against your privacy (and you can opt out).
- Consent - where required, including your acceptance of the bandwidth exchange and telemetry at first run; you may withdraw consent by disabling the relevant option or uninstalling.
- Performance of a contract - to provide the Software and deliver updates under the EULA.
9. How information is shared
We share information only as follows:
- Service providers (sub-processors): Sentry (crash reporting) and Aptabase (privacy-friendly, anonymous analytics) process the limited data described above on our behalf.
- The Exchange operator: Massive and/or its partners operate the bandwidth-sharing network as an independent data controller, subject to their own terms and privacy practices. Massive is not our service provider or processor for that activity.
- Update and website hosting providers deliver updates and run clicktray.io.
- Legal and safety: we may disclose information if required by law, or to protect the rights, safety, or property of Clearware, our users, or others.
- Business transfers: if Clearware is involved in a merger, acquisition, or asset sale, information may transfer as part of that transaction, subject to this policy.
We do not authorize these providers to use the data for their own unrelated purposes.
10. We do not sell your personal information
We do not sell your personal information, and we do not share it for cross-context behavioral advertising, as those terms are defined under the California Consumer Privacy Act (CCPA/CPRA) and similar U.S. state laws. Because the Software is built to avoid collecting personal identifiers in the first place, there is very little personal information involved at all.
11. Data retention
- On your device: your macros, profiles, captured screen templates and settings remain until you delete them or uninstall the app.
- Crash and usage data: retained by our providers for a limited period consistent with diagnosing issues and understanding trends, then deleted or aggregated.
- Install-attribution signal: retained in aggregate/measurement form; the random install id is not linked to your identity.
- Microsoft click id (
msclkid) and Google click id (gclid): each stored in your browser for 90 days from your most recent ad click, then it expires; a newer click replaces an older one. Where one has been used to report a conversion, the platform's own copy is subject to its retention schedule, not ours. - Consent withdrawal: if you decline after having accepted, we keep a minimal record that you withdrew — the anonymous install id and the date — because that record is what stops any further conversion being reported for you. It contains nothing else.
- Exchange data processed by Massive: governed by Massive's own retention schedule (currently capped at up to 60 days), under Massive's privacy policy.
12. Your privacy rights
Depending on where you live, you may have rights to:
- access the personal information we hold about you;
- correct inaccurate information;
- delete your information;
- object to or restrict certain processing, and withdraw consent;
- portability of information you provided;
- non-discrimination for exercising your rights.
Because ClickTray is local-first and largely anonymous, the fastest way to exercise most of these rights is directly in the app - turn off telemetry, turn off bandwidth sharing, delete your local data, or uninstall. To make a formal request, or if you're in the EEA/UK, California, or another region with statutory rights, email info@clearware.co and we will respond as required by law. You may also have the right to lodge a complaint with your local data-protection authority.
For rights relating to the data Massive processes to operate the Exchange, contact Massive through the privacy policy linked in Section 3.
13. Your choices and controls
You are in control of the optional data flows:
| Control | Where | Effect |
|---|---|---|
| Crash reporting | First-run consent screen and Settings | Turn off to stop sending any crash reports |
| Usage analytics | First-run consent screen and Settings | Turn off to stop sending usage events |
| Install-attribution | Settings | Turn off to suppress the first-open signal |
| Bandwidth sharing on/off | ClickTray Settings, ClickTray tray menu, or Massive's tray icon | Stops sharing immediately. While off, the app's utilities do not run (see EULA Section 4) |
| End sharing permanently | Uninstall | Uninstalling stops and removes the Massive agent and ends participation |
This policy does not claim automatic pausing on metered connections or during active use, and does not claim a bandwidth cap. Those controls are not part of the shipped build. In particular, sharing is not paused while a ClickTray session is running or while a game is in the foreground.
14. Security
We design the Software to minimize the data at stake: processing is local, the renderer runs sandboxed and isolated from system APIs, and privileged work is confined to the app's main process behind a typed bridge. A profile you import is treated as untrusted data and never as code: it is validated field by field on import, unknown fields are rejected, every numeric is clamped to a bounded range, and template images are resolved only from inside the profile bundle. No profile can describe a program to run. No method of transmission or storage is completely secure, but we take reasonable measures to protect the limited information we handle.
15. Children's privacy
ClickTray is not directed to children under 13 (or the minimum age required in your jurisdiction), and we do not knowingly collect personal information from them. If you believe a child has provided us personal information, contact info@clearware.co and we will address it.
16. International data transfers
We are based in the United States, and our service providers may process data in the U.S. and other countries. Where required, we use appropriate safeguards (such as standard contractual clauses) for transfers of personal data out of the EEA, UK, or other regions with transfer restrictions.
17. Changes to this policy
We may update this Privacy Policy to reflect changes to the Software, our practices, or the law. When changes are material, we will update the effective date and provide reasonable notice (for example, in-app or on clicktray.io). Your continued use of the Software after an update takes effect constitutes acceptance of the updated policy.
18. Contact us
Clearware, LLC Email: info@clearware.co Web: https://clicktray.io
For privacy requests, please put "Privacy Request" in the subject line so we can route it quickly.