Stenfox

/ Certified data wipe

Proof, not promises. Reports auditors can trace.

Every Stenfox wipe closes with a signed report: which device, which method, what verification found, who ran it and when. A scannable label goes on the unit and the history stays in the portal.

Data erasure report

PDF · JSON

Data erasure report

SFX-2026-0914-00482

Device
MacBook Air M2, 512 GB
Serial
C02•••••••Q6L
Method
NIST 800-88 Purge
Verification
Passed
Operator
Station 04
Completed
2026-09-14 10:42 UTC

Erasure verified

What you get

01

Signed report per device

Each report is signed and records the device, the erase method, the verification result, the operator and the time.

02

Verification in the record

Drive erasure is verified by read-back; phones, tablets, Macs and smart TVs get a verified outcome. The result is in the report, pass or fail.

03

Scannable label

Print a scannable label on any standard label printer, so the physical unit and its record stay linked.

04

Device identity

IMEI and serial scan-and-match on phones and tablets, and serial numbers on computers and drives, tie each report to one unit.

05

Operator identity

Every report names the operator who ran the erase, so accountability is concrete, not implied.

06

Full history in the portal

Reports and device history live in Stenfox Portal, ready to pull for an audit or a customer request.

Stenfox Portal

Workflows, grading forms, reports
  1. Intake

  2. Diagnose

  3. Erase

  4. Report

  5. Route

/ FAQ

Frequently asked questions

What's in a Stenfox erasure report?

Each signed report records the device, the erase method, the verification result, the operator and the time. For drives the method is one of 22 selectable methods, from NIST SP 800-88 Clear and Purge to Gutmann, verified by read-back. For phones and tablets it is a factory reset or a full firmware restore with a verified outcome.

How is this different from reports produced by legacy erasure suites?

Legacy erasure suites and standalone drive erasers usually report on the wipe alone. An Orion report sits in the same device record as the diagnostics, lock and ID checks and grading, with a scannable label on the unit and the full history in Stenfox Portal, so an auditor can trace a device from intake to disposition.

Is Stenfox certified by ADISA, NIST or R2v3?

No. Stenfox holds no third-party certification. Orion follows the Clear and Purge guidance of NIST SP 800-88 Rev. 1 and Rev. 2, and its reporting is built around NIST SP 800-88, IEEE 2883, ADISA, R2v3, GDPR and GSMA. Certified processors can use its signed reports as evidence in their own audits.

Will the report stand up in a HIPAA, SOX or PCI-DSS audit?

The signed report is ready for HIPAA, SOX and PCI-DSS audits: it records the device, the method, the verification result, the operator and the time, and the full device history stays in Stenfox Portal. It is evidence your auditor reviews, not a certification; Stenfox holds no third-party certification.

What happens if a report is lost?

The full history stays in Stenfox Portal, so the report can be pulled again from the device record at any time. Scan the label on the unit to find it.

What happens when an erase fails?

The report records the failure. A failed verification is never counted as a pass, and on smart TVs an unconfirmed outcome is reported as unconfirmed, not as a pass. The workflow's fail branch routes the device to the next step you define.

Next step

See it run on your own devices.

  • Live demo on your own devices
  • Pilot in your workshop before you commit
  • Direct line to our engineers
  • Onboarding and training for your team

Tell us what you process and at what volume. We reply within one business day.