AI Companions

Companion Device Retention for Institutional Buyers

Illustrative rendering of a companion device form factor
Illustrative rendering of the form factor — ask for production photographs of the exact build before printing a shelf talker. Illustrative rendering, not a photograph of a shipped unit.
TITLE: Companion Device Retention for Institutional Buyers DESC: Companion device retention policies matter when care groups manage data lifecycles across EU/UK institutions — here’s how WingPhoenix documents export, deletion and audit scope per hardware revision. KEYWORDS: companion device retention, institutional data policy, retention class, export compliance, audit readiness TAGS: compliance, procurement, data governance, B2B, healthcare Q: What does “companion device retention” mean for an institution procuring AI devices? A: It defines how long personal or operational data stays on the device or in associated cloud services, how it is exported or deleted upon request, and whether that process is auditable under local law. WingPhoenix documents retention scope per hardware revision, not per model family. Q: How does finance or compliance verify that retention claims are enforceable? A: They require written policy tied to a specific firmware version and hardware revision, with test reports confirming deletion mechanics and export formats. WingPhoenix supplies these documents only after factory validation, not during quotation. Q: A distributor received a sample where the app showed cached voice logs beyond 72 hours — what changed? A: The sample ran pre-release firmware; retention behaviour is validated only at FQC stage against the final firmware image shipped with production units. All factory testing gates include retention logic verification. Q: What is the one question most suppliers dodge about companion device retention? A: Whether full local-data deletion leaves no recoverable artefacts on flash memory or internal storage. WingPhoenix does not claim forensic erasure — our documented retention class covers logical deletion only, verified by factory-level read-back tests on NAND and eMMC partitions.

Data residency and export scope

WingPhoenix does not operate cloud infrastructure. All companion devices — including the companion robot, smart health ring and health smartwatch — store data locally unless integrated into a customer’s own backend via OEM/ODM services. Export functionality is limited to CSV or JSON payloads generated on-device or via authenticated API calls. No export includes raw sensor binaries, firmware logs or unprocessed audio fragments. Export format and field naming are defined in the OEM/ODM agreement, not in standard firmware.

Deletion mechanics and validation

Logical deletion removes user-generated content (voice notes, activity entries, custom prompts) and associated metadata from the device’s primary storage partition. It does not overwrite NAND blocks or perform cryptographic erasure. Validation occurs at FQC using factory-defined test scripts that confirm absence of target files post-deletion command. This is documented in the factory test report for each hardware revision. Deletion triggers do not extend to system partitions, bootloader logs or diagnostic buffers — those remain inaccessible to end users and are excluded from retention scope.

Audit readiness and documentation

WingPhoenix supplies retention-related documentation only after mass production release: a retention class statement (e.g., “Class B: 72-hour cache, manual-triggered export, logical deletion”), a firmware version hash, and a summary of factory validation steps. These are included in the CE RED document checklist package alongside radio test reports. No retention claim is made in pre-production quotations or samples. Audit evidence is tied to the exact hardware revision and firmware build shipped — not to model names or marketing categories.

Retention class definitions

Retention class is assigned per hardware revision and reflects how long user data persists without manual intervention. Classes are not aligned to GDPR or UK Data Protection Act schedules — they describe technical behaviour only. Class A applies to devices with no persistent local storage (e.g., certain AI wearables with RAM-only operation). Class B applies to companion and health devices with flash storage and user-initiated export/deletion. Class C applies to learning pad models with optional SD-card logging — where retention is governed by the card’s file system, not the device itself.

Where to say no to a supplier claim

Do not accept any supplier claim that their companion device meets “GDPR-compliant deletion” or “audit-ready erasure” without seeing the factory validation report for your exact hardware revision. WingPhoenix does not offer certified erasure, forensic wipe, or tamper-evident deletion logs. If your institution requires verifiable zero-recovery assurance — for example, for devices deployed in secure care facilities — this capability is outside the current retention class scope. Such requirements must be scoped in OEM/ODM services and validated separately with accredited labs.
Decision point What WingPhoenix provides What requires OEM/ODM engagement
Data export format CSV/JSON payload, field-named per revision Custom schema, encryption, SFTP delivery
Deletion trigger User-initiated, local only Remote command, MDM integration, timed auto-purge
Audit evidence Firmware hash + factory test summary Third-party lab report, ISO 27001-aligned log retention
Storage medium eMMC or NAND, no removable media Removable SD, encrypted USB, enterprise SSD
Retention class assignment Per hardware revision, documented at FQC Custom class definition, signed validation letter
Compliance reference No legal or regulatory certification claimed GDPR Article 17 mapping, UK ICO guidance alignment

WingPhoenix treats companion device retention as a hardware- and firmware-bound engineering outcome — not a marketing promise. That means every retention class statement is testable, versioned and traceable to a physical unit. To begin the process, review the MOQ, sampling and lead times page, then request a retention class statement for your target hardware revision using the product catalogue reference number and intended deployment context.

Questions buyers ask

What does “companion device retention” mean for an institution procuring AI devices?

It defines how long personal or operational data stays on the device or in associated cloud services, how it is exported or deleted upon request, and whether that process is auditable under local law. WingPhoenix documents retention scope per hardware revision, not per model family.

How does finance or compliance verify that retention claims are enforceable?

They require written policy tied to a specific firmware version and hardware revision, with test reports confirming deletion mechanics and export formats. WingPhoenix supplies these documents only after factory validation, not during quotation.

A distributor received a sample where the app showed cached voice logs beyond 72 hours — what changed?

The sample ran pre-release firmware; retention behaviour is validated only at FQC stage against the final firmware image shipped with production units. All <a href="https://wingphoenixai.com/factory/">factory testing</a> gates include retention logic verification.

What is the one question most suppliers dodge about companion device retention?

Whether full local-data deletion leaves no recoverable artefacts on flash memory or internal storage. WingPhoenix does not claim forensic erasure — our documented retention class covers logical deletion only, verified by factory-level read-back tests on NAND and eMMC partitions.

Related: more on ai companions · buyer guides · customisation tiers