Legal
ScreenTray - Privacy Policy
Draft — pending legal review. This policy is a plain-language draft and may change before public launch.
Effective date: Draft, not yet in effect (last revised November 20, 2026) Product: ScreenTray Provider: Clearware, LLC, a Delaware limited liability company ("Clearware," "we," "us," or "our") Contact: [email protected] | https://www.screentray.io
The short version (plain-language summary)
This summary highlights the key points. The full policy below controls.
- ScreenTray runs on your device. Your screenshots, recordings, GIFs, captions and transcripts are ordinary files in a folder on your computer. Speech recognition, Smart cleanup, background blur and Copy text all run on your computer. Dictation audio is never saved or sent. We don't upload any of it.
- We never receive your captures or what you say. Not your files, their names, the windows you capture, what you dictate or type, or your transcripts. Our crash and usage reporting is built around a code-level allow-list that can say that a screenshot was taken or a video was emailed, but never what was in it.
- How ScreenTray is funded - bandwidth sharing. While ScreenTray is running, 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. Sharing runs inside ScreenTray, including while it sits in the system tray with its window closed, and stops when you quit ScreenTray. While sharing is off, ScreenTray does not start new screenshots, recordings or dictation; your existing files stay fully usable. It does not read or upload your data. See Section 3. This is disclosed when you install and shown by an always-visible status indicator in the app.
- 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 limited and carries no name or contact details: crash reports and usage counts, which you can turn off, and install and uninstall signals keyed to a random install id. We also record your device's IP address with these signals, and the first launch sends basic hardware details; we use both to detect fraudulent installs. If you send feedback, we receive what you write and any name or email you add. See Section 4 for exactly which of these you can switch 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 ScreenTray, a free Windows app for screenshots, screen and webcam recording, and dictation. This policy explains what information the Software and our related services handle, how, and your choices. It applies to the ScreenTray application and the screentray.io website's interactions with it. It is incorporated into the Terms of Use.
2. Our core principle: local-first
ScreenTray is designed to keep your data on your device:
- Your captures are files on your computer. Every screenshot, recording, GIF, caption file and transcript is saved in your library folder (
Documents\ScreenTrayunless you choose another). ScreenTray never uploads them. They leave your computer only when you send them yourself, for example by pasting them into an email or chat, attaching them to a message, or using the Windows Share sheet. Where they go then is up to you and the service you send them through. - Your voice stays on your computer. Dictation and captions use a speech-recognition model that runs on your computer. Dictation audio is turned into text in memory and is never saved or sent. Captions are made from a recording's own soundtrack, on your computer.
- Cleanup runs on your computer. Basic cleanup is simple local text rules. Smart cleanup, if you turn it on, runs a language model on your computer's processor. Nothing you dictate is sent anywhere to be cleaned up.
- Nearby text is read locally and never kept. With Use nearby text for better formatting on (the default), ScreenTray reads up to 500 characters before your cursor in the app you are dictating into, so it can match capitals, numbering and sentence flow. That text is used in memory for that one dictation, never saved, logged or sent, and password fields are never read. You can turn this off in Settings.
- Copy text and background blur run on your computer. Copy text uses Windows' own text recognition. Background blur uses a small model on your computer. Your camera picture is not sent anywhere.
- Microphone, camera and screen access. ScreenTray uses your microphone, your camera, your screen and your computer's sound only when you start a capture, turn on the webcam bubble or Camera page, test your microphone, or dictate. What it captures goes into your files or, for dictation, into the text it types.
- Your settings and library index are local. Preferences, the library index and thumbnails, downloaded models, logs and job history are stored in ScreenTray's app data on your device. We don't have a copy.
- No account required. ScreenTray 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)
ScreenTray is free because, while it is running, 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, adding watermarks or limits, 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. When you open ScreenTray or start a capture while another Clearware app holds the slot, ScreenTray takes it back within a few seconds.
The Exchange runs only while ScreenTray is running. It runs inside ScreenTray itself, through Massive's embedded component; there is no separate Massive app, process or tray icon. It shares while ScreenTray is running, including while ScreenTray sits in the system tray with its window closed. ScreenTray starts when you sign in to Windows by default, so it normally shares from sign-in until you quit it, turn sharing off, or sign out. Quitting ScreenTray stops it, as do signing out of Windows and shutting down. 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 screenshots or recordings, your screen, your camera or microphone, what you dictate, your transcripts, your browsing or search history, the sites you visit, your credentials, cookies, or keystrokes. 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. ScreenTray does not itself instruct Massive's component to keep your computer awake; depending on your system and that component'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.
Your control. You can turn sharing off at any time from ScreenTray's Settings or its tray menu, and quitting ScreenTray stops it too. Note: sharing is what pays for ScreenTray, so while sharing is not running ScreenTray does not start new captures: taking a screenshot, starting a screen or webcam recording, turning on the webcam bubble, and starting dictation are refused until sharing is back on. Your files are never held back. Everything you have captured stays in your library folder and opens in File Explorer as usual; a recording already running keeps running and can be paused, stopped or discarded; and the editor and video preview, sending, trimming, Fit for email, GIFs, captions, the job queue and Settings keep working. Turning sharing back on makes new captures available again within a few seconds. To end participation permanently, uninstall the app, which removes it from your device along with its Massive component and the sharing data it kept.
4. Information the Software collects
Nothing below carries your captures, a file name, a file path, a window title, text you typed or dictated, or a transcript. Apart from feedback you choose to sign, nothing carries your name or email address. The table says which items you can switch off.
| 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; a page opened; a capture started or finished; a capture sent (by copy, email, share or drag); a trim, Fit for email, GIF or caption job started, finished, failed or was cancelled; a model finished downloading; Windows text recognition installed; a dictation finished; the Raw button used after cleanup; a setting changed; the bandwidth exchange changing state; and the app-update lifecycle (update available/downloaded/applied/failed). The only details attached are fixed values: the module id; the kind of capture (screenshot, screen recording or webcam) and what was selected (area, window or screen); the frame rate and resolution setting; the length and file size as coarse ranges; how it was sent; the kind of job; the model name; the name of a setting you changed, never its value or a folder path; for dictation, its length and processing time as coarse ranges, the cleanup level and whether Smart cleanup fell back to Basic; the bandwidth exchange's status; a coarse error category; the update channel (stable/beta); and a public version number. These events are sent to Aptabase and also to Clearware's own usage service, which receives them together with the random install id described in the next row, plus one "app active today" signal per day | Understand which features are used, how reliably, and whether updates are being adopted | On (opt-out) | Aptabase; Clearware (screentray.io) |
| Install-attribution signal | A first-launch ping, and one after each update, containing a random install identifier created by the installer (a UUID) and the app version - no name or email | Measure how many downloads become active installs, and reinstalls | On; follows the Usage analytics switch | Clearware (screentray.io) |
| Install and uninstall signals | When the installer starts - before its agreement pages - it sends the same random install id, the app version, the operating system, a coarse screen-size range, and your computer's Windows machine identifier (MachineGuid). As you move through the installer it reports which step you reached. When ScreenTray is uninstalled, the uninstaller sends the install id, the app version and the machine identifier. The machine identifier is the same one Massive reports, so we can match bandwidth-sharing activity to the download that produced it | Count installs and uninstalls, see where installs stop, and attribute sharing activity to the channel that delivered the install | Always sent; the in-app switches do not control it | Clearware (screentray.io) |
| Install-quality data | Your device's IP address, recorded by our servers when the app is installed, first opened, upgraded or uninstalled, and at each step of the installer. We look up each IP address with ip-api.com to learn its approximate location (such as country, region, city and postal code), its network provider and ASN, and whether it belongs to a hosting or data center network, a proxy, a VPN or a Tor exit. On first launch, the app also sends basic hardware characteristics once: CPU core count, memory size, disk size, whether the computer has a battery, whether it runs under a hypervisor, and the virtualization vendor if it is a virtual machine | Detect fraudulent or non-genuine installs and protect our referral and affiliate program. Not used for advertising profiles | Always on for the installer and uninstaller; the first-launch and upgrade parts follow the Usage analytics setting | Clearware; ip-api.com |
| Feedback | Only when you press Send in the app's Feedback page: your star rating, your note, and the first name and email address if you choose to add them, together with the app version, the operating system, your time zone and your screen size. If Usage analytics is on, the random install id is attached so we can tell which install it came from | Read and respond to feedback, and fix what it reports | Sent only when you send it | Clearware (screentray.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 |
| Model downloads | One-time downloads, when you first need them, of the speech-recognition model you choose (Whisper Base, Small or Large v3 Turbo), the background-blur model, and the Smart cleanup model if you set Smart cleanup up. They are downloaded directly from Hugging Face, which, like any web server, sees your device's IP address and the file requested. The request carries nothing about you, your captures or your dictation. Each model is checked against a fixed fingerprint before ScreenTray uses it | Make dictation, captions, background blur and Smart cleanup work on your computer | Only when a feature that needs the model is first used (Smart cleanup only after you agree to the download) | Hugging Face |
| Windows text recognition | If you click Install in Copy text, Windows downloads its own text-recognition pack for your language from Microsoft, with your permission | Make Copy text work on your computer | Only when you click Install | Microsoft (Windows) |
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, and any value that looks like a URL, a file path or a filename is dropped too. 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. Dictated text, nearby text and transcripts are kept out of logs. Nothing you type into Feedback is passed to crash reporting, analytics or logs. This is a design safeguard, not an absolute guarantee.
5. Information we do NOT collect
We do not collect, and the Software is built not to transmit:
- your screenshots, recordings, GIFs, captions or transcripts, or anything they show or say;
- your microphone audio, your camera picture, or your computer's sound;
- what you dictate, the text ScreenTray types for you, or the text near your cursor;
- the names, paths or contents of any file on your disk, or the titles of the windows you capture;
- the words in your dictionary;
- your browsing history, search history, or the websites you visit;
- your name, email address, passwords, payment details, or precise location (except a name or email address you choose to add to feedback);
- persistent cross-site advertising identifiers.
6. How we use information
We use the limited 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, retention and uninstalls in aggregate, and attribute installs and bandwidth-sharing activity to the channel that delivered them;
- detect fraudulent or non-genuine installs and protect our referral and affiliate program (install-quality data, Section 4);
- read and reply to feedback you send;
- deliver updates.
We do not use it to build advertising profiles or to identify you.
7. Cookies and tracking
The ScreenTray 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 screentray.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 Clarity | Microsoft, as our analytics provider | Records how visitors use the site — clicks, scrolling and mouse movement — as session replays and heatmaps, so we can see where pages confuse people. What you type into form fields is masked and never recorded | 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 |
Asterra click id (asterra) | Us, first-party | When you arrive through one of our Asterra advertising links, the landing URL carries a click id. We store it in your browser (local storage plus a first-party cookie) so that a first launch of the app can be matched back to the link that produced it | 30 days from your most recent Asterra click, then it expires. A newer click replaces an older one |
Affiliate link parameters (st_ap) | Us, first-party | When you arrive through a partner's link marked ?aff=, we store the partner's name and the other parameters on that link (such as the partner's own click id) in your browser (local storage plus a first-party cookie), so that a later download or install can be reported back to that partner | 30 days from your most recent partner-link arrival, then it expires. A newer one 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 — the IP addresses we record for install quality (Section 4) are never added to these reports, and we deliberately declined to start collecting any of those in order to improve ad matching.
What we send to Asterra, and what we do not. Some of our advertising runs through Asterra, whose links carry their own click id. If you arrive through one and later install and open the app for the first time, our server tells Asterra so by requesting its conversion address with that click id. The request carries the click id and nothing else: no install id, no IP address of yours, no email address, no device details. A visitor who declined in the cookie notice never has the click id stored or forwarded, so nothing is sent.
What we send to other partners. When a download or install arrives through a partner's ?aff= link, our server reports it back to that partner using the parameters the partner put on its own link, so that partner can count the conversion. It does not add your IP address, your email address or device details. A visitor who declined in the cookie notice never has the parameters stored or forwarded.
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 any click id being stored — nothing on screentray.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 — screentray.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, partner parameters 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 partner parameters, 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 crash and usage reporting and install and uninstall measurement, to keep the Software secure, stable, and improving, balanced against your privacy (and, for crash reports, usage analytics and the first-launch signal, you can opt out).
- Consent - where required, including your acceptance of the bandwidth exchange at install, and feedback you choose to send; you may withdraw consent by disabling the relevant option or uninstalling.
- Performance of a contract - to provide the Software and deliver updates and the models its features need under the Terms of Use.
9. How information is shared
We share information only as follows:
- Service providers (sub-processors): Sentry (crash reporting), Aptabase (privacy-friendly analytics) and ip-api.com (IP address lookups for install quality) 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.
- Model hosting: the speech, blur and cleanup models are downloaded from Hugging Face, which receives the download request (and so your IP address) under its own privacy policy. We do not send it anything else.
- Update and website hosting providers deliver updates and run screentray.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. When you send a capture yourself, by email, chat, the Share sheet or anything else, it goes to the service you chose under that service's terms; we are not involved.
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. Apart from the install-quality data described in Section 4 and anything you choose to put in feedback, the Software is built to avoid collecting personal identifiers in the first place, so there is very little personal information involved at all.
11. Data retention
- Your captures: stay in your library folder until you delete them. ScreenTray never deletes a capture permanently; Clean up and Move to Recycle Bin only move files to the Windows Recycle Bin. Uninstalling never deletes your captures folder (
Documents\ScreenTray, or the folder you chose), including the captions and the hidden.screentrayfolder inside it. - On your device, everything else: your settings, library index, thumbnails, downloaded models, logs, job history and the sharing data Massive's component keeps stay in ScreenTray's app data until you uninstall. Uninstalling removes them (
%APPDATA%\io.screentray.appand%LOCALAPPDATA%\io.screentray.app), along with ScreenTray's start-with-Windows entry and its values underHKCU\Software\screentray. Dictation audio and nearby text are never saved, so there is nothing to delete. - Crash and usage data: retained by our providers, and by Clearware's usage service, for a limited period consistent with diagnosing issues and understanding trends, then deleted or aggregated.
- Install-attribution, install and uninstall signals: retained in aggregate/measurement form; the random install id is not linked to your identity.
- Install-quality data: IP addresses, the information looked up from them, and hardware details are kept until you ask us to delete them (Section 12).
- Feedback: kept so we can read it and reply; ask us to delete it at any time (Section 12).
- 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. - Asterra click id (
asterra): stored in your browser for 30 days from your most recent Asterra click, then it expires; a newer click replaces an older one. Where it has been used to report a first launch, Asterra's own copy is subject to Asterra's retention schedule, not ours. - Affiliate link parameters (
st_ap): stored in your browser for 30 days from your most recent partner-link arrival, then they expire; a newer arrival replaces them. Where they have been used to report a conversion, the partner'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 ScreenTray is local-first and largely anonymous, the fastest way to exercise most of these rights is directly in the app - turn off telemetry, delete your captures, or uninstall. To make a formal request, or if you're in the EEA/UK, California, or another region with statutory rights, email [email protected] 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 → Privacy & diagnostics | Turn off to stop sending any crash reports |
| Usage analytics | First-run consent screen, and Settings → Privacy & diagnostics | Turn off to stop sending usage events, to Aptabase and to Clearware, and to suppress the first-launch and upgrade signals and the install id on feedback. It does not stop the installer's and uninstaller's own signals, which run outside the app (Section 4) |
| Use nearby text for better formatting | Settings → Capture → Dictation | Turn off and dictation no longer reads the text before your cursor; only the kind of app is used |
| Smart cleanup | Settings → Capture → Dictation → Cleanup | Off unless you choose it. Remove download deletes the model |
| Bandwidth sharing on/off | ScreenTray Settings or ScreenTray tray menu; quitting ScreenTray also stops it | Stops sharing immediately. While it is off, ScreenTray does not start new captures or dictation; your files and everything else keep working (Section 3) |
| End sharing permanently | Uninstall | Uninstalling removes ScreenTray with its Massive component and the sharing data it kept, and ends ScreenTray's participation. Your captures folder is kept |
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.
14. Security
We design the Software to minimize the data at stake: capture, speech recognition, cleanup, blur and text recognition happen on your device, and dictation audio never touches the disk. The app's window has no direct access to your files or the network; privileged work is confined to the app's own process behind a typed bridge. Bundled binaries and downloaded models are checked against a fixed SHA-256 fingerprint before they are used. 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
ScreenTray 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 [email protected] 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 screentray.io). Your continued use of the Software after an update takes effect constitutes acceptance of the updated policy.
18. Contact us
Clearware, LLC Email: [email protected] Web: https://www.screentray.io
For privacy requests, please put "Privacy Request" in the subject line so we can route it quickly.