Privacy Policy
Whispyr is designed around proximity-first communication and a local-first data model. This policy explains what we collect, what we don’t, and how the architecture reduces unnecessary data gravity.
1. The short idea
Whispyr aims to minimize centralized data collection. Where the product supports local-first behavior, your identity and conversations are stored on your device, not in a global message warehouse.
2. Data you provide
You may provide profile information you choose to share in the app. If you contact us for support, we will receive the information you include in your message.
3. Local-first storage
Whispyr may store identity, chats, spaces, stories, and events on-device by default. This architecture is designed to reduce reliance on centralized infrastructure and keep context grounded in real-world proximity.
4. Backups and exports
If the app offers export or backup options, those actions are initiated by you. You are responsible for storing exported files securely and protecting any passphrases you choose to use.
5. Technical data (website)
When you visit our website, we may collect basic technical information such as browser type, device information, and approximate usage analytics to keep the site stable and secure.
6. What we don’t aim to do
Whispyr is not built as a data-harvesting platform. We do not aim to create a centralized directory of your relationships or store your private conversations in a global inbox.
7. Security overview
Whispyr uses modern cryptographic primitives appropriate for peer sessions. For details on the high-level approach, see our Security & Cryptography page.
8. Your rights
Depending on your location, you may have rights to access, correct, or delete personal information we hold in connection with support or website interactions.
9. Contact
If you have privacy questions or requests, contact support@getwhispyr.app.
Short version
Whispyr is designed to keep conversations close to the device and the moment. We collect only what we need for the website and support, and we avoid building a central message warehouse.