Fair Usage Policy (FUP)

1. Purpose and scope

Purpose: This Fair Usage Policy (FUP) defines reasonable use limits and enforcement measures to ensure stable, secure and equitable access to Guru VPN services (the “Service”) for all Users.
Scope: This FUP applies to all Users of the Service and is incorporated into the Terms of Service. Where a specific plan or promotional offer contains bespoke limits, those prevail over the generic FUP.
This FUP supplements the Guru VPN Terms of Service and should be read together with our Privacy Policy, No-Logs Policy, Acceptable Use Policy, and other policies referenced in the Terms.

2. Principles

Equitable access: The Service is provided to enable fair access for all Users; excessive or abusive consumption that degrades service for others may be restricted.
Proportionality: Enforcement measures aim to be proportionate, minimally disruptive and targeted to restore normal operation.
Transparency: We will publish or communicate applicable limits and significant changes via our website, legal/policy page, account dashboard, app legal section or another official publication location, and notify affected Users through a reasonable communication method where practicable.

3. Allowed use

General: Users may use the Service for lawful personal and (if permitted by plan) business purposes in accordance with the Terms, AUP and this FUP.
Reasonable consumption: Normal browsing, streaming, remote access, secure communications and moderate file transfer consistent with the selected subscription tier are permitted.

4. Usage limits and examples of excessive use

Bandwidth and traffic: sustained aggregate traffic that materially impairs network performance may be addressed using aggregate server traffic volume, infrastructure-impact signals, IDS/IPS alerts, error rates or external abuse reports. Aggregate traffic measurements concern servers and infrastructure as a whole and are not calculated or retained for individual accounts. Account-specific enforcement may rely on available primary connection records, security alerts, external reports, account information and registered-device status. Primary connection records have no age-based cleanup and are deleted with the account. DNS request records are not currently used for FUP enforcement.
Registered devices: Each plan has a maximum number of registered devices, currently up to four (4) devices unless the applicable plan states otherwise. Exceeding that registered-device limit or attempting to bypass device-limit controls is not permitted and may trigger enforcement.
Resource monopolization: use that materially strains shared infrastructure may be considered excessive where reasonably identifiable through available technical signals, security alerts, registered-device checks or abuse reports. Device limits use registered-device status rather than a live concurrent-connection counter. Separate analytics of VPN connection start/end events are disclosed in the Privacy Policy and No-Logs Policy.
Automated or bot traffic: Continuous automated scraping, crawling, distributed scanning or other bot activity originating from the Service that imposes load on our infrastructure or third-party systems may be restricted. Our ability to identify such activity is limited to available indicators, such as anomalous network patterns, infrastructure impact, external complaints, and other abuse signals; we do not guarantee precise identification of all automated activity.
Abuse of trial or promotional offers: Repeatedly creating accounts to exploit free trials or promotional offers is prohibited.

5. P2P, torrents and bandwidth‑intensive activity

P2P allowance: P2P file-sharing may be permitted on designated servers only and subject to applicable law and plan terms. Torrenting and other high-bandwidth P2P that causes sustained node saturation may be limited or redirected to specialized servers.
Illegal content: Use of P2P to distribute copyrighted or illegal content remains prohibited under the AUP and may lead to suspension.

6. Throttling, shaping and redirection

Traffic management: To protect network stability we may apply temporary traffic management measures (throttling, shaping, traffic redirection) during congestion or where misuse is reasonably indicated by available technical signals, external complaints, or other reasonable grounds.
Notification: Where reasonably practicable we will notify affected Users of applied management measures and expected duration via email, in-app notice, website notice, account dashboard notice, push notification, or any other reasonable communication method.

7. Suspension, restrictions and termination

Remedies for excessive use: For violations of this FUP we may, at our discretion:

restrict or reduce bandwidth for the offending account;
limit access to specific servers or features;
require plan upgrade to continue usage at current levels;
temporarily suspend or permanently terminate the account for repeated or severe violations.

Refunds: Refund eligibility after a restriction or termination is governed by the Refund Policy and Terms of Service, subject to mandatory consumer rights. FUP enforcement does not automatically establish entitlement to, or exclusion from, a refund.

8. Monitoring and enforcement

Monitoring: We may use available primary connection records, registered-device status, aggregate server traffic volume and infrastructure performance, IDS/IPS alerts, external complaints and error rates. The primary connection table includes a start timestamp and available status, without an end timestamp or real source IP address. Separate Amplitude and BigQuery analytics include VPN connection start/end events, IP addresses and identifiers; their existence does not itself establish their use for FUP enforcement. We do not use per-user traffic-volume totals, a live concurrent-connection counter, DNS request records or retained communications content for FUP enforcement.
Investigations: Suspected violations may prompt internal investigation. We may request information from the User to assess usage patterns.
Privacy: Monitoring is conducted in accordance with our Privacy Policy and applicable law.
Retention: primary connection records have no age-based cleanup and are removed with the account through cascade deletion. The standard operational log retention period is 14 days. Database backups remain for no more than 14 days; VPN servers have no backups. DNS records in the logging system are retained for 14 days, while BigQuery exports have no configured fixed expiration. DNS request records are not currently used for FUP enforcement. Provider-held and exported records may remain after primary account deletion, as described in the Privacy Policy and No-Logs Policy.

9. Exceptions and enterprise plans

Exceptions: Legitimate high‑volume use cases (research, corporate VPN needs, content delivery) should be discussed with us. We may provide custom plans, dedicated resources or enterprise terms to accommodate such needs.
Enterprise agreements: Corporate or bespoke contracts may include tailored fair‑use provisions and SLAs; those controls supersede this generic FUP where expressly stated.

10. Appeals and dispute process

Appeal: If you believe a restriction or enforcement action was applied in error, submit an appeal to support@guruvpn.com or privacy@guruvpn.com within 14 days, including relevant evidence, dates/times, account details and an explanation.
Review: We aim to respond within 14 business days. If we find an error, we will lift or adjust the measure and restore service where appropriate.

11. Changes to the FUP

Modifications: We may amend this FUP from time to time. Updated versions will be published at our website, legal/policy page, account dashboard, app legal section, or any other official publication location with the date of last update.
Continued use: Continued use after publication of changes constitutes acceptance of the updated FUP.

12. Definitions

“Excessive use” — usage patterns that materially degrade network performance or impair other Users’ access, as determined by us.
“Registered devices” means devices linked to an account for plan-limit purposes. Limits are enforced through registered-device status rather than a live count of simultaneous connections. This definition does not exclude the collection of connection analytics described in the Privacy Policy.
“Traffic management” — temporary technical measures (throttling, shaping, redirection) applied to preserve network stability.
Other capitalized terms have the meanings given in the Terms of Service.

13. Contact

13.1. For questions, appeals or custom plans contact: support@guruvpn.com or privacy@guruvpn.com.

Effective date: 01.07.2026.