Velixnet Trusted Safe Exchange
The Idea Why Velixnet Trust Notes Account Contact

Plain information about how the VXN closed test handles the data it needs to operate.

This notice applies to the VXN mobile app distributed for closed testing, the Velixnet website, and the limited account and message-delivery data used to operate the service.

Short version

Private keys stay on user devices. Message content is encrypted before upload. The service uses only the account, delivery, timing, permission, and connection data needed to operate the closed test.

Scope

Velixnet is the service brand. VXN is the mobile application distributed for testing. In this policy, “the App” means the VXN mobile app and, where relevant, its connection to the Velixnet service.

This policy covers the public Velixnet website, the VXN app, the contact form on this site, and Velixnet-operated testing services.

Information we collect

When you use the contact form, Velixnet may store the name, email address, optional note, submission time, and a hashed value derived from the connecting IP address for rate limiting and abuse review.

For a closed-test invitation, Velixnet uses the email address supplied for that purpose only. When you create or use a test account, the service processes your Velix ID, password-authentication data, login session state, public keys, encrypted message-envelope routing data, acknowledgement state, timestamps, and other delivery records needed to route encrypted messages.

Device data and permissions

The App may request internet access so it can connect to the Velixnet service, camera access for QR-code scanning, and notification permission for message alerts. These permissions are used only for their stated functions, not for advertising, profiling, or unrelated tracking.

The App is intended to request only permissions that are necessary for its stated functionality.

What remains visible to the server

Velixnet is built around encrypted message content, but the server can still process or store information such as sender and recipient identifiers, queue state, timing, payload size, account records, public keys, session information, and connection details needed to operate the service.

Choose the network path that suits your needs.

Velixnet encrypts message content, but a network provider can still observe connection metadata. A VPN or Tor can reduce exposure of your home or mobile IP address to the service; neither makes a person automatically anonymous.

Direct connection Simple and fast
IP address visible to the service
Your normal home or mobile IP address.
Main benefit
Simple, fast, and requires no additional provider.
Main trade-off
Your network address is directly associated with the connection.
Practical guidance
Use HTTPS and keep the app and device updated.
Reputable VPN Everyday IP separation
IP address visible to the service
The VPN server’s IP address, rather than your normal IP.
Main benefit
Usually fast and practical for everyday IP-address separation.
Main trade-off
You must trust the VPN provider’s practices; a VPN is not the same as anonymity.
Practical guidance
Choose a provider carefully, review its privacy policy, and avoid services that make impossible “total anonymity” claims.
Tor Stronger IP separation
IP address visible to the service
A Tor exit IP rather than your normal home or mobile IP address.
Main benefit
Provides stronger network-level IP separation through a distributed relay network.
Main trade-off
Often slower, may be less reliable, and cannot protect against account identification, unsafe device settings, or traffic-correlation risks.
Practical guidance
Use a well-maintained Tor client and remember that Tor does not hide information you provide through an account or message metadata.

How we use information

Velixnet uses information to run the website, send requested closed-test invitations, respond to contact requests, prevent abuse, operate test accounts, authenticate users, route encrypted message envelopes, maintain service stability, and investigate technical problems during development and testing.

Velixnet does not sell user data to advertisers or data brokers.

Sharing

Velixnet uses a Swedish hosting provider for the service. Firebase Cloud Messaging is used solely for generic push notifications; it receives push-routing data such as a device registration token and message ID, not VXN message plaintext, encrypted message content, or private keys.

Velixnet may otherwise disclose information only when reasonably necessary to host, secure, maintain, or investigate abuse affecting the service, or when required by law.

The service is not intended as a platform for broad public sharing of user content.

Retention

Closed-test invitation email addresses are deleted within 7 days. Undelivered encrypted message envelopes are retained for up to 30 days. Abuse and aggregate delivery metadata are retained for up to 7 days.

Ordinary account records do not expire automatically. They remain only while the account is active and are removed through the account-deletion process. VXN is not long-term message storage; delivery and account data can be removed according to these rules.

Account and data deletion

You can permanently delete a VXN account in the app: open Settings, choose Delete account, and confirm the deletion. This permanently removes the account from the active VXN service; no website request is required.

Deletion removes the active account record, authentication record, public identity and one-time public prekeys, device delivery token and client-capability record, failed-login record, and undelivered encrypted message envelopes sent by or addressed to that account. As part of deletion, the app removes its local identity and private keys, contacts, local message history, ratchet state, recovery material, and account settings from that device. If device storage prevents completion, the app informs the user.

The active-service deletion routine does not apply an additional retention period to those records and does not create a deletion-specific operator backup. VXN does not currently maintain a per-account recovery deletion ledger or promise automatic reconciliation after a later server restoration.

Standard disaster-recovery backups are a separate operational safeguard and may contain historical encrypted service data until they are purged under their own retention policy. VXN message plaintext and client private keys are not stored on the transport server. If the app reports that local data could not be removed, delete the app's storage or contact privacy@velixnet.com for assistance.

Security

Velixnet aims to use HTTPS, client-side encryption for message content, rate limiting, and restricted server-side storage.

No website, app, or test service can honestly promise perfect security, perfect secrecy, or zero risk, especially during an early testing stage.

Libraries and SDKs

The App uses open-source libraries and standard Android/Qt build components required for its stated functionality. Firebase Cloud Messaging is used only to provide generic message notifications. Third-party and open-source components are included solely to support the App’s stated functionality.

The App does not use advertising, analytics, or tracking SDKs.

Store disclosures

The App is intended to operate only as described in its store listing, in-app screens and privacy disclosures. Store declarations are updated when the App’s data handling or permissions change.

Software behaviour

The App is not designed to install other applications, introduce undisclosed functionality through downloaded executable code, or use permissions for purposes unrelated to its documented features.

Your choices

You can choose not to submit the contact form and not to create or use a test account. You can also deny optional permissions such as camera access, though some QR-code features may not work without that permission.

You can delete your VXN account directly in the app through Settings > Delete account. You can ask about, correct, or request deletion of information associated with a closed-test invitation by writing to privacy@velixnet.com and including enough detail to identify the request.

Contact and updates

This notice may be updated as Velixnet and VXN change. Last reviewed: 4 September 2026. Privacy questions, correction requests, and deletion requests can be sent to privacy@velixnet.com.

Velixnet © 2026 Closed testing — VXN in development.
privacy@velixnet.com
Privacy & GDPR Terms Beta notice