Aether Reel

Aether Reel GmbH

Trust Center · published May 23, 2026

Compliance posture for Aether Reel.

Aether Reeloperates under the regulatory frameworks listed below. NexionLabs provides the credential verification infrastructure; it does not make compliance determinations on behalf of the partner. The posture indicators on this page reflect automated control assessments run by the NexionLabs platform. They are not legal advice and do not constitute a certification of the partner's compliance status. This statement is a draft pending review by qualified legal counsel.

Status at a glance

Updated continuously from the NexionLabs platform substrate.

Compliant

ARCOM

France

Last checked 2 days ago

Drift detected

Ofcom OSA

Last checked 2 days ago

Compliant

US-state AV

United States

Last checked 2 days ago

Trust anchor freshness

Cryptographic proof that the platform substrate is currently operational.

DIIP root

Fresh

block 21,840,402

Last published May 23, 2026

DIIP Root → R12 → R8 → leaf

fingerprint: sha256:4f3a…d12c

EU AV anchor

Stale

—

Last published Apr 11, 2026

EU AV anchor publication suspended pending EUDI ARF v1.5 schema ratification. Expected Q3 2026.

Conformance status

Standards-body conformance posture.

Regime	Status	Evidence	Target
HAIP	Certified	View evidence &nearr;	—
FAPI 2.0	Certified	View evidence &nearr;	—
DIF	In progress	—	2026-Q3
OIDC	Certified	View evidence &nearr;	—
EUDI ARF	In progress	—	2026-Q4

Regulatory watchlist

Events matched to this organization's regulator exposure.

2026-05-23

ARCOM published guidance update 2026-05. No impact on current workflows.

2026-05-21

Control OSA-7.3 (age-assurance proportionality review) flagged for attention.

2026-05-19

US-state AV evidence pack regenerated for quarterly report.

2026-05-17

KJM published new operator FAQ. Review for DE workflow impact.

2026-05-15

ARCOM 2024-31 evidence pack regenerated. All controls passing.

Audit evidence export

Request a downloadable artifact for external auditors and counsel.

Audit packs include conformance evidence, control-mapping matrices, and the platform attestation chain. Available formats: OCSF NDJSON (preferred for SIEM ingestion), signed PDF (preferred for regulator filings), JSON (machine-readable).

Rate-limited. Result is emailed to a verified address.

Certificate rotation state

For technical auditors.

Verifier binding certificate

sha256:6f2c…b41a

Rotates 2026-08-12

Webhook signing key

sha256:3d11…02ef

Rotates 2026-07-04

mTLS client certificate

sha256:e22f…915c

Rotates 2026-09-30

Statements of practice

What NexionLabs verifies on behalf of this organization, and what it does not.

1. Verification methodology

NexionLabs verifies credential presentations using the OID4VP 1.0 protocol against issuer-signed credentials. The verification does not access, store, or process the underlying identity document. Pass/Fail decisions are derived from cryptographic proof validation, not from identity matching or biometric comparison at the gateway layer. This statement is a draft pending review by qualified legal counsel.

2. Data handling

Verification session metadata (timestamps, outcome, policy receipt hash) is retained per the partner's configured retention policy. Raw identity attributes presented during verification are not stored by NexionLabs and are not accessible to NexionLabs personnel. The partner receives only the attributes permitted by their workflow configuration. This statement is a draft pending review by qualified legal counsel.

3. Audit trail

Each verification produces a signed Activity Receipt anchored to a hash-chain. The receipt can be independently verified by any party holding the receipt ID and the partner's public verification key. This audit trail is designed to satisfy GDPR Art. 5(2) accountability requirements and regulator evidence expectations under ARCOM, Ofcom OSA, and equivalent frameworks. This statement is a draft pending review by qualified legal counsel.