No-Log Policy

Effective date: 2026-02-18

This No-Log Policy (“Policy”) explains how Securqbit (“Securqbit”, “we”, “us”, or “our”) approaches user activity data across our websites, applications, and VPN services (collectively, the “Services”). It is a binding commitment to our users and should be read together with our Privacy Policy and Terms of Service.

We are engineered to need as little information about you as possible. Where data is not required to deliver a secure, reliable, and lawful service, we do not collect it, store it, or process it.

1. Scope

This Policy applies to all users of the Services and to all traffic that passes through Securqbit VPN infrastructure. It covers the systems we operate, the data those systems handle, and the data we explicitly choose not to handle.

2. What We Do NOT Log

Securqbit does not collect, monitor, record, or store any of the following in connection with your use of the VPN:

  • Websites, URLs, or domains you visit
  • DNS queries that identify individual user browsing
  • The contents of any traffic routed through the VPN
  • Files, messages, or communications you transmit or receive
  • Originating IP addresses associated with your VPN session
  • IP addresses assigned by the VPN during your session
  • Connection timestamps tied to an individual user
  • Session duration or bandwidth usage attributable to a user
  • Ports, protocols, or destination servers you connect to
  • Your physical location or precise geolocation derived from VPN usage

Because this information is not collected, it cannot be produced, disclosed, sold, shared, or compelled — not by Securqbit, not by any third party, and not by any governmental authority.

3. What We May Process (Strictly Limited)

To operate the Services securely and reliably, a narrow set of operational data may be processed. This data is not a record of your activity and is designed to be minimal, aggregated, or short-lived.

  • Account data: Email address or other identifier you provide at sign-up, used to authenticate you and provide support.
  • Billing data (if applicable): Subscription status and payment records required by law and processed by regulated payment providers. Securqbit does not store full payment card numbers.
  • Aggregated service metrics: Non-identifying counters (for example, total connections per region, error rates, server load) used for capacity planning and reliability.
  • Diagnostic logs: Transient, non-identifying crash or error diagnostics that you may choose to submit from the app when reporting an issue.
  • Abuse prevention signals: Temporary signals used to mitigate attacks on our infrastructure (e.g., rate-limit counters), retained only as long as necessary and not tied to user activity.

None of the above constitutes a log of your browsing, DNS, or traffic activity, and none of it can be used to reconstruct such activity.

4. Infrastructure Design

Our no-log commitment is enforced in the architecture of the Services, not only in policy:

  • VPN servers are configured to avoid persistent storage of user traffic metadata.
  • Wherever practical, servers run on volatile-memory (RAM-based) configurations that do not retain state across reboots.
  • DNS resolution is operated to minimize retention and to avoid associating queries with individual users.
  • Access to production systems is restricted, audited, and limited to authorized personnel under strict operational controls.
  • Changes to systems that handle user traffic are subject to internal review to preserve this Policy.

5. Requests from Governments and Third Parties

Securqbit will assess any lawful request it receives. However, we can only produce data we actually possess. Because we do not log user activity as described in Section 2, we have nothing to hand over in response to requests for browsing history, traffic contents, DNS queries, or connection records tied to an individual user.

Where we are legally compelled to respond, our response will be limited to the narrow categories of data described in Section 3, and only to the extent required by applicable law.

6. Third-Party Processors

Where service providers help us operate the Services (for example, infrastructure hosting or payment processing), they are bound by contractual confidentiality and data-processing obligations. These providers do not have access to user activity data that we do not ourselves collect.

7. Limitations You Should Understand

A VPN protects the transport of your traffic; it does not make you anonymous in every context. Specifically:

  • Websites and services you log into can still identify you through your account credentials.
  • Cookies, browser fingerprints, and tracking technologies operated by third parties are outside the scope of a VPN.
  • Malware or compromised devices can expose activity regardless of VPN use.
  • Local networks, ISPs, or operating systems may retain records that are independent of Securqbit.

This Policy describes what Securqbit does and does not do. It does not alter the behavior of third parties or your device.

8. Verification and Accountability

We are committed to backing this Policy with transparency measures, which may include independent audits, transparency reports, and disclosure of any lawful requests we receive, to the extent permitted by law. Any such materials, if published, will be made available through our website.

9. Changes to This Policy

We may update this Policy to reflect changes in our Services, infrastructure, or legal obligations. We will update the effective date above. Material changes that expand what we process will be communicated before they take effect, where feasible.

10. Contact

Questions about this No-Log Policy: [email protected]

Security or legal inquiries: [email protected]