Trust & Compliance

AlocNet operates a strictly scoped proxy network serving six enterprise use cases. This page describes our acceptable use, compliance boundaries, and the audit artifacts available to enterprise customers.

6 use cases only — no general proxy traffic
Dedicated 1:1 allocation, zero shared pools
Per-request audit logs available
DPA and compliance documents on request

Service Integrity

  • • 1:1 dedicated IP allocation — no shared pools, no cross-client contamination.
  • • Customer use cases are vetted at onboarding — we decline workloads outside our six focus areas.
  • • Per-request audit logs with timestamp, egress IP, and target (retention: 30 to 365 days by plan).
  • • 24/7 abuse monitoring with immediate isolation for contaminated IPs.

Acceptable Use & Prohibited Workloads

  • • Permitted: ad verification, brand protection, SEO/SERP monitoring, market research, price intelligence, authorized cybersecurity work.
  • • Strictly prohibited: DDoS, scanning without authorization, credential stuffing, spam, fraud, CSAM-adjacent activity.
  • • Customers must provide a written use case statement at onboarding and update it when scope changes.
  • • Violations result in immediate suspension with no refund per our Terms of Service.

Operational KPI Targets

Connection Success

≥ 98%

successful connects / attempts

Median RTT (p50)

Zone Baseline

tracked by service region/zone

Abuse Rate

↓ MoM

monthly downward trend

Churn

Target-based

controlled by package-level target

Binding Scope Hierarchy

In case of wording conflicts, apply this order: (1) order confirmation/checkout scope, (2) Terms of Service, (3) relevant Policy, (4) informational summary pages such as this page.

Order Confirmation / Checkout
Terms and Policy
Operational Summary Pages

Policy Linkage (Onboarding & Billing)

Onboarding and checkout copy should reference the same Terms, Policy, and Billing/Refund policy to keep usage, suspension, and refund rules consistent across all channels.