Telemetry Policy

Caution

CoreSystem does not collect deployment data. Inventory is written locally on every deployment. MSP Advanced can forward it using the private package supplied with the license.

CoreSystem Commitment — No Collection

• Personal data (name, account, password, email)
• Profile contents (unattend.xml, Post-setup.ps1, tweaks)
• License information (*.lic, user-config.json)
• Data on the workstation’s hard drive

What Is Recorded

Every deployment writes one inventory record with hardware, firmware, OS and deploy context — enough for asset inventory, lifecycle and warranty tracking:

Group	Examples
Device identity	device_key (SHA-256 UUID), serial, UUID, manufacturer/product
Firmware	BIOS, UEFI/Legacy, Secure Boot, TPM
Hardware	chassis, CPU, RAM, disks
Deployment	OS build/edition/language, mode, profile, image, target disk, duration, result
USB	usb_serial, usb_brand

Serial numbers and UUIDs are device identifiers (not personal data). MAC addresses are not part of the local record. See Inventory Data for the full schema.

Data Storage

Tier	Storage
Free	Local Inventory-*.json + .csv on the OS volume (C:\) and the USB — never sent anywhere
MSP Advanced	The same local files. Additional forwarding options are covered in the private package supplied with the license.

Note

Local-first delivery. Inventory JSON/CSV is written with write-through + verify before the reboot. If the network is down, the deployment continues and the local files remain the source of truth.

Frequently Asked Questions

Does CoreSystem receive my data? No. Data remains only on your USB/OS volume or at your endpoint.

Does CoreSystem read my Profiles? No. Profiles are stored only on the USB and executed locally on the workstation.