Acceptable Use Policy

WireGress is a managed WireGuard gateway service designed for legitimate business infrastructure.

Our Acceptable Use Policy exists to protect the reliability, reputation, and availability of the service for all customers.

By using WireGress, you agree to comply with this policy.

1. Intended Use

WireGress is designed for business infrastructure including:

• Vendor allow-listing
• API and SaaS integrations
• CI/CD systems
• Production application connectivity
• Hybrid and multi-cloud networking
• Secure WireGuard peer connectivity

WireGress is not intended for anonymous browsing, consumer VPN usage, or activities that place our infrastructure or IP reputation at risk.

Eligible business customers may be located internationally, subject to the Terms of Service and applicable law. Where enabled, optional inbound TCP/UDP access must be secured and used only for authorized, lawful purposes. Downloadable peer configurations provide access to the hosted service; WireGress does not distribute WireGuard client software.

2. Prohibited Activities

You may not use WireGress to:

• Send unsolicited email (spam)
• Operate open mail relays
• Distribute malware or malicious software
• Perform denial-of-service attacks
• Conduct unauthorized port scanning or network reconnaissance
• Attempt unauthorized access to systems or networks
• Use the service for fraudulent or unlawful activities
• Interfere with the operation or security of the WireGress platform
• Circumvent service limits or enforcement mechanisms
• Supply access to, or use the service for the benefit of, a person, entity, destination, or activity where that supply or use is prohibited by applicable sanctions or export controls
• Evade sanctions or export restrictions, conceal prohibited end users or beneficiaries, misrepresent material identity, ownership, location, or end-use information, or use intermediaries to bypass a restriction
• Facilitate exports, reexports, transfers, releases, or services prohibited by applicable law, including prohibited nuclear, missile, chemical or biological weapons activities or prohibited military-intelligence end uses or end users
• Resell or commercially provide access to third-party customers without the written agreement required by the Terms, or permit unauthorized downstream resale

Restrictions depend on the applicable law and transaction, including any valid authorization; this policy does not treat every government, military, or internationally located customer as automatically prohibited. Where an authorization is necessary for WireGress to supply the service, WireGress must confirm it before access is enabled. Authorized resellers must meet the screening, downstream-contract, recordkeeping, reporting, and cooperation responsibilities in their reseller agreement.

3. SMTP Policy

Outbound SMTP (TCP port 25) is blocked by default on all plans to protect network reputation.

If your business requires direct SMTP delivery, contact support to discuss your use case.

SMTP submission using ports 465 or 587 is unaffected.

4. Bandwidth Usage

Each plan includes a monthly bandwidth allocation.

WireGress does not hard-cap bandwidth at your plan limit.

Instead:

• Notification at approximately 80% usage
• Notification at 100% usage
• Final warning at approximately 130% usage
• Customers expecting continued usage should contact support

Bandwidth usage resets at the beginning of each billing cycle.

Extremely excessive usage beyond the levels above may result in a temporary service pause until reviewed by our operations team.

5. Peer Limits

Each plan includes a maximum number of WireGuard peers.

Repeatedly creating and deleting peers within a short period may trigger temporary administrative restrictions designed to protect platform stability.

Normal administration and occasional peer changes are not affected.

6. Service Protection

To maintain service quality, WireGress may temporarily apply operational controls when infrastructure policies are exceeded or verified abuse is detected. We may also restrict access to address a credible compliance concern or comply with applicable law, as described in the Terms.

These controls may include:

• Temporary forwarding restrictions
• Temporary peer management restrictions
• Temporary bandwidth limitations
• Temporary gateway suspension
• Manual operational review

Operational controls protect infrastructure reliability and do not involve inspection of the application content of customer traffic. Suspension or termination for policy violations or legal restrictions is governed by the Terms.

7. Privacy

WireGress does not inspect, decrypt, or log the application content of customer traffic.

Operational enforcement relies on network and connection metadata such as:

• Bandwidth usage
• Connection counts
• Port activity
• WireGuard peer events
• Verified abuse reports

Compliance review may additionally use account, business, ownership, end-user, location, and screening information described in the Privacy Policy. We may review evidence voluntarily submitted with support requests or abuse reports. This does not involve inspection of the application content of customer traffic. See the Privacy Policy for collection, use, sharing, and retention practices.

8. Abuse Reports

Anyone may submit a good-faith abuse or compliance report through Report Abuse or abuse@apyl.com. We assess reports from upstream providers, network operators, security organizations, affected parties, and other reporters based on available evidence.

A false or unverifiable allegation alone will not justify permanent suspension. We may take interim protective measures while investigating credible concerns and must take action required by law. Where appropriate and legally permitted, customers will be contacted before additional enforcement actions. Advance notice may be omitted for urgent security, abuse, or compliance risks. Customers may request review through the contact below.

9. Enforcement Principles

WireGress follows several operational principles:

• Observable facts over inferred intent
• Deterministic rules over probabilistic detection
• Infrastructure signals over application inspection
• Predictable enforcement over intelligent enforcement
• Operational reliability over security product features

These principles guide operational enforcement. They do not exclude risk-based compliance screening, investigation of relevant warning signs, human review, or actions required by law.

10. Policy Updates

This Acceptable Use Policy may be updated as the service evolves.

Material changes will be published on the WireGress website.

Continued use of the service constitutes acceptance of the updated policy.

11. Contact

Questions regarding this policy may be directed to internal@wiregress.com.

Abuse reports: abuse@apyl.com. See Report Abuse for reporting instructions.