Veyra Privacy Policy

This policy covers the Veyra messenger app (Windows, macOS, Linux, Android, iOS) and the veyra.social website.

The short version

• No accounts on our servers. Your profile is a cryptographic key pair generated on your device. We have no user database.
• The app collects nothing. No analytics, no ads, no trackers, no telemetry, no crash reporting anywhere in the app.
• End-to-end encryption everywhere. Messages, calls, and file transfers are end-to-end encrypted. Our infrastructure cannot read them.
• Your data lives on your devices. Deleting your profile deletes your data. There is nothing to delete on our side, because we never had it.

1. Who we are

Veyra is a peer-to-peer, end-to-end encrypted messenger. There is no central message server: your messages are stored only on your devices and travel either directly between devices or through relay nodes that see only encrypted data. Questions: privacy@veyra.social.

2. What we do not collect

The app has no registration. We do not ask for — and cannot see — your phone number, email address, name, or contact list. The app contains no third-party analytics, advertising, or tracking components, and it sends no telemetry or crash reports.

3. Your profile and data on your device

• Creating a profile generates encryption keys locally. Your identity in the network is a public key; the private key never leaves your device.
• Messages, contacts, attachments, and settings are stored only on your device. Message texts, file names, and file keys are stored encrypted with keys derived from your profile password. We cannot recover them: if you lose the password and have no backup, the data is gone — by design.
• Backups are created only when you ask for one, are encrypted with a password you choose, and are stored wherever you put them. We never receive them.
• You can delete a profile inside the app; this removes its keys and data from the device. Uninstalling the app removes all local data.

4. What other people see

• Contacts you have added see the profile name and photo you chose, your public network ID, and — obviously — the messages you send them.
• On a direct peer-to-peer connection (same network, or a punched-through Internet path), your device's IP address is visible to your contact's device, as with any direct connection. When traffic goes through a relay, the contact sees the relay instead.

5. Relay nodes (infrastructure)

To find each other behind firewalls and NATs, devices connect to bootstrap nodes — run by us or by third parties using the open-source node software. Nodes:

• see ordinary connection data: your IP address, your public network ID, and connection timestamps;
• relay only end-to-end encrypted envelopes and cannot decrypt them — the keys exist only on user devices;
• may hold an encrypted envelope for an offline recipient for a limited time (store-and-forward). What is stored: the encrypted envelope, sender and recipient network IDs, size, and timestamps. Envelopes are deleted after delivery or when their time-to-live expires;
• may relay a call (TURN) when no direct path works; relayed call media stays end-to-end encrypted, and the relay sees only IP addresses and encrypted packets.

Nodes keep no message archives, no contact graphs, and no profile data. Short-lived technical logs used to keep the service healthy may contain IP addresses; they are not used to identify or profile users.

6. Calls

Calls are peer-to-peer and end-to-end encrypted. To discover a connection path, the app may contact a public STUN server (currently Google's stun.l.google.com); a STUN server learns your IP address — that is the only thing STUN does. If no direct path exists, the call is relayed through our nodes (see section 5).

7. Local network

On your local network the app announces itself (mDNS/Bonjour) so that your own and your contacts' devices can find each other and transfer data directly. This is why iOS asks for the Local Network permission. Nothing about this leaves your network.

8. Update check

The app can periodically (at most about once every three days) fetch a small version file from veyra.social to tell you when a new version is available. The request carries only the app version and operating system type — no identifiers. Like any web request, it reveals your IP address to our web server. You can switch the automatic check off in the About dialog. Nothing is ever downloaded or installed automatically.

9. Notifications

Notifications are generated locally on your device while the app is running. The app currently uses no push services (no Google FCM, no Apple APNs), so no notification data is shared with anyone.

10. Website

veyra.social serves pages and release downloads. Standard web-server access logs (IP address, requested URL, time, browser signature) are used for security and operations.

If you subscribe to release news or early builds, we store your email address, selected mailing list, and language until you unsubscribe or an administrator deletes the subscription. Every mailing must include a personal unsubscribe link. After unsubscribing, the address is retained only on a suppression list so it cannot be added to future mailings again unless the exclusion is explicitly removed.

We keep first-party aggregate visit statistics: date, country code, operating system, browser, device type, and visit counts. To count a daily visitor without an analytics cookie, the IP address and browser signature are converted into a one-way daily hash. The raw IP address is not stored in the statistics tables, and the daily hash is not designed to link visits across different days.

The site sets a language-preference cookie. News pages may also use a random reader token to count reads and reactions; it contains no identity and is not used to follow you across other websites. The site uses no third-party analytics trackers and shows no advertising.

11. Children

Veyra is not directed at children under 13 (or the higher minimum age of your jurisdiction). The app does not request or collect a user's age or other account data. The limited technical data created by use of the website and relay infrastructure is handled as described in this policy.

12. Your rights

We hold no server-side account, profile, message history, contact list, or file archive about you. Access, correction, or deletion of that data is under your direct control on your own device. Transient relay data (IP addresses, encrypted envelopes) expires automatically.

Website and infrastructure records may contain limited technical data as described above. If you have a question about that data, want to exercise a right available in your jurisdiction, or believe this policy is inaccurate, write to privacy@veyra.social. We may need enough information to locate a record, and in some cases we may not be able to connect an aggregate or one-way-hashed record to you.

13. Changes to this policy

We will post any changes on this page with a new effective date. The app never accepts remote configuration; a policy change never changes what the software does silently.