NgSense · Privacy and Workflow
Why structured feedback should stay separate from anonymous analytics
Structured feedback and anonymous analytics answer different questions. Keeping them separate makes the product easier to trust and makes support workflows easier to reason about.

On this page
If you need to report a problem, use Contact / Feedback. Anonymous usage events are not a support ticket and do not give us your description or a way to reply. Feedback is a separate message you choose to send; contact information is optional.
Anonymous analytics and structured feedback are not the same signal
Anonymous analytics exists to observe aggregate product behavior. Structured feedback exists to carry a message, context, and sometimes optional contact information. One is telemetry about usage patterns. The other is a request, report, or conversation starter.
Why the boundary matters for trust
People evaluating a local-first tool often ask a simple question first: what data goes where? If a site says the product is privacy-aware but quietly mixes behavior analytics with structured feedback content, the boundary becomes harder to explain and harder to trust.
Why the boundary matters for support
A useful report contains only the context needed to understand the problem:
- Product and app version
- Platform and a broad source category, such as USB or RTSP, when relevant
- The action you took
- Expected behavior and the actual result
- A visible error after removing private details
Do not include passwords, complete RTSP addresses, LAN IPs, file paths, private documents or desktop screenshots by default. Send a small example only when you deliberately choose to disclose it. A report is not an automatic upload of your files, and anonymous events are not a substitute for that report.
What this means on the NgSense website
The site keeps anonymous behavior measurement in a narrow role only. Messages sent through Contact stay on a dedicated feedback path instead of being hidden inside simple usage measurement.
Choose the help page for your product
Start with ScopeDock camera checks, LoveMarkDown file and export help, FocusHop display and shortcut help, or Web Launcher webpage display help. Product-specific permissions, network behavior and privacy policies can differ; do not treat one app’s local-file promise as a brand-wide guarantee.
The practical next step
Use the support page to try the documented check. If it still fails, send feedback and choose whether to provide a contact address for follow-up. Submission does not promise an immediate reply, a diagnosis or device compatibility.
Next with NgSense
- Compare NgSense products
Find camera, Markdown, multi-display, and Android webpage-display apps by task and platform.
- Choose an installation channel
Compare the verified installation paths for each NgSense app.
- Send feedback
Share a product question or request through the structured feedback form.