# Qurmmius vendor approval packet — 2026-09-13

Status: packet prepared; outreach has not been sent and no vendor approval is implied.

## Request in one paragraph

Qurmmius LLC is seeking written confirmation of permitted use for the named SDKs, runtimes, devices, and telemetry interfaces used by its controlled-release prototypes. The company will use only documented, user-consented interfaces and will not bypass anti-cheat controls, read console memory, identify devices by MAC address, silently capture media, or represent a vendor as an endorser without written permission.

## Evidence provided

- [Apex Academia PC adapter and telemetry matrix](APEX-ACADEMIA-PC-ADAPTER-MATRIX.md)
- [Palimpsest + EraWeaver rights checklist](PALIMPSEST-ERAWEAVER-RIGHTS-CHECKLIST.md)
- [Deepfake Shield internal acceptance](DEEPFAKE-SHIELD-INTERNAL-ACCEPTANCE.md)
- [Vendor approval register](data/vendor-approval-register.json)
- [Product hardware acceptance form](https://qurmmius.com/hardware-testing/)

## What to ask each vendor

1. Is the named SDK/runtime/device interface permitted for this use case and commercial model?
2. Which version, platforms, regions, and telemetry fields are supported?
3. Are attribution, rate limits, user consent, data retention, or security requirements imposed?
4. Are there prohibited integrations, anti-cheat constraints, or certification steps?
5. Who can provide a dated written approval, license grant, or official documentation link?

## Approval record format

Do not mark an item approved from a sales conversation or an undocumented verbal response. Attach the vendor’s written response, reviewer/entity, exact version, conditions, date, and renewal/expiry terms. Keep the register status `pending-vendor-review` until that record exists.

## Outreach boundary

This packet is ready for owner-reviewed outreach. No messages, forms, accounts, or vendor submissions have been created or sent. Pilot invitations and provider activation remain deferred.