FAQs | STIX

Home

FAQs

Why Stix Doesn't Support Phone Calls?

Stix prioritizes secure and reliable communication, which is why phone calls are not supported.
Calls over the Tor network—integral to Stix's privacy and anonymity — are technically challenging and impractical due to several inherent limitations.
Here's why:

High Latency

The Tor network routes traffic through multiple nodes (entry, middle, and exit), adding significant latency to maintain anonymity. Real-time communication, such as voice and video calls, requires low-latency connections to ensure seamless interaction. Tor’s high latency makes this impractical, leading to delays and interruptions.

Packet Loss and Unstable Connections

Tor relays are operated by volunteers with varying quality. Packet loss and unstable connections are common, causing dropped or distorted audio in real-time communication. VoIP protocols, which are highly sensitive to these issues, cannot function reliably under such conditions.

Bandwidth Limitations

Tor prioritizes anonymity over speed, and many of its nodes have limited bandwidth. Real-time calls require consistent, high-bandwidth connections to maintain quality, which Tor cannot guarantee.

Protocol Limitations

Most real-time communication relies on UDP (User Datagram Protocol) for its speed and efficiency. Tor, however, primarily uses TCP (Transmission Control Protocol), which is more reliable but unsuitable for the demands of voice or video calls. Experimental implementations of UDP over Tor exist but are not stable or widely supported.

NAT and Firewall Traversal

Voice calls often require NAT (Network Address Translation) traversal to establish direct peer-to-peer connections. Tor’s design, which conceals real IP addresses, makes NAT traversal nearly impossible. Furthermore, Tor exit nodes cannot support direct inbound connections, further complicating peer-to-peer communication.

End-to-End Encryption Challenges

While Tor provides anonymity, ensuring end-to-end encryption for calls adds another layer of complexity. Without robust encryption, there is a risk of eavesdropping, particularly at Tor’s exit nodes. Real-time encryption protocols, such as those in WebRTC, may not function securely within Tor’s infrastructure

Why Stix is Not Available on iOS?

The iOS platform poses significant challenges for Tor-based messaging apps like Stix due to restrictions in Apple’s ecosystem and technical requirements specific to the Tor network. Here's why implementing Stix on iOS is impractical:

Lack of Background Process Support

iOS enforces strict limits on background processes to conserve battery life and improve system performance. However, Tor requires a continuously running client to maintain its connection. Without persistent background support, the Tor connection drops, making reliable messaging impossible.

Connection Persistence Issues

Tor-based messaging relies on onion services that need stable, continuous connections. iOS often suspends app network activity when an app is minimized or the device enters sleep mode. This disrupts the Tor connection, rendering real-time and asynchronous messaging unreliable.

Custom Networking Protocol Restrictions

Tor's functionality depends on low-level control over network sockets to route traffic through its relays. On iOS, apps are restricted to high-level APIs, such as URLSession, which are incompatible with Tor’s custom networking protocols.

App Store Policy Constraints

Apple’s App Store policies create additional barriers:

- Tor-based apps often use custom interpreters or undisclosed configurations, which Apple prohibits.
- Apple emphasizes user safety and compliance with local laws, potentially rejecting apps that prioritize anonymity in ways deemed non-compliant.
- These restrictions make it difficult to secure approval for Tor-based apps like Stix.

No System-Level VPN Integration for Tor

Tor often requires VPN-style tunneling to route all traffic through its network. iOS, however, does not permit third-party apps to create true system-wide VPN tunnels without special entitlements. Apple’s built-in VPN frameworks are incompatible with Tor’s custom routing needs, limiting the app’s ability to establish secure connections.

Resource Constraints

Tor encrypts and routes traffic through multiple relays, which demands significant computational power. iOS prioritizes efficiency and user experience, making resource-intensive processes like Tor challenging to implement without impacting app performance.

Closed System Architecture

Unlike Android, which allows sideloading apps and modifying system configurations, iOS is a closed system. Users cannot install system-level Tor clients or modify network settings without jailbreaking their devices. Jailbreaking not only voids warranties but also introduces security risks, making it an impractical solution for most users.

Onion Service Challenges

Stix relies on Tor onion services for peer-to-peer communication. Onion services are complex and sensitive to disruptions, which are common on mobile devices. Furthermore, Apple’s push notification system is incompatible with onion services, preventing real-time message alerts.

Focused on What Works Best

While iOS limitations prevent Stix from being available on the platform, Stix remains committed to providing secure and anonymous communication on systems where Tor can function optimally. By leveraging the flexibility of Android and open ecosystems, Stix ensures the highest levels of privacy and performance for its users.

Why Stix is paid?

In a world full of "free" messengers, Stix stands apart by prioritizing your privacy and security above all else. Unlike many free services that rely on invasive data practices or hidden funding mechanisms, Stix is designed to be truly independent and transparent.
Here’s why Stix is paid:

True Privacy Comes at a Cost

Many free messaging apps fund their operations by selling user data, targeting you with ads, or partnering with external entities. Stix does none of this. By charging a fair price, we ensure that your data remains yours and that you are never the product.

Independence from External Influence

Stix operates without external funding, advertisers, or corporate sponsors. This independence ensures that we remain accountable only to our users—not to shareholders, advertisers, or other third parties.

No Hidden Costs or Dependencies

“Free” apps often come with hidden costs: selling your data, compromising your privacy, or displaying ads. Stix is upfront and transparent about its pricing, allowing us to fund the system ethically without compromising your security.

Supporting Secure Technology

Building a secure, decentralized messaging system like Stix requires significant resources. From maintaining infrastructure to ensuring ongoing security updates and improvements, your support allows us to continue providing cutting-edge technology that prioritizes your privacy.

A Commitment to Quality

By choosing to pay for Stix, you’re contributing to the development of a high-quality app with no compromises. This includes military-grade encryption, offline functionality, and regular updates—all designed to keep your communications secure and your experience seamless.

Empowering Ethical Innovation

Your support fuels innovation. Instead of relying on data harvesting or external investments, we use the revenue from Stix to develop new features and ensure our app remains secure and effective for all users.

Invest in Your Privacy

Choosing Stix means investing in a platform that values your privacy and independence. By paying for Stix, you’re directly supporting a secure, ethical, and trustworthy messaging solution built for people who refuse to compromise on privacy.