Account and portal data
- Organisation name and plan type so your licence profile and dashboard can be created.
- Contact name and work email so setup, support, renewal, and password emails can be sent.
- Address details for account setup, invoicing, and subscription records.
- Support tickets, attachments, and replies submitted through the portal.
Client check-in data
- Tenant ID, environment, licence mode, and organisation name from the deployed profile.
- Hashed device identity, hostname, macOS version, DockPilot version, and last check-in time.
- Licence state such as trial, licensed, grace, expired, or offline cached state.
- Active device count for support visibility.
Website analytics
- Public website page views and referrers.
- Approximate country or region, browser, and device type.
- Popular pages so DockPilot can improve documentation, pricing, and signup journeys.
- Admin, customer portal, support, setup, sign-in, password reset, and API routes are excluded from DockPilot website analytics.
Data DockPilot avoids
- No raw serial number is sent to the backend.
- No full inventory collection.
- No personal files, documents, emails, or browser history.
- No full enrolment token or device token in UI or logs.
Why this data is needed
DockPilot needs enough information to issue a licence profile, identify enrolled Macs, show support status, pause managed Dock actions when licensing expires, and help support diagnose deployment issues.