Release notes: v1.0 (launch)

Welcome to PrivateByRight VPN version 1.0. This is our launch release, built from the ground up to provide a secure, transparent, and technically sound VPN service. We designed this version to focus on the fundamentals: strong encryption, reliable protocols, and a strict adherence to data minimization. This isn't a beta—it's a fully functional release that delivers on our core privacy promises while laying the groundwork for future features.

What's included at launch

Protocols

We support two of the most reliable and secure VPN protocols available today.

• WireGuard (Default): Built for high performance and modern cryptography. It's lean, fast, and ideal for mobile devices or anyone prioritizing speed without sacrificing security.
• OpenVPN: A mature, battle-tested protocol. We include it as an alternative for users who need maximum compatibility, especially when navigating restrictive networks or strict firewalls.

Core features

Version 1.0 includes the essential features required to maintain your privacy and security online.

• Kill switch: This blocks your internet traffic if the VPN connection drops unexpectedly, preventing your real IP address from leaking. It operates at the system level by default, with configurable app-level exceptions for advanced users.
• Private DNS: All your DNS requests are routed through our encrypted tunnel and resolved by our own DNS servers. This prevents your ISP from seeing which websites you visit and protects against DNS leaks.
• Split tunneling: You can choose which applications route their traffic through the VPN and which use your regular, unencrypted connection. This is useful for accessing local network devices or services that block VPN traffic.

Supported platforms

At launch, PrivateByRight VPN is available on the major operating systems. You can secure your devices across:

• macOS
• Windows

No-logs policy

We do not log your browsing history, connection timestamps, session duration, or originating IP addresses. Our systems are designed from day one to minimize data collection. Our complete privacy policy is published and publicly available, and our infrastructure is designed to be audited by independent third parties to verify these claims.

Transparency Hub

Trust requires verification. Our Transparency Hub is live as of version 1.0. It includes our warrant canary and a log of any legal requests we receive. We believe you have a right to know how we handle data requests and whether our systems have been compromised.

Impact model

Privacy is a fundamental right, and we are committed to supporting the organizations that fight for it. Our impact model is live: a percentage of every subscription is automatically allocated to support privacy, press freedom, and human-rights initiatives.

Current limitations

This is version 1.0. While it is stable and secure, there are features we are still building and limitations you should be aware of.

• Multi-hop routing: Currently not available. All connections are single-hop to the server you select.
• Dedicated IP addresses: We do not offer dedicated or static IP addresses at this time.
• Linux GUI: While we support the core protocols, a dedicated graphical user interface for Linux is not included in this release.
• Advanced obfuscation: Bypassing deep packet inspection (DPI) in highly restrictive regions (like China or Iran) may be inconsistent. We are working on more robust obfuscation techniques.

What's coming next

We are already working on the next set of features and improvements. Our focus will be on expanding our server network, introducing advanced privacy features like multi-hop routing, and refining our client applications based on your feedback.

Learn more: Roadmap: what we're building next (next 90 days)

How to report bugs or feedback

Your feedback is critical to improving PrivateByRight VPN. If you encounter a bug, experience connection issues, or have a feature request, you can submit it directly through the support section in any of our apps, or by visiting our website's help center. Please include as much technical detail as possible (OS version, protocol used, and steps to reproduce) so our engineering team can investigate efficiently.