Speakapp is a secure, privacy-focused messaging application built for the Web3 era. It uses Ethereum Virtual Machine (EVM) addresses for user identification instead of phone numbers, emails, or traditional login credentials.
No personal information, phone numbers, or passwords are required to create or use a Speakapp account. All messages are end-to-end encrypted before they reach our servers.
Privacy, freedom, and ownership are core principles that shape how we design and operate our Services.
Our Commitment to Data Protection
Speakapp is designed with a strict privacy-by-design approach. We aim to collect as little information as possible and avoid any data that could be used to build a long-term profile about you.
Your primary identifier in Speakapp is your EVM-compatible address or cryptographic key pair. We do not ask you to link your real-world identity (such as your name, phone number, or email address) to this identifier.
What We Collect (and What We Don't)
By default, we do not collect or store information such as your real name, phone number, email address, or government-issued identifiers. You can use Speakapp without providing such data.
We do not use third-party analytics or tracking cookies to monitor your behavior across apps or websites. We do not log your location history, build advertising profiles, or sell any data to third parties.
However, as with any internet-based service, certain limited technical information (such as IP address or basic connection metadata) may be processed transiently for the purpose of routing traffic, delivering messages, preventing abuse, or maintaining service reliability. Where possible, we minimise, aggregate, or discard such information rather than storing it long term.
Your messages and interactions are designed to remain private. Our infrastructure follows strict privacy-by-design principles to ensure that what is yours stays yours.
Encryption & Security
Speakapp implements end-to-end encryption (E2EE) using the Signal Protocol – the same class of cryptographic protocol used by modern privacy-focused messengers.
All encryption and decryption happen exclusively on client devices. The server operates under a zero-knowledge architecture: it stores and relays only opaque ciphertext and public key material, never plaintext message content.
- Messages are encrypted on your device before transmission and can only be decrypted by intended recipients.
- No readable (plaintext) message content is stored on our servers.
- No Speakapp team member or third party can access your unencrypted messages by design.
- Multi-layer encryption can control access at user, group, and admin levels.
- Data remains encrypted in transit and at rest, and is only decrypted on your own device.
While we use advanced and widely reviewed cryptographic protocols, no system can guarantee protection against all future threats, vulnerabilities, or decryption techniques. Security is an ongoing effort, and we continuously work to improve it.
Abuse Reporting and Encrypted Proof
Reporting Abuse
Speakapp provides a feature to report abuse or violations of our Terms, especially in public Communities or shared content visible to others. When you report abuse, we may collect limited metadata such as group or channel identifiers, timestamps, and the type of violation reported. We do not access the decrypted content of private messages as part of this process.
Reports are reviewed in accordance with our governance policies. We aim to balance strong privacy with the need to keep public spaces as safe and respectful as possible.
Signed Message Reporting
In addition to metadata-based reporting, Speakapp supports a privacy-preserving method where users may forward cryptographically signed copies of encrypted messages they have received as evidence of abuse or Terms violations.
- No message content is revealed to Speakapp; we do not decrypt the payload.
- The report contains only the encrypted payload, message ID, sender's public key, and timestamp.
- Our systems verify the cryptographic signature to ensure the authenticity and integrity of the reported message.
This feature strengthens abuse reporting in encrypted environments without compromising user privacy or end-to-end encryption.
Mobile App Store and OS-Level Data
When using Speakapp on iOS or Android, the operating system and app store providers (such as Apple or Google) may collect telemetry data, such as app install and open events, crash logs, and basic device information. This collection is governed by their own policies and applies to many apps, not just Speakapp.
To learn more, please refer to:
Your Responsibility
Because of our end-to-end and zero-knowledge design, Speakapp cannot access or restore your messages, keys, or EVM-based identity. It is your responsibility to securely store your Recovery Phrase, keys, and to manage the security of your device.
If you lose your recovery information or permanently lose access to your device, we cannot help you recover your account or message history.
Transparency and Legal Requests
We may receive legal requests (such as subpoenas or court orders) from authorities. Due to the way Speakapp is built, we generally do not possess decrypted message content or traditional identity data that could be produced in response.
Where we are legally permitted and technically able to do so, we will describe how we handle such requests in a public Transparency Report, which we aim to update periodically. This report may summarise the number and type of requests received and our responses, without exposing individual users.
Policy Updates
We may update this Privacy Policy from time to time to reflect technical, legal, or operational changes. When we make material changes, we will take reasonable steps to inform you (for example, via in-app notices or website updates).
By continuing to use Speakapp after changes become effective, you agree to the current version of this Privacy Policy.
Get in Touch
If you have questions, feedback, or concerns about this Privacy Policy or how Speakapp handles data, you can contact us at [email protected].
Last updated: 27 February 2026