> For the complete documentation index, see [llms.txt](https://xnet-mobile.gitbook.io/xnet-mobile-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xnet-mobile.gitbook.io/xnet-mobile-docs/deploy-connect-earn/quickstart-1/acceptable-use.md). # Acceptable Use ### ✅ What’s Allowed **Proper Locations**\ Deploy APs servicing **public access, business or commercial areas only.** All APs must be installed at carrier approved, contracted or operator owned locations. **Accurate Registration**\ Always provide an accurate location of your AP in XNET’s asset management system. This keeps the network optimized and ensures you’re eligible for $XNET rewards when carrier location approval and paid offload begins. **Solid Internet Uplink**\ Your connection should deliver at least 20 Mbps down/1 Mbps up per user or 100 Mbps down/10 Mbps at the bare minimum. We recommend gigabit or business-class internet to handle peak traffic in high-density locations. **Approved Backhaul**\ Use wired or fiber-based connections only. \ \&#xNAN;***No cellular backhaul***—even business-grade plans—due to reliability and throttling issues. **Auto Connection Only**\ The XNET experience should be seamless. End users must be able to connect **automatically via Passpoint**—no manual logins, T\&Cs or captive portals allowed. ### 🚫 What’s Not Allowed **Falsifying Deployment Locations**\ Submit accurate location information on where your AP is servicing. Residential deployment locations are not allowed unless servicing a business or public location. Inaccurate reporting may lead to bans or rewards disqualification. **Using APs as Personal Routers**\ The XNET network is meant for **public cellular offload**, not residential, not personal or consistent employee use. **Traffic Manipulation**\ Spoofing usage, altering traffic patterns, or interfering with Access Point configurations will lead to a ban or disqualification for $XNET rewards. **Unapproved Devices**\ Only use [**approved hardware**](https://xnet-mobile.gitbook.io/xnet-mobile-docs/deploy-connect-earn/quickstart-1/brownfield-conversions/supported-hardware) to ensure your APs aren’t flagged. **RADIUS Proxy Restrictions** (Mandatory) \ To ensure accuracy, accountability, and fairness in XNET’s WiFi roaming and carrier offload ecosystem, RADIUS proxying on the WiFi infrastructure side is strictly prohibited. Access Point Location Legitimacy (Mandatory) All APs must be installed at approved, contracted locations and accurately registered in XNET’s asset management system. ### Traffic Monitoring & Outliers XNET monitors AP traffic patterns to protect the network and ensure rewards integrity. **We flag patterns like:** * High offload with very few users * Consistently long sessions * Performance outside the expected norms **What to Expect:** * You may be contacted by support for verification ### Remediation & Offboarding **If issues persist after initial outreach:** 1. A Final Notice will be issued with steps for remediation 2. Reward Suspension will occur until traffic is normalized 3. AP Deactivation may occur (within 24 hours if critical) 4. Account closure and operator bans in severe or repeated cases ### Appeals & Incident Reporting * Report traffic anomalies immediately caused by localized events via support tickets * Appeal decisions in writing within **30 days** if you have supporting facts * All actions are handled by XNET’s fraud prevention team, with transparent communication from the support team\ \ ⚠️ ***XNET and its partners may suspend or permanently ban devices, operators, or locations that violate these policies.*** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://xnet-mobile.gitbook.io/xnet-mobile-docs/deploy-connect-earn/quickstart-1/acceptable-use.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.