Account and device information
Sign-in is handled by auth.mattmade.ai. Selfwipe receives your account identifier, name, email, and authentication information. The service stores device names, operating system and processor details, agent versions, reported encryption and erase capability, and check-in timestamps.
The agent generates its own signing identity. Its private device key stays on the device. The cloud stores the public key and enrollment information. Erase authorization codes are shown once during enrollment; the service retains a verification hash rather than the readable code.
Commands and activity
We store queued commands, device acknowledgments, and account activity to deliver requests and show their status. Commands contain fixed actions rather than arbitrary scripts. Selfwipe does not upload the contents of your disks.
Cookies and usage measurement
Authentication cookies keep you signed in. First-party analytics uses a random browser identifier in a cookie called sw_vid, lasting up to one year, and a session identifier in browser session storage. A new analytics session starts after 30 minutes of inactivity.
Analytics records public page paths, predefined button labels, the platform installation guide selected, and whether a page started the session. It does not collect form contents, query strings, enrollment codes, erase authorization codes, device names, email addresses, or raw IP addresses. Account identifiers may link usage to an authenticated account. Enrollment and command activity comes from the service’s own records.
Analytics is sent to Selfwipe’s own service. We do not embed third-party advertising trackers. Hosting and database providers process service data to run the application; their infrastructure may maintain operational and security logs separately.
Storage and requests
Account, device, and command records remain available to operate the service and provide activity history. Contact support@mattmade.ai to request access, correction, or deletion of your Selfwipe information. We may need to verify account ownership before acting. Never include device private keys or authorization codes in a support message.
Keep secrets separate
Keep your erase authorization code somewhere you can reach from another device. Removing local cookies does not delete server records, and erasing a computer does not erase data or credentials already copied elsewhere.