What MAST collects, and what stays with you.

Device and service data

The service records account information, phone model and OS, app inventory and permissions, install and usage information, browser notification settings, scan scores, your keep/remove/restore choices, and device action history. iPhone intake may include battery, activation and lock information.

Serial numbers and IMEIs are hashed on the computer before reaching the API, except for IMEI lookups. When you run an IMEI lookup, MAST sends the raw IMEI through its API to SickW to check carrier, blacklist and Find My status. MAST does not store or log the raw IMEI. Records are associated with your account and hashed device identifier. Professional service history relates to the shop's ticket; shops keep customer identity in their own systems.

Computer and diagnostics data

Computer records include OS build, hardware, USB and driver state, app version, conflicting software, network identifiers and a hashed machine fingerprint. IP addresses support security and license enforcement. Diagnostics you choose to send include crash records and redacted service logs.

These records support detection improvements, service history, troubleshooting and license enforcement.

Content excluded from collection and sharing

Message content, backup contents and exported files never reach the API and are never shared with anyone by MAST. Contacts, call logs, photos, phone account names and location are not collected. Backups, message exports and printing run locally on your computer.

Proposed sale or sharing disclosure

The proposed policy would allow device information and app inventory data to be sold or shared with analytics providers and marketing companies for analytics and marketing. This describes a proposed use, not a claim that data is currently sold. Final categories, recipients and purposes must be confirmed in the reviewed launch policy.

Do Not Sell or Share — account portal. Sign in to view your organization’s privacy preference. An account owner can change it there.

Policy changes and requests

The launch policy will be versioned and accepted at signup, with re-acceptance for material changes. Retention, deletion and access-request procedures will be included in the reviewed policy before launch.