Purpose and scope
Huragon Technologies is registered in Kenya and is based in Kisii, Kenya. This policy forms part of the Huragon Terms of Service and covers the platform and its documentation. It applies to tenant owners, staff and anyone using Huragon through their authority. Use the platform only for lawful ISP operations and only with permission to manage the networks, accounts and information involved. Your own subscriber terms and network-use rules remain your responsibility.
Prohibited activity
- Fraud, impersonation, falsified subscriber or merchant details, forged receipts, duplicate payment claims, unauthorized refunds, credential theft or misrepresentation of payment confirmation.
- Unauthorized access to routers, workspaces, subscriber accounts, personal information or third-party infrastructure; bypassing authentication, tenant separation or access controls.
- Malware distribution, destructive code, denial-of-service activity, botnet operation, exploitation or interference with the platform or other users' networks.
- Unsolicited or unlawful bulk messaging, deceptive campaigns, harassment, threats, exploitation, or using Huragon to facilitate unlawful content or services.
- Collecting, disclosing, selling or using personal information without lawful authority; publishing credentials, payment PINs or other secrets; using staff access for unrelated purposes.
- Evading applicable telecommunications, spectrum, equipment, merchant, sanctions, consumer-protection or data-protection requirements.
- Abusive automation, deliberate service overload, falsified telemetry, interference with logs or payment verification, or attempts to conceal prohibited activity.
Configuration access is not permission to test, disrupt or compromise another organization. Security research must be authorized in advance and avoid exposing personal information or interrupting service.
Responsible operations
Maintain required approvals for your ISP activities, protect credentials and integration keys, use supported merchant configurations and review staff permissions. Validate payment evidence through approved workflows. Send communications only to appropriate recipients under applicable consent and messaging rules. Review AI suggestions before applying changes and share only information you may lawfully provide to the configured provider.
Respond promptly to abuse affecting resources under your control. Keep subscriber contracts and notices appropriate to your service. Do not promise customers that a Huragon account itself proves your licensing status or guarantees continuous access.
Network access and security testing
Manage only the routers, accounts, addresses and networks you own or are authorised to administer. Do not scan other tenants, bypass authentication or captive-portal controls, exploit exposed management interfaces, copy credentials or use Huragon as a route into third-party infrastructure.
Obtain written authorisation and an agreed scope before security testing that could affect the service. Do not copy subscriber records to prove a weakness, maintain unauthorised access, deploy persistence or disrupt traffic. Stop and report minimal necessary evidence if you encounter information outside your authority.
Protect management addresses, exports, backup files and support materials. Never publish working API keys, callback tokens, VPN credentials, private management links or subscriber access secrets.
Payment and billing integrity
Do not fabricate receipts, reuse another person's reference, intentionally misallocate collections, conceal reversals or alter records to obtain service without payment. An initiated request or browser message must not be represented as verified settlement.
Use merchant credentials only under an approved arrangement you are authorised to operate. Do not collect for undisclosed third parties, evade merchant checks, route prohibited funds or bypass provider restrictions. A managed merchant application requires approval before it can be represented as active.
Use documented correction, investigation and manual-payment workflows. Preserve the evidence needed for a dispute and avoid duplicating a receipt while troubleshooting. Deliberately falsifying subscriber or collection records to change platform charges is prohibited.
Subscriber information and confidentiality
Access records only for a legitimate, authorised service purpose. Do not browse out of curiosity, sell subscriber information, export a list for an unrelated business or use a former employee's credentials.
Collect relevant information, keep it accurate and restrict disclosure. Do not place identity documents, passwords, payment PINs, private router configuration or another organisation's records in public materials or general notes. Share only what a support case needs.
Respect applicable access, correction, objection and deletion processes. Do not erase, falsify or conceal evidence to obstruct a complaint, lawful investigation or regulator request.
Messages and harmful content
Send messages and campaigns only with the permissions and notices required for the purpose and recipients. Spam, phishing, deceptive payment prompts, malware, impersonation and deliberate evasion of an opt-out are prohibited.
Do not use the platform to facilitate exploitation, threats of violence, unlawful discriminatory conduct, child sexual exploitation, non-consensual intimate material, stalking, doxxing or another person's unlawful exposure to harm. This includes distributing content through the tools or using them to organise the prohibited activity.
Do not misrepresent prices, licensing, provider affiliation or service conditions. An ISP notice must not falsely appear to be an instruction from a regulator, bank, payment provider or Huragon Technologies.
Automation, scraping and AI
Supported automation must stay within the permissions, intended purpose and operating limits of its feature. Do not flood payment, login, messaging, router-control or documentation endpoints, circumvent rate limits or use multiple identities to disguise abusive traffic.
Bulk harvesting, republication, unauthorised dataset construction and AI-model training/fine-tuning using Huragon documentation require written permission, subject to mandatory law. Do not bypass crawler restrictions or use a false identity to obtain protected information.
Ordinary product use, appropriate accessibility tools and authorised integrations remain subject to the applicable terms. Public access to a guide does not entitle anyone to extract tenant records or operate a privileged API.
If optional AI assistance is enabled, share only information you may lawfully provide to its configured provider. Do not use it to generate fraud, steal credentials, compromise a network or evade safeguards. Review proposed actions before applying them.
Keeping ISP operations lawful
Maintain the approvals that apply to your territory and operating model, including telecom, spectrum/equipment, upstream/resale, tax, merchant and data-protection obligations. Do not present a Huragon workspace or guide as proof of regulatory approval.
Provide accurate subscriber terms, prices and complaint channels. Address abuse affecting resources under your control and cooperate with proportionate, lawful investigation. A configuration option does not itself create a legal entitlement to intercept, retain or disclose communications.
Evidence and appeals
A report should identify the affected account or public address, approximate times, the behaviour observed and the reason for concern. Provide only evidence you may lawfully share, with unrelated people and secrets redacted. Do not send a complete database or private key.
We may request clarification and preserve relevant records where appropriate and lawful. Investigative details may be restricted to protect people, accounts, confidential information or a lawful process.
If you dispute enforcement, explain the relevant facts and corrective steps to [email protected]. Creating a replacement account, changing merchant details or moving abuse to another tenant to evade a restriction is prohibited. A temporary restriction does not itself determine the final outcome.
Reporting a concern
Report suspected abuse or a security issue to [email protected]. Include a concise description, relevant dates, affected account/domain and safe supporting information. Avoid including passwords, payment PINs, full subscriber lists or unnecessary identity information. Do not continue exploiting an issue or accessing records in order to gather more evidence.
Investigation and enforcement
Huragon may assess reports and relevant operational records, request clarification and take proportionate action. Depending on severity, action may include a warning, request for remediation, restriction of a feature, suspension or account termination under the applicable agreement and law. We may cooperate with competent authorities when lawfully required.
Where practical and safe, we will explain the issue and provide an opportunity to correct it. Immediate restrictions may be necessary for an active security threat, serious abuse, risk to others or a legal/provider requirement. An emergency restriction does not by itself determine the final outcome of an investigation.
If you believe enforcement was mistaken, contact support with the account and relevant facts for review. Do not create another account or change merchant details to evade a restriction. Published versions identify their publication date and remain available for reference.