Purpose and scope
Draft — to be reviewed by legal counsel before publication
This policy transparently explains what RebootGuard records on your PCs, what is sent to Star Soft and why, and what is never collected. It supplements the Privacy Policy.
Core principles
- Data minimization: we collect only what is needed to run licensing, provide support and protect the service.
- Local by default: operational logs stay on your PCs and are not sent to us automatically.
- Explicit consent: diagnostic logs are uploaded only with your consent each time.
- Secrets excluded: logs are designed not to contain passwords, activation codes, keys or tokens.
- Limited retention: every data category has a defined retention period.
Local logs on admin and gaming PCs
The Master Console and the Client agent create local operational logs that include:
- Protection mode changes (enable, disable, Maintenance mode).
- Commands sent from the Master Console to PCs and their results.
- Errors, warnings, and service start and stop events.
- Activation and license validation events.
These logs are stored on your PCs under your control and are sent to the Company only through a diagnostic upload you explicitly approve.
Data sent to the license server
| Item | Purpose |
|---|---|
| Activation ID | Linking the installation to the correct license |
| Hashed device fingerprint (no raw serial numbers) | Preventing the same activation from being used on multiple machines |
| Machine name | Helping you identify your activations in the customer portal |
| Product version | Checking compatibility and targeting updates |
| Number of managed devices | Verifying compliance with the plan limit |
| Timestamps | Managing leases and the offline grace period |
| IP address | Security and abuse prevention |
Only the Master Console sends this data; gaming PCs do not contact the license server directly.
Website, security and audit logs
- IP address and user agent are recorded on sign-in and sensitive actions for security purposes.
- Administrative and sensitive actions are recorded in a tamper-evident, hash-chained audit log, so any later modification can be detected.
- The strictly necessary cookie rg_session is used only to maintain your session; no tracking or advertising cookies are used.
Diagnostic log uploads
- 1Support requests logs when needed, within a specific support ticket.
- 2The software assembles the diagnostic package locally, and you can review its content before sending.
- 3The upload happens only after your explicit consent to that specific upload; consent does not extend to any later upload.
- 4Logs are used solely to resolve the related ticket.
- 5Logs are deleted 90 days after the ticket is closed.
What we never collect
- User files and documents.
- Passwords typed on the PCs.
- Browsing history and keystrokes.
- Screenshots.
- Game data or player accounts.
- Personal data of venue visitors or players.
Retention
The periods below are draft values.
| Category | Retention period |
|---|---|
| Local logs | Determined by the customer on their own PCs |
| Security and audit logs | 12 months |
| Uploaded diagnostic logs | 90 days after the ticket is closed |
| License and activation records | For the life of the license plus 24 months |
| Account data | For the life of the account, and up to 24 months after closure where legally required for invoicing |
| Contact and quote requests | 12 months |
Access and protection
- Only authorized staff can access data, through role-based permissions and only as far as their work requires.
- Multi-factor authentication is mandatory for all staff.
- Data is transmitted over TLS-encrypted connections.
- Rate limiting and temporary lockouts apply after repeated failed attempts.
- Access to data and sensitive actions is recorded in the audit log.
Your choices and rights
- You can decline to upload diagnostic logs; this may limit our ability to analyze some issues.
- You can ask us to delete previously uploaded diagnostic logs before the retention period ends.
- You can exercise the rights of access, export, correction, deletion and objection described in the Privacy Policy via the support page or at [privacy contact email]; we will respond within 30 days.
Changes and contact
We may update this policy when the way the software works changes, and we will notify customers of any material change in the data collected before it takes effect.
Questions: [privacy contact email] — Star Soft, [Star Soft legal address].