Information We Collect
1.1 Website Information
- Account Information: Email address, password (securely hashed), and profile details you provide when creating an account.
- Transaction Data: Purchase history, subscription details, and billing information processed through Stripe (we do not store full credit card numbers).
- Support Communications: Support ticket content, email correspondence, and any translations generated for multi-language support.
- Analytics Data: Pages visited, session duration, browser type, and device type. We use our own privacy-preserving analytics — visitor identification uses daily-rotated salted hashes (not persistent tracking IDs). Raw analytics data is automatically purged after 90 days.
1.2 PNT-RMMS Desktop Client Data
When you install and use the PNT-RMMS software, the following data is collected and transmitted to our servers:
- Device Information: Computer hostname, domain membership, operating system type and version, CPU specifications, memory (RAM) capacity and usage, disk storage capacity and usage, and network adapter details.
- Network Data: Local and public IP addresses (public IPs are stored as salted hashes, not in plaintext), connection status, and availability metrics.
- Agent Metadata: PNT-RMMS software version, device identification tokens, and license validation data.
- Diagnostic Logs: Warning-level and above application logs are automatically submitted to our server for centralized troubleshooting. Logs are deduplicated and batched (maximum 50 entries per submission). Personal data is not included in diagnostic logs.
1.3 Remote Access Session Data
When a remote support session is initiated, the following data may be collected:
- Session Metadata: Session start/end times, duration, administrator identity, connection type (relay or peer-to-peer), and session status.
- Screen Content: During active remote viewing sessions, screen frames are transmitted in real-time to the authorized administrator. Frames are encrypted in transit (TLS) and may be end-to-end encrypted (AES-256-GCM with ECDH key exchange).
- Session Recordings: If session recording is enabled, screen frames and metadata may be stored for compliance and training purposes.
- Audit Logs: All remote actions (commands executed, files transferred, services modified, processes managed) are logged for security and compliance purposes.
1.4 Peer-to-Peer Connection Data
PNT-RMMS supports direct peer-to-peer (P2P) connections using WebRTC technology:
- ICE/STUN Data: Your device's network address information is exchanged through our STUN server (stun.pronovatech.com) and a public Google STUN server as fallback to establish direct connections.
- TURN Relay: When direct P2P connections cannot be established, session data is relayed through our TURN server (turn.pronovatech.com). Relay data is encrypted and not stored.
1.5 RMMS End-User Portal Data
If you use the RMMS self-service portal to manage your company and devices:
- Company name, contact information, and organizational structure.
- Team member invitations, roles, and device permission levels.
- Support agreement consent records (text version, timestamp, IP address).