Guru VPN No-Logs Policy

Effective date: 01.07.2026 | Version: 1.0

This No-Logs Policy explains how GURU NETWORK S.R.L. ("Company", "we", "us", "our") applies its no-logs commitment in connection with the Guru VPN service, including the website guruvpn.com, mobile applications, VPN infrastructure, and related services (collectively, the "Service").

This Policy supplements and should be read together with our Privacy Policy, Terms of Service, Fair Usage Policy, Acceptable Use Policy, Cookie Policy, and Refund Policy. If there is any inconsistency between this Policy and the Privacy Policy, the Privacy Policy governs the processing of Personal Data.

1. Our no-logs commitment

Our no-logs commitment is limited to the content carried through the VPN tunnel: we do not retain communications content, traffic payloads, full URLs or page content. Guru VPN does record connection metadata, DNS requests and analytics events, including IP addresses. This Policy explains those records and must not be read as a claim that no VPN-related activity data is stored.

The primary Vpn Connection Sessions table does not store users' real source IP addresses. Separately, the original IP is visible to the VPN server, and Amplitude receives IP addresses associated with user/device/session identifiers and VPN connection events. Those analytics events are exported to BigQuery. We therefore do not make a general claim that source IP addresses are never stored or associated with a user identifier.

Our DNS resolver records individual DNS requests in the logging system and exports data to BigQuery. The DNS record format contains no direct user/account ID, device ID, connection ID or real source IP field, but includes domain, time and server information. We do not use that dataset to identify which user made a request. Absence of direct identifiers is not a guarantee of irreversible anonymity.

Registered-device limits are enforced using devices linked to an account, not a live count of simultaneous connections. Separately, analytics include events relating to VPN connection start and end; the device-limit mechanism does not imply that no session events are retained.

We also process account, subscription, billing, authentication, security, diagnostics, registered-device, support, cookie, SDK and push-notification data. The Privacy Policy describes their purposes, storage locations, retention periods and deletion limitations, including the absence of a fixed expiration period for BigQuery exports.

2. Quick summary

The table below summarizes the main categories relevant to our no-logs position:

3. Scope of the traffic content commitment

The following limits apply to records of content carried through the VPN tunnel:

• we do not retain the content of communications or message content carried through the VPN;
• we do not retain traffic payloads or packet contents as user activity logs;
• we do not retain full URLs or page content carried through the VPN;
• we do not maintain a full browsing history for each user; domain-level DNS request records nevertheless exist as described in Section 4.4;
• the primary connection table contains no real source IP; separate analytics records can contain original or VPN exit IP addresses;
• the DNS record format contains no direct account, device, connection or real source IP field; this is a limitation of the record format, not a claim that no DNS requests are logged;
• registered-device limits do not depend on a live user-level concurrent connection counter; VPN start/end analytics events are still collected;
• DNS request records are not used to build individual browsing or advertising profiles.

4. Limited data and technical signals we may process

The categories below include account-linked operational and analytics data, as well as DNS request records without direct user identifier fields. They are separate from the traffic content excluded above.

4.1. Account and subscription data.

We process email address, account and subscription status, authentication metadata, registered-device details and support communications. A random UID is generated at registration and used as an account identifier. Re-registration creates a new UID, but does not erase historical records associated with the old UID in other systems.

4.2. Payment and billing metadata.

We process limited payment and billing metadata such as transaction identifiers, receipts, subscription IDs, billing email/name where provided, and payment provider references. We do not store full card numbers on our servers.

4.3. Primary connection records.

The primary database on DigitalOcean in the Netherlands stores an internal account or registered-device reference, VPN server identifier, connection start timestamp and an available connection-status indicator. The Vpn Connection Sessions table has no connection end timestamp or real source IP address. There is no cleanup based on record age; the account and linked connection records are removed by cascade deletion when the account is deleted, without an additional 30-day holding period. Metabase queries the source data live for cohort and connection-rate metrics. Amplitude events described in Section 4.8 are a separate dataset.

4.4. DNS request records.

Our DNS resolver logs requested domain names, timestamps, query protocol and type, DNS query identifier, request size, response duration, server hostname and service/log type. Records are retained in the logging system for 14 days and exported to BigQuery in the United States without a configured fixed expiration period. BigQuery copies remain while the warehouse service is maintained. These are DNS request records rather than only aggregate statistics. The record format has no direct account, device, connection or source-IP field. The dataset is not currently used for an active operational purpose, FUP/AUP enforcement or refund assessment. It is not described as irreversibly anonymous. DNS names do not include full URLs or page content.

4.5. Security and IDS/IPS signals.

We may use an IDS/IPS system to analyze limited network-level traffic signatures and patterns for indicators of suspicious activity, malware behavior, scanning, attacks, abuse, or other security threats. The system may generate security alerts or technical indicators based on predefined or configured signatures and patterns. Alerts may include internal device identifiers or other technical indicators that can allow account/device association where necessary for security, abuse-prevention, or lawful-request handling. This analysis is intended for signature- and pattern-based security detection, not for reviewing the substance of user communications or maintaining browsing histories. We do not retain traffic content, packets, or traffic payloads as user activity logs for routine Service operation, and signature-based detection is not guaranteed to detect all misuse or security threats.

4.6. Registered-device limits.

Each plan may limit the number of registered devices, currently up to four (4) unless the applicable plan states otherwise. We enforce these limits using registered-device status rather than a live count of simultaneous connections. This does not exclude the collection of VPN connection analytics events..

4.7. Aggregate server-level traffic volume and infrastructure metrics.

We may use aggregate server-level traffic volume, aggregate infrastructure performance signals, error rates, abuse reports, external complaints, and IDS/IPS alerts to protect network stability and enforce the Fair Usage Policy and Acceptable Use Policy. These measurements relate to VPN servers and infrastructure as a whole. We do not monitor, calculate, or retain traffic-volume totals for individual users or user accounts. We rely only on metrics actually available under our technical architecture and do not claim to detect all possible misuse. These metrics do not include traffic content, browsing history, full URLs, page content, or communications content.

4.8. Analytics, diagnostics and SDK data.

Amplitude receives VPN connection start/end events, user_id, device_id, session_id, IP addresses and device or approximate location information. Events may contain the original IP before connection or a VPN exit IP afterwards. Amplitude event data is exported to BigQuery. Other warehouse datasets include Firebase session data, OneSignal events, Singular campaign data, Stripe subscriptions/payments and Keitaro conversions, as detailed in the Privacy Policy. Metabase runs live queries; its cache stores SQL text, not query results. Manual connection diagnostics are collected only occasionally, over up to one day, analysed for the individual case and deleted immediately after analysis. They are not collected automatically. Website cookies, mobile SDK identifiers and push tokens are described in the Cookie Policy and Privacy Policy.

5. Why limited data is processed

Operational, account and analytics data may be processed for the purposes below where an applicable legal basis exists. The DNS request dataset currently has no active operational use; the list below is not a claim that the DNS archive is used for each of these purposes.

• to provide, maintain, and troubleshoot the Service;
• to authenticate users, manage accounts, verify subscriptions, and support billing;
• to protect the Service against fraud, attacks, malware, spam, scraping, DDoS activity, unauthorized access, and other abuse;
• to enforce the Terms of Service, Fair Usage Policy, Acceptable Use Policy, and registered-device limits;
• to improve performance, reliability, security filtering, and user experience;
• to respond to support requests and data subject requests;
• to comply with applicable legal, accounting, tax, and lawful request obligations.

6. FUP and AUP enforcement

Enforcement of the Fair Usage Policy and Acceptable Use Policy may be based on limited service metadata, registered-device status, aggregate server-level traffic volume and infrastructure impact, IDS/IPS alerts, external abuse complaints, payment or account signals, currently available historical user-linked connection records, and user communications with support, only to the extent these signals are actually available under Guru VPN's ordinary technical architecture. DNS technical logs are not currently used for enforcement.

FUP and AUP enforcement does not use DNS request records, per-user traffic-volume totals or a live concurrent-connection counter. The collection of IP-bearing analytics events is disclosed in Section 4.8; it does not itself establish that those events are used for enforcement. We do not retain communications content or traffic payloads for enforcement.

Because detection is limited to available technical signals and external reports, we do not claim to identify every prohibited activity. Where practicable, we may provide notice and an opportunity to remedy before restrictions, unless immediate action is required to protect the Service, other users, third parties or legal interests.

7. Retention

Retention differs by system and data category. The 14-day retention periods for the logging system and database backups do not apply to BigQuery exports or all records held by external providers.

Primary connection records have no age-based cleanup and are removed with the account through cascade deletion. The logging system retains DNS records for 14 days; BigQuery has no configured fixed expiration for DNS or the six analytics/payment source datasets and keeps them while the warehouse service is maintained. Database backups are retained for no more than 14 days, and VPN servers have no backups. Standard operational log retention is 14 days. Occasional manually collected connection diagnostics are deleted immediately after analysis; their collection window is up to one day.

Account deletion is not currently sent automatically to Amplitude, Stripe, RevenueCat or Brevo, and does not constitute a complete purge of BigQuery exports. Old identifiers and historical records may remain after customer profile data is removed. Billing, support, investigation and other provider-held records follow the purposes, applicable legal requirements and limitations described in the Privacy Policy. This Policy does not promise a fixed deletion period for a provider where none is specified.

We cannot retain or disclose traffic content, full URLs or page content that we do not record. We may hold DNS request records, connection metadata and IP-bearing analytics events, and do not claim that these categories are unavailable for a lawful request.

8. Service providers and infrastructure

We use infrastructure, analytics, payment, subscription, communications and push-notification providers. The primary application/database infrastructure is in the Netherlands; BigQuery datasets are in the United States. Relevant providers and exports are described in the Privacy Policy, including Amplitude, Firebase, Stripe, RevenueCat, Brevo, OneSignal, Singular and Keitaro.

International transfers and provider relationships are subject to applicable data protection requirements and the arrangements described in the Privacy Policy. Provider retention settings and the absence of automatic erasure do not remove our obligations or users' statutory rights.

9. Lawful requests and disclosures

We may disclose information where legally required, to comply with lawful requests, to protect rights, property, safety, the Service, or users, or to respond to legal process. Any disclosure is limited to data we have and can lawfully disclose.

If information exists and disclosure is legally required, it may include account or billing data, registered-device status, primary connection records, security alerts, support communications, DNS request records and analytics/SDK data, including IP addresses and identifiers. No traffic-content or full-URL logs can be provided where they are not created or retained. The absence of direct user fields in DNS records is not a guarantee that no information can ever be correlated.

10. Account deletion and data subject rights

Users may exercise rights to access, rectify, erase, restrict, object to processing, request portability, or withdraw consent where applicable by contacting privacy@guruvpn.com or support@guruvpn.com.

Deleting an account removes the primary user record and linked connection records through cascade deletion. It does not automatically erase all downstream data, old UIDs, analytics events or warehouse exports. Database backups may retain deleted primary data until expiry, for no more than 14 days. Re-registration creates a new UID without erasing the old history in other systems. To request erasure of remaining Personal Data, contact the addresses above; the Privacy Policy explains this process and lawful retention exceptions.

11. Internal controls and review

We maintain technical and organizational controls intended to keep our no-logs commitments accurate and enforceable, including access controls, limited permissions, security reviews, vendor reviews, and internal or independent assessments where applicable. The current systems do not apply a fixed automatic deletion schedule to user-linked connection records or the existing DNS technical dataset; this limitation is disclosed in this Policy and the Privacy Policy.

If our architecture or logging practices materially change, we will update this Policy and related public policies to reflect those changes.

12. Changes to this No-Logs Policy

We may update this No-Logs Policy from time to time. Material changes will be posted with a new effective date and, where appropriate, notified to users through the Service or other reasonable means.

13. Contact

For questions about this No-Logs Policy, privacy practices, data subject requests, or lawful request handling, contact:

• Privacy: privacy@guruvpn.com

• Support: support@guruvpn.com

• Legal / law enforcement requests: support@guruvpn.com or privacy@guruvpn.com

Last updated: 01.07.2026