GHOSTphoneALPHA 0.7BY CPX / CHYPHNXYour GHOST number.
Call over Wi-Fi.
Free GHOST network calling, Lite encrypted test messaging, and three separately named identities for your Samsung and Moto. Bring any SIM/eSIM—our browser calls use internet data, not your carrier dialer. This is a lab, not a public telephone service.
Choose your GHOST identity
Switching identities disconnects the current call and chat. GHOST IDs and pairing secrets are distinct in the browser, but production isolation requires separate backend identities and verified cryptographic keys.
Release gate: Complete the two-device acceptance test before buying a number, changing SIMs, or claiming carrier/encryption certification. The test is independent of the paid voice gateway.
Your GHOST ONE test number
Saved in this browser, not reserved with a telephone carrier.
Each browser/device must have its own number. Changing or clearing browser storage can lose yours. These are temporary experimental IDs.
GHOST dialer
First share the same pairing code between the phones in person. Then enter the other phone's GHOST test ID below.
Create the code on the Samsung and enter it on the Moto. Do not include the secret in invites, URLs or screenshots.
Open on two devices to begin.
GHOSTmessenger LITE LAB
Message bodies use AES-GCM end-to-end encryption with your shared 128-bit pairing code. Both pages must be online; no server message history.
Security: waiting for verified pairing code
Use your existing SIM or eSIM
GHOST Wi-Fi calls use the browser's internet connection—even if your phone has an active SIM or eSIM. This button only launches your device's regular phone dialer; carrier calls are billed and governed by your carrier and are not GHOST encrypted calls.
Encrypted call transport diagnostics
During a live paired call, check whether the browser reports a connected DTLS transport and audio packets flowing. This is a standards-aligned transport diagnostic, not proof of verified E2EE identity. Do not use sensitive conversations in this alpha.
No media audit run. Place a call on Samsung and Moto first.
No IP addresses, SDP offers, ICE credentials, microphone samples or device/SIM identifiers are included in the exported audit. Future work: bind WebRTC media fingerprints to verified account keys.
Device & connection checks
No IMEI, ICCID, SIM data, GPS or contacts are collected. Checks run locally in your browser. Save the report to document testing.
Device checks run automatically. No permissions requested until you make a call.
Alpha / Beta Crypto verification
Assign this installation to Samsung A or Moto B. Run deterministic pass/fail checks using audited browser Web Crypto primitives. The tool never asks for IMEI, ICCID, phone number, passwords or SIM access, and reports contain no cryptographic secrets.
A browser cannot reliably prove that traffic uses Wi-Fi instead of cellular. This confirmation is recorded only in a downloaded local report.
Covers AES-GCM decrypt, tamper, wrong-key and wrong-associated-data rejection, IV freshness, replay prevention in the test harness, and HKDF identity separation. These are local unit tests, not proof of a secure protocol or verified WebRTC media identity.
Alpha limitations: This uses public PeerJS signaling, WebRTC transport and public STUN. Both phones need internet through Wi-Fi; calls may fail on restrictive networks without a TURN relay. Keep Chrome and this page in the foreground with both screens awake. The paired code authenticates the data channel for this lab only; it does not bind the separate media-call fingerprint. WebRTC voice transport is encrypted (DTLS-SRTP), but full authenticated E2EE calling is NOT verified. No background ringing, guaranteed delivery, real PSTN/SMS, or 911. Not audited or suitable for sensitive communications or emergencies.