Velixnet should explain plainly what it does and does not collect.

What we collect

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

When you create or use a test account, the service may process your Velix ID, password-authentication data, login session state, message envelope metadata, acknowledgement state, timestamps, and other delivery records needed to route encrypted messages.

Basic server and network logs may also exist as part of operating and securing the service.

What we use it for

Velixnet uses this information to run the website, respond to contact requests, prevent abuse, operate test accounts, route encrypted message envelopes, maintain service stability, and review problems during development.

Velixnet does not publish contact submissions, and the site is not intended to sell submitted contact details to advertisers or data brokers.

What remains visible to the server

Velixnet is built around end-to-end encrypted message content, but that does not mean the service sees nothing. 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.

What stays outside this notice

If you follow links to other websites or third-party services, their own privacy rules apply. This notice only covers the Velixnet website and Velixnet-operated testing service.

Retention

Early testing data is kept only as long as reasonably needed for service operation, abuse prevention, debugging, and staged review. The current technical design targets approximately 30-day retention for queued undelivered message records, though operational records and logs may follow different short-term retention periods while the service is still being tightened.

Contact submissions are kept for review and response until they are no longer needed.

Sharing

Velixnet may share information when reasonably necessary to host, secure, maintain, or investigate abuse affecting the service, or when required by law. The site is not presented as a platform for broad public sharing of user content.

Security

Velixnet aims to use HTTPS, client-side encryption for message content, rate limiting, and restricted server-side storage. But no website or test service can honestly promise perfect security, perfect secrecy, or zero risk, especially during an early public-testing stage.

Your choices

You can choose not to submit the contact form and not to create a test account. If you contact Velixnet and want your submission reviewed for deletion or correction, use the contact path listed on this site and include enough detail to identify the request.