Remedexa is currently in development and is not yet available for purchase.
Security & privacy
Remedexa is designed to collect the technical evidence needed to understand a Windows problem while avoiding unrelated personal content and broad system changes.
Trust model
This page explains the product’s security and privacy philosophy. It is not a legal privacy policy, a certification list, or an infrastructure diagram.
Remedexa is designed to understand the affected function before it applies a repair.
Changes should stay related to the diagnosis and avoid unrelated Windows modifications.
A repair step completing is not treated as proof that the user’s problem is resolved.
Diagnostics are designed to keep the technical evidence needed for troubleshooting and avoid unrelated personal content.
Conservative repairs
Repairs should follow diagnosis, stay with the affected target, and use the least-disruptive reasonable action. A command succeeding is not treated as proof that the problem is resolved.
A repair should be justified by what the investigation found, not by a generic cleanup list.
Where the evidence supports it, work focuses on the affected component rather than the whole PC.
Remedexa is designed to prefer the least-disruptive reasonable change when a repair is appropriate.
Arbitrary driver downloads are avoided. Windows-supported mechanisms are preferred where appropriate.
Validation as a safety control
Remedexa retests the affected function where the troubleshooting profile supports functional validation. If validation still fails, the issue should not be labeled resolved. Validation reduces false “fixed” outcomes. It does not eliminate all risk.
Repair execution
Problem resolved
Diagnostic data
Remedexa needs enough technical context to understand the selected problem. The exact evidence depends on the profile. This is not a list of proprietary diagnostic rules.
Needed for troubleshooting
Categories that may be relevant to a given problem area.
Designed to avoid
Diagnostics are designed to avoid collecting unnecessary personal content such as:
Personal content
Remedexa diagnostics are designed to avoid collecting passwords, tokens, typed content, microphone or camera recordings, diagnostic screen captures, and arbitrary user documents. That is not a claim of zero data collection, complete anonymity, or that nothing ever leaves the device.
When Business support is requested, the workflow may transmit sanitized technical evidence. That is a support action, not a standing upload of personal content.
Remedexa Home
Home is designed around local diagnosis, conservative repair, and validation on the Windows PC the user is repairing.
Troubleshooting is primarily performed on the Windows PC.
Home requires legitimate online activation. It is not described as never contacting Remedexa infrastructure.
An activated perpetual Home entitlement is designed to remain usable offline.
Home does not include technician tickets, remote support, or Business monitoring.
Remedexa Business
Business uses the same local troubleshooting loop. Cloud and support capabilities are added around that loop. An unresolved result is not treated as an automatic upload.
The same troubleshooting foundation runs on the employee’s PC.
A targeted change is applied when an appropriate repair exists.
The affected function is retested where the profile supports it.
If the issue is verified, the loop stops. Diagnostic information is not treated as automatically uploaded.
If the user invokes support, structured technical evidence can travel with the request.
A support case can lead to technician review and attended remote support if required.
Support packages
A Business support package is intended to contain relevant technical evidence for the unresolved problem, and to avoid unnecessary personal content. Exact payload fields and retention periods are not published here.
Attended remote support
Business may provide attended remote support when automated troubleshooting is not enough. Exact consent screens, session-recording behavior, and provider capabilities are not claimed here.
Human intervention is intended for cases where local troubleshooting is not enough.
Attended remote support is initiated as part of a support case, not as always-on access.
Employee or user participation and consent are part of the attended model.
Remote support should not be understood as permanent unattended monitoring of the PC.
Health awareness
Business may include lightweight endpoint health awareness to support troubleshooting. It is not employee monitoring.
Lightweight health awareness is intended as technical endpoint context that can support troubleshooting and support.
It is not screen, keystroke, productivity, microphone, camera, or browser-history monitoring.
It is not a mature fleet-management or surveillance platform.
Broader company and device management remains future capability.
Transparency
Remedexa is designed to provide a clear record of troubleshooting activity. That is not a claim of a complete forensic audit or a tamper-proof log.
What this page does not claim
Product security and privacy design is not the same as a published compliance certification. Remedexa will only publish certification or regulatory claims when they are actually established. This page does not preview upcoming badges or treat unfinished commercial or compliance work as complete.
Questions
Remedexa diagnostics are designed to avoid collecting arbitrary user documents. The intended evidence is technical context related to the problem being investigated.
Diagnostic collection is designed to avoid diagnostic screen captures. Attended remote support, when used in Business, is a separate human support session and is not presented as screen recording or surveillance.
Diagnostics are designed to avoid collecting microphone recordings and camera recordings or frames. Remedexa may still investigate whether those devices are available to Windows.
Home requires a legitimate online activation step. Once activated, the perpetual Home entitlement is designed so the application can continue to be used offline. Home is not described as never contacting Remedexa infrastructure.
No. Lightweight health awareness is intended as endpoint health context for troubleshooting. It is not employee activity, productivity, or screen monitoring.
Local troubleshooting can complete without opening a support case. Structured technical context is intended to be sent when support is invoked, not automatically for every unresolved event.
No. Attended remote support is intended as a support-workflow session with user participation. It is not permanent unattended access to the PC.