Nexus Mining

NM COMPANION / NEXUS MINING

Privacy Policy

Last updated: 3 September 2026

This notice explains how NM Companion and the Nexus Mining web service handle data.

English

1. Controller

The controller for NM Companion and Nexus Mining is Thilo Wende. Privacy enquiries can be sent to privacy@nexusmining.net.

2. Data we process

Depending on the feature you use, we process account and Discord identity data, session and pairing data, device identifiers and labels, structured mining data, and optional feedback. Server requests can also create technical security and operational records such as timestamps, route and response metadata, and error information.

We do not use advertising identifiers, third-party advertising analytics, or automatic crash telemetry. This does not mean that no diagnostics exist: operational logs, API metadata and feedback records may be used to keep the service secure and reliable.

3. Local screenshot and OCR processing

Selected screenshots and screen regions are captured and processed locally on your Windows device for OCR. In the normal product flow, full screenshots, OCR crops and other image bytes are not uploaded to Nexus Mining or a cloud OCR service.

Local screenshots, crops or diagnostic files can remain on the device until you remove them. NM Companion does not promise immediate or automatic deletion of every local file.

4. Account, device and pairing data

Nexus Mining uses Discord OAuth to associate a Nexus account with a Discord identity. We may receive and store your Discord user ID, username, display name and avatar reference. We never receive or process your Discord password.

Pairing can store the Nexus user and device association, a device ID and label, token identifiers, timestamps, activity state and relevant account, unit or loadout context. The Companion protects its local device token with Electron safeStorage when the operating system supports it. Removing a paired device ends that device relationship; it is not the same as deleting all account data.

5. Data transferred after confirmation

NM Companion does not silently transfer an unreviewed scan. After you review, correct and explicitly confirm a transfer, it can send structured Rock data such as location, mass, resistance, instability, composition, material names, percentages and quality values. A confirmed refinery transfer can contain refinery, method, processing time, cost, material quantities, quality and yield.

Transfers can also include pairing, device, idempotency, sequence, display and activity metadata needed to authenticate the request, prevent duplicates and present the result in Nexus Mining. Full screenshots and OCR crops are not part of this normal transfer.

6. OCR learning and feedback

OCR learning, aliases and corrections are stored locally by default. Scan feedback can be enabled or disabled in the Companion. Feedback is queued only when feedback is enabled, and automatic sending occurs only when that separate option is enabled. Otherwise, you decide when queued feedback is sent.

Feedback contains structured OCR observations, corrections and technical context needed to improve recognition. It does not contain screenshot, crop or other image bytes. Do not include unnecessary personal information in free-text corrections.

7. Aggregated mining statistics

Confirmed mining data may contribute to aggregated statistics and quality analysis. Contributor identities are not directly displayed in those aggregate views. Aggregation reduces direct identifiability, but it should not be understood as a promise that every record is fully anonymous in all circumstances.

8. Data stored on your device

Local storage can include the protected device token, device name, pairing state, selected location, capture-region settings, user preferences, OCR model assets, aliases, corrections, feedback queue, local logs and files you deliberately import or create. Windows and Electron control the underlying storage protection and file access.

9. Data stored by Nexus Mining

Server-side storage can include Nexus and Discord identity references, account status, web sessions, paired devices, token identifiers or hashes, timestamps, current unit and loadout references, confirmed Rock and refinery records, their material rows, import and idempotency records, aggregated mining data, feedback and operational security logs.

Passwords and raw Companion device tokens are not intended to be stored as readable server-side secrets.

10. External services

Nexus Mining uses Cloudflare infrastructure to host and protect the web service and its data services. Discord provides the OAuth sign-in flow. Their own privacy terms apply to data they process for their services.

The normal NM Companion OCR and transfer flow does not directly contact Google Sheets, Regolith Ops Next, GAS, UEX, community wikis, cloud OCR providers or Microsoft analytics services. Microsoft may process Store, installation or operating-system data under its own terms when you obtain or run the application through Microsoft services.

11. Security

We use measures appropriate to the product design, including HTTPS for network transport, local safeStorage for the device token where available, authenticated loopback sessions, host and origin validation, server-side session and permission checks, and keeping server secrets out of the client. No system or transmission method can be guaranteed to be absolutely secure.

12. Retention

We retain account, pairing, confirmed mining, feedback and operational records for as long as they are operationally necessary, required to protect the service, or needed to fulfil the purpose for which they were collected. The applicable period depends on the data and service state; we do not claim a single fixed period for every category.

Local files remain under your control and may persist until removed. Deleting or disconnecting a device does not automatically delete the complete Nexus account, confirmed mining records, security records, logs or backups. Deletion from logs and backups may follow operational retention and recovery cycles rather than occurring immediately.

13. Access, correction and deletion requests

You can ask for information about your stored personal data, request correction, or request deletion where applicable by emailing privacy@nexusmining.net. We may need to verify your identity and clarify the scope before acting. Some records may need to be retained for security, integrity, legal or operational reasons.

14. Changes to this policy

We may update this notice when product features, data handling or service providers change. The date at the top identifies the published version. Material changes will be reflected on this public page.

15. Contact

Privacy contact: privacy@nexusmining.net.