Short questions. Clear answers.

A messenger concept for private messages, files, and calls over Tor. Content is encrypted on the end devices. The planned launch is in November 2026.

No. Your personal ID is generated on your device. Contacts start with a deliberately shared QR or link invitation. Your device address book is not read.

The private content keys remain on your end devices. Nodes receive encrypted delivery copies. A compromised, unlocked device and deliberately shared content remain boundaries of protection.

Messages and attachments from the app's local storage, starting at sending or first receipt respectively. Contacts remain. This cannot recall screenshots, exports or copies held by others.

HeyAppPro suspends its transmission. Still valid messages wait encrypted, and calls are interrupted. There is no silent direct backup path. Other apps on your device are not affected.

No. It is a voluntary infrastructure contribution. Suitable Pi, Linux, or Docker devices can provide encrypted delivery copies. They are not general Tor exit nodes.

The Free License: After the first proven 24-hour qualification, you receive full licenses free of charge depending on the level – Private 1, Business 3, Business Pro 5, and Gov 5 – as long as your node runs 24/7. For each renewal, it is checked whether the node was continuously operational and remains so. You are responsible for the one-time app purchase of CHF 10.00 and the hardware, electricity, and internet for the node.

The app costs a one-off CHF 10.00 in the App Store or Google Play, once per user thanks to Family Sharing. A licence is added: Private CHF 3.50 per month or CHF 35.– per year, Business CHF 5.– and Business Pro CHF 9.– per user per month, Gov as a licence bundle from CHF 12.– per licence per month. Authorities allocate and manage licences internally and operate HeyAppPro completely autonomously on their own infrastructure. These are planned prices; the offer at launch is binding.

Yes. If a new customer registers with an existing customer's referral code, both receive 6 months of additional service. This applies to Private, Business, and Business Pro, but not to Gov. You can find your personal referral code in the app.

On macOS, Linux, and Windows, you use HeyAppPro via web access with a local Core. There are also apps for iOS and Android. Authorized devices have their own keys. The user concept includes nine languages as well as light and dark mode. Developed in Rust.

Yes, in development. Planned capacities are up to 50 people per group with Private, 100 with Business, 256 with Business Pro, and 500 with Gov. Groups are formed from your contacts; only those who accept the invitation can join. Admins can add or remove members. Those who are removed will no longer receive new keys. There are no public groups or join links without acceptance, nor a central group server.

Yes, in development. You send your location once or share it live for 1, 2, 3, 4, 5, or 12 hours, updated every approx. 15 seconds. All sharing users appear on a shared map, usable as usual: pan, zoom, "My Location", "Show All". You can switch between street map (OpenStreetMap) and aerial view (swisstopo). The map tiles are sourced exclusively via Tor from a dedicated map service; it sees which sections are retrieved, but not who is retrieving them. Radar and list remain as alternatives. On request, only approximate (≈ 1 km). Live locations are deleted after the session ends. On iPhone, a live location updates only as long as HeyAppPro is open.

Yes, in development. In the chat, you hold the push-to-talk button, speak, and release. The other person's device rings first; after "Accept", further announcements from this contact play directly until the call is ended. "Decline" discards pending announcements. The announcement plays in short, individually encrypted segments over Tor and is only played, not saved in the chat history. Over Tor, this is not real-time radio: expect a few seconds of delay. Group radio will follow group chats.

Yes, in development. A phone icon sits next to the walkie-talkie control in the chat: it rings, your contact accepts or declines, then you speak simultaneously. Calls are end-to-end encrypted, run exclusively over Tor and are not recorded. Each direction takes a few seconds over Tor, so it feels more like an intercom than a usual phone call. Headphones prevent echo. For now, it does not ring when the device is locked or the app is closed. Video and group calls will follow.

Crisis communication helps here: HeyAppPro provides the PlugIn infrastructure; the transmission paths are third-party solutions. PlugIns can connect LoRa mesh with Meshtastic, amateur radio networks such as HAMNET, AREDN, Winlink and APRS, and digital and trunked radio such as DMR and TETRA. In a disaster, amateur radio operators or authorities' technical services can quickly enable alternative paths. Text messages and locations continue over them, with more possible on faster radio networks. You use the same app, contacts and history and choose the fallback path for each contact. Each message shows which channel it uses.

In case of disaster, amateur radio operators, technical services of the authorities, or organizations with their own operational radio activate the alternative communication paths. They operate the radio equipment, nodes, and gateways and install the appropriate third-party PlugIn, for example for Meshtastic, Winlink, or DMR. HeyAppPro provides the PlugIn infrastructure: In the app, you select the alternative route for each contact and continue writing as usual. This keeps families, clubs, municipalities, and emergency organizations connected even without the internet.

Your LLM agents can work on common tasks with colleagues and a colleague's colleague via MCP. You explicitly authorize the involved contacts, functions, and content. Access is off by default. Read rights authorize plain text; external AI requires additional conscious authorization.

Yes, in development. A HeyAppPro node on a Pi, Linux computer, or Docker host can serve as a network gateway. IT systems at two locations can then reach each other via TCP/IP, but only with authorized services, ports, and subnets. «Private via Tor» connects individual TCP services via authenticated Onion gateways. «Network via NetBird» connects locations with TCP, UDP, and IP routing over encrypted WireGuard connections. Each authorization uses exactly one path, and the counterparty confirms the access itself. Chats, attachments, and mailboxes remain separate and run exclusively over Tor.

There is no central server infrastructure: communication takes place exclusively between participants over community hardware. Only the manufacturer's licence server for licences and node authorisations, and the map tile service, are central; neither transports messages. Complete anonymity is not guaranteed: devices, conversation content and traffic patterns can reveal information.