MIT license · Judge guide · Submission assets
A private phrase. A trusted response.
Need help to alert your people in difficult cases? SignalWord helps you reach the people you trust when unlocking your phone or navigating an app may not be practical. Trigger a discreet alert with Apple Vocal Shortcuts, notify up to three trusted contacts, share an optional location snapshot, use safety check-ins, and see exactly what has been sent, delivered, acknowledged and resolved.
It is not an emergency-dispatch service, does not run an app-owned always-on microphone, does not receive the private phrase or ambient audio, and must not claim delivery or live location without evidence.
| Understand and set up | Supporter appearance |
|---|---|
![]() |
![]() |
Setup and privacy guidance, alongside optional appearance customization. The setup image is an owner-provided preview prepared at 1179×2556; the supporter image retains its original dimensions. View and download the submission assets.
- Product: private alerts and server-managed check-ins for consenting trusted contacts.
- Platform: native SwiftUI iPhone app; recipients use an email link and browser.
- RevenueCat: one optional non-consumable purchase,
com.signalword.supporter.appearance, unlocks both Ocean and Lavender accents and a supporter card. Purchase, restoration and entitlement refresh are separate from safety actions. - Evaluation: follow the reproducible setup and TEST walkthrough. Use synthetic contacts and an inbox you control.
- Website: signalword.app. A homepage is not a substitute for the native app demo.
- Availability: Apple review is pending. Next Gen eligibility requires a public licensed repository and an accessible demo video; other award eligibility depends on the official store requirements or written organizer permission.
apps/
ios/ SwiftUI iOS app and XCTest suite
viewer/ React/Vite contact viewer
supabase/
migrations/ Postgres schema and RLS migrations
functions/ Edge Functions implementing the alert API
tests/ database and authorization tests
scripts/ dependency-free repository checks
tests/ fast repository automation tests
Version 1.0 (8) and the optional SignalWord Supporter Appearance purchase were submitted together to Apple on 1 October 2026 at 04:16 Sydney time. After Apple requested additional information under Guideline 2.1, the same Build 8 was resubmitted on 2 October 2026 at 01:33 Sydney time. Owner-provided screenshots captured at 02:04–02:06 show both items Waiting for Review. This is submission evidence, not Apple approval or a public App Store release. See the selected Apple review evidence.
The app is configured for free download. All safety features remain free; one non-consumable Supporter purchase unlocks both Ocean and Lavender accent colours. RevenueCat manages the optional purchase and restoration.
The submitted native binary is unchanged by this repository preparation. Later repository updates may improve the website and documentation without changing the binary Apple is reviewing. Release evidence and operational gates are retained privately by the maintainer.
The recovery/acknowledgement slice is implemented. Passing local tests does not mean release-ready; production evidence is maintained privately.
SMS is not part of this release.
- Complete the applicable private release checklist with the maintainer before deploying.
- Install Node.js 22, run
npm ci, thennpm run verify. - Copy
.env.exampleto.envonly for local development; never commit real credentials. - Configure Xcode and the local environment as described in the iOS README. The build validates the backend URL, public key and intended project before producing an app.
- Run the relevant browser, Swift and database checks documented in the component READMEs. Use controlled contacts for delivery testing; do not send unsolicited real alerts.
GitHub Actions runs the fast repository verification on every push and pull request. It also performs a full-history secret scan. Before public release, additional physical-device, RLS, delivery, and viewer tests are mandatory.
Only development/test and production are supported. Use the component READMEs and .env.example when configuring tools; never commit real secrets.
Internal planning, rules and release documents in docs/ are private local files and are excluded from Git. Public setup documentation remains in this README and the component READMEs. Safety claims require supporting evidence recorded in the private claims ledger.

