# Aktuelle Store-Verfügbarkeit · 19. November 2026

HORST Secret Chat ist öffentlich und kostenlos im [App Store für iPhone und iPad](https://apps.apple.com/de/app/horst-secret-chat/id6827768757) (ab iOS/iPadOS 15.0) sowie bei [Google Play für Android](https://play.google.com/store/apps/details?id=de.smfuture.smchat) verfügbar. Der bestätigte Apple-Stand ist Version 0.6.13.

Der folgende technische Übergabestand vom 28. Oktober 2026 ist historisch. Seine damaligen Angaben zu TestFlight und noch ausstehenden Store-Veröffentlichungen beschreiben nicht mehr die heutige Verfügbarkeit. Eine unabhängige Sicherheitsprüfung wird durch die Store-Freigabe nicht bestätigt.

---

# HORST Secret Chat — authoritative continuation, Teil 2

Checkpoint 28 October 2026, 20:34 UTC (21:34 Europe/Berlin).
Current implementation: **0.6.7 / Android and iOS build 15**.
Runtime code commit: 594903f37c90ffcb1108e9ec0bd1e93bcc8116c1.
Subsequent checkpoint changes are documentation/evidence only.

## Delivered correction

Changing a group's maximum lifetime could be lost behind an in-flight state
refresh. Forced refreshes are now queued and awaited. The picker and signed
outgoing message use the same normalized lifetime; switching from permanent
to finite groups no longer reuses an invalid permanent draft choice.
Existing signed expiry and draft text are retained. See GROUP-EXPIRY-B15.md.

The regression fails against build14 at the new seven-day maximum and passes
for iOS, Android and Web UI adapters against build15. It tests owner/member
updates, increases, reductions, permanent/finite switches and sent expiry.
All 90 unit tests and six further browser checks pass: direct retention, iOS
voice, recovery export, foreground feedback, peer history and registration.
These are isolated browser/relay tests, not physical device acceptance.

## Current distribution

- Web, HTTPS and own Onion run 0.6.7. All 11 deployed Web assets match the
  build; main HORST health is 200. Server code/dependencies, persistent data,
  push configuration and account identities were preserved.
- Android release APK, AAB and account-compatible test-device APK are built,
  signature/ZIP/assets/16-KiB alignment checked. No phone installation occurred.
- iOS IPA is signed, deep signature verified and uploaded once. It reuses
  unchanged native build13 code/frameworks with new resources, version/build
  metadata and signatures; no new native compilation. Temporary credentials
  were removed. Apple build ID 93d6c939-813e-481f-a29c-bbe253e7aeff is VALID.
- TestFlight build15 is IN_BETA_TESTING for the verified existing owner.
  Individual assignment was rejected by Apple (409); T2 therefore created
  internal group "HORST Secret Chat - Martin Abnahme", ID
  6dc9c1af-1ae5-47f4-b697-1910d623e333, with exactly that owner and build15.
  It has no public link and no automatic access to every build.
- iOS scope remains TestFlight, not public App Store release. Android Google
  Play production preparation/declarations/upload remains unfinished.

## Concurrent Apple changes: preserve current state

The final read at 20:32 UTC also observed build15 in the original two-person
internal group and in "Alle anderen"; external review WAITING_FOR_REVIEW,
submitted 20:31:33 UTC. Builds13 and14 were EXPIRED. These actions were NOT
performed by this T2 workflow; the actor is not established. Do not undo them,
resubmit review or infer they came from the stopped owner. The external group
currently reports zero testers and its public link remains enabled.
The new owner-only group is still present with one tester. Do not create it again.
Authoritative final read: docs/evidence/HORST_CHAT_T2_FINAL_ASC.json.

## Verified takeover and corrections

120 executable/build/test source files matched the build PC and 44 matched the
active build14 server/public ZIP. Four build14 packages matched recorded hashes
and embedded assets. A fresh Web rebuild matched all 11 live assets. The old
owner explicitly handed over at 19:54:59 UTC, no active phone reservation,
automation disabled, source checkpoint af041f301b0a364b20ea8825bf5db09ef13b038a.
Build14 upload was not repeated. Old APNs keys were not recreated.

The old Android release receipt contains unconditional success prose despite
empty results and "ADB action failed". The old-owner handoff confirms no update.
Do not reuse that prose or alter the historical coordination receipt.

T2 coordinator attempts fail with Windows error5 at atomic state replacement.
Last check20:33 UTC: revision57, phase free, active null, queue empty. No T2
reservation or phone commands occurred. Only T2's failed temp files were removed.
Use the sole coordinator on rabbi_pc before any ADB access. Never bypass it,
overwrite state, clear app data or replace a debug-signed install with release.

## Push and security limits

The early02:00 UTC release hold was followed by APNs setup and recorded user
acceptance before the18:15 checkpoint in IOS-CONTINUATION.md. Driver-app status
must not be substituted for Secret Chat. No fresh instrumented iPhone push
delivery is claimed here; physical voice/push/update acceptance remains pending.

The PIN throttle can be reset by an attacker already controlling app-origin
storage. iOS lacks a dedicated rotating native Vault key; its browser Vault is
still PIN-encrypted. Both findings remain open. This group-expiry correction is
not an independent security audit or a native-vault redesign.
See PRE-AUDIT-2026-10-28.md and the retained historical evidence.

## Paths and next safe actions

- Source: /workspace/scratch/59242dd16830/secret-chat-verify
- Build source: C:/SMFutureBuild/projects/horst-secret-chat-067
- Packages/receipts: C:/SMFutureBuild/downloads/HORST-Secret-Chat-0.6.7-build15*
  and HORST_CHAT_B15_*; Apple receipts on D:/AblagePrivat/Downloads/HORST_CHAT_T2_*.
- Mac: /Users/m1/horst-secret-chat-b15-20261028; no new rental/extension authorized.
- Server: /opt/horst-secret-chat/releases/0.6.7; read live state before changes.
- Coordinator: rabbi_pc, D:/AblagePrivat/Downloads/SMFUTURE_XIAOMI_COORDINATION.

Next: TestFlight15 physical acceptance; resolve coordinator write access without
bypassing reservations, then matching-signer install-r and Android acceptance;
follow existing external review without duplicate submission; production store
preparation and separate security hardening. Never archive credentials.
