adirh3
Request for Public License & Privacy Policy Transparency
@adirh3 Thanks for all the hard work on Fluent Search. It’s an incredibly useful tool, and I really appreciate the effort you’ve put into building and improving it.
That said, I (and others) have concerns about the lack of publicly available licensing terms and a clear privacy policy, especially given the level of system access Fluent Search requires. Since the software interacts with critical OS components, running processes, file indexing, and browser tabs, transparency about data collection, storage, and user control is crucial for user trust and security.
1. License Transparency
- In Issue #1121, you mentioned:
"Hey, the installation folder contains a license file in COPYING.txt, and it shows in installer/MS store as well. The GitHub does not have a license as it doesn't contain code."
- While it’s helpful to know the license file exists after installation, it would be more transparent if the COPYING.txt file were (or its content) publicly accessible— in this repository and on the website.
- Since Fluent Search is not open-source, it’s even more important for users to be able to review licensing terms before installation to understand usage rights, restrictions, and distribution terms.
2. Privacy Policy & Data Access Concerns
- Fluent Search does not currently have a privacy policy listed on its website.
- Given that Fluent Search requires deep system access for features like searching running apps, browser tabs, and system files, it is critical for users to understand:
- What data (if any) Fluent Search collects and whether it logs user activity.
- Where the data is stored (local machine only, or transmitted externally).
- Who, if anyone, has access to this data (Fluent Search, third-party services, OS-level integration).
- How long any collected data is retained (if applicable).
- Whether users have control over data collection (can it be disabled?).
- Many applications with similar system access explicitly document their data handling policies, and it would be reassuring if Fluent Search provided the same level of transparency. This is a conundrum, because certain actions the app may take upon installation or running, may not be fully undone with uninstalling the app, but users can't know this BEFORE they install it. I am sure you can see the paradox.
3. Why This Matters
- Fluent Search’s deep integration into file systems, running processes, and browser data means it interacts with sensitive user information. While I have no reason to believe the software misuses this access, clarity and transparency are essential when an app operates at this level.
- Many users are increasingly cautious about privacy, and a detailed, publicly accessible privacy policy would go a long way in building trust and reassuring users that their data is handled responsibly.
- Right now, users must install Fluent Search before they can review the privacy policy, which isn’t ideal for those who want to make an informed decision before granting system access.
Suggested Actions
- Make the license file publicly available (in this GitHub repository or on the website).
- Publish the privacy policy on the website, ensuring it clearly details data collection, storage, and user control.
- Explicitly clarify whether Fluent Search transmits or retains user/system data, and if so, provide users with clear opt-out settings.
I fully understand that Fluent Search is a productivity tool, not spyware, but privacy concerns are not about developer intentions—they're about clear, documented policies that users can rely on. Given the deep system integration Fluent Search has, a transparent privacy policy is not just a feature—it’s a necessity.
I hope you’ll consider these suggestions. Thanks again for all your work on Fluent Search!
