1. Overview & Privacy Principles
OSResolve is engineered with a strict principle of least privilege, zero personal data harvesting, and server-authoritative integrity:
- Zero Personal Data Harvesting: OSResolve does not collect user names, browsing history, files, documents, passwords, or personal credentials.
- Standard-User Execution: The main graphical user interface runs strictly as a standard Windows user (
asInvoker). - No Unrelated Hardware Telemetry: OSResolve does not scan, profile, or collect unrelated hardware serial numbers, MAC addresses, or invasive hardware identifiers.
- Transparent Communication: All communications with the server use secure HTTPS and are strictly limited to device registration, diagnostic telemetry evaluation, signed repair plan generation, and security audit integrity.
2. Server-Authoritative Entitlement & Diagnostic Checks
A. Pseudonymous Device Identifiers
- When communicating with the OSResolve Server Intelligence Engine, OSResolve creates a pseudonymous device identifier by computing a one-way cryptographic SHA-256 hash of the Windows Machine GUID.
- This pseudonymous identifier (
dev-<sha256_hash>) is bound strictly to the device's entitlement records. - It cannot be reversed to discover user identities or hardware serial numbers.
- Limitation Notice: In accordance with industrial security engineering, pseudonymous device identifiers alone do not constitute conclusive cryptographic identity proof against sophisticated local hardware or operating system reinstallation attacks.
B. Free Tier & Entitlement Policy
- Diagnostic Scans: New and existing free devices receive unlimited complimentary diagnostic scans.
- Initial Repair Opportunity: New devices receive one (1) initial complimentary opportunity to generate and execute an authorized repair plan for identified system anomalies.
- Subsequent Repairs: Once the initial repair opportunity is consumed, further repair plan generation requires an active Professional entitlement verified by the authoritative backend. Diagnostic scanning remains free and unrestricted.
- Server Authority: Entitlements, scan allowances, and repair opportunities are tracked transactionally and authoritatively on the backend. Local preference files, client flags, or registry edits cannot authorize a repair.
3. Security Event Logging & Abuse Prevention
A. IP Address Processing
When requests are received by the OSResolve API, the source IP address is observed by the server for standard transport logging, rate limiting (maximum 10 requests per minute for sensitive endpoints), and abuse protection. IP addresses are processed strictly for technical integrity and defense against automated attacks. An IP address is never treated as conclusive proof of an individual's personal identity.
B. High-Confidence Security Alerts
If the server detects high-confidence malicious activity or policy violations—specifically:
- Forged or altered cryptographic plan signatures;
- Replay attacks attempting to reuse previously consumed nonces or authorization identifiers;
- Repeated unauthorized attempts to forge repair executions;
- Device suspension events;
A sanitized notification is logged and dispatched to authorized engineering operations (pj.debbarma@gmail.com).
C. Secret Redaction Guarantee
Security event alerts strictly omit credentials, tokens, passwords, private keys, and user documents. The notification payload includes only: UTC timestamp, event type and severity level (CRITICAL / HIGH), observed source IP address, pseudonymous device ID, redacted account reference (if authenticated), Windows version / build, OSResolve application version, affected plan / correlation identifier, and technical rejection reason.
4. Device & License Suspension Policy
Suspension for Confirmed Abuse: Devices confirmed to have generated forged cryptographic audits or repeated signature bypass attempts are placed into a suspended state (isBlocked = true) by the server.
Protections for Normal Failures: Normal operational events—such as standard UAC prompt cancellations, network disconnects, failed repair step verifications, or restore point creation failures—never trigger an abuse suspension.
Administrative Review: Suspended device records maintain an auditable event history and can be reviewed and unblocked by authorized administrators via /api/v1/admin/devices/unblock.
5. Data Retention & Deletion Schedule
- Diagnostic Telemetry: Transient diagnostic payloads submitted for real-time classification are processed in-memory and retained for no longer than 30 days for operational debugging.
- Execution Audit Records: Audit logs of executed and rolled-back repair transactions are retained for 90 days to support user support inquiries and cryptographic verification.
- Security Event Logs: High-confidence security logs are retained for 90 days for forensic analysis and threat intelligence, after which they are automatically purged.
- Deletion Requests: Users may request the deletion of all pseudonymous device bindings and transaction logs associated with their account by contacting pj.debbarma@gmail.com.
6. Contact Information
For privacy inquiries, technical audits, or vulnerability disclosures, contact:
Pijush Debbarma
Website: https://www.pijush.in
Email: pj.debbarma@gmail.com