These Terms of Service ("Terms") form a binding agreement between STOPBOT.NET ("Stopbot", "we", "us" or "our") and the person or organization that accesses or uses the Service ("you" or "Customer").
By creating an account, purchasing a plan, calling an API, installing an official integration or otherwise using the Service, you accept these Terms and our Privacy Policy. If you do not accept them, do not use the Service.
1. Agreement, authority and eligibility
You must be legally able to enter into this agreement. If you use the Service for a company, client or other organization, you represent that you have authority to bind that organization, and "you" includes that organization.
- You must provide accurate registration and billing information and keep it reasonably current.
- You must comply with laws and regulations applicable to your use, your users and the data you submit.
- You may not use the Service if applicable law prohibits you from receiving it.
- Stopbot is a business and developer service and is not intended for children.
Documents that form the agreement
These Terms, the Privacy Policy, the plan or checkout details accepted by you, applicable product documentation, and any separately signed order form or data processing agreement together form the agreement for the relevant subject.
| Document | What it controls |
|---|---|
| Signed order form or custom agreement | Negotiated commercial terms for the specific order. |
| Data processing agreement | Covered processing of personal data. |
| These Terms | General use of Stopbot and all self-service purchases. |
| Plan and checkout details | Price, quota, duration, currency and selected features for a purchase. |
| Documentation | Current technical requirements, endpoint behavior and integration instructions. |
A more specific document controls only for its subject. Mandatory consumer rights that cannot lawfully be excluded remain unaffected.
2. The Stopbot service
Stopbot provides API-driven visitor intelligence, traffic decisions, redirects, network lookup and validation tools. Available functions may include:
| Component | Purpose |
|---|---|
| Blocker | Returns visitor, network, bot, threat and configured access-decision fields. |
| Blocker V2 | Applies a named customer configuration and can return a configured redirect, HTTP status or stay-on-page response. |
| SmartURLs | Combines visitor detection, configured destinations and optional browser verification for redirect flows. |
| IP Lookup | Returns available IP, hostname, ASN, network and approximate geographic information. |
| Email Validation | Evaluates email syntax and domain-level signals such as disposable status, MX, SPF and DMARC. |
| Phone Number Identify | Evaluates international number validity and available type, carrier, location and country metadata. |
| Panel and Account API | Manage configurations, lists, logs, statistics, API credentials, plan, quota, usage and expiration. |
| Official clients and plugins | Provide reference or ready-made integrations for supported server and application environments. |
Features, datasets, provider coverage and response fields may change as the Service evolves. A feature shown in documentation or source code is available only while it is enabled for your account, plan, region and current service version.
The Service is not an emergency service, identity authority, payment guarantee or substitute for a complete security program. Do not use it as the sole control for safety-critical systems or decisions that produce legal or similarly significant effects on a person.
3. Accounts, sessions and API keys
You are responsible for all activity performed through your account, sessions, API keys and integrations, whether performed by you, your personnel or a third party you authorized.
- Use a unique, strong password and protect account recovery channels.
- Keep API keys only in backend configuration, environment variables or protected server-side plugin settings.
- Do not publish keys in frontend JavaScript, mobile bundles, public repositories, screenshots, logs or public support messages.
- Regenerate or rotate a key immediately when exposure is suspected, then update every authorized integration.
- Limit panel and server access to personnel who need it.
- Notify Stopbot promptly about unauthorized account use or a security incident involving the Service.
You may not sell, rent, sublicense, publicly share or transfer account access or API keys unless a Custom Partner agreement or other written authorization permits it. Creating multiple accounts to evade plan restrictions, rate limits, suspension or abuse controls is prohibited.
We may require email verification, reauthentication, CAPTCHA or other reasonable verification before allowing sensitive account actions. You are responsible for maintaining access to the registered email address.
4. Trial access, paid plans and quota
Trial access
Stopbot may provide limited trial access after account registration and email verification. Trial availability, duration, quota and accessible features may be limited, changed or withdrawn. Trial access has no service-level commitment and may not qualify for promotions, transfers, affiliate credit or other paid-plan benefits.
Paid plans
Paid plans are prepaid access packages with a specified API request quota and active duration. Unless checkout or a signed agreement states otherwise, access to paid API operations ends when the quota is exhausted or the plan expires, whichever occurs first.
| Plan event | What happens |
|---|---|
| Authenticated API request | The request may consume quota, including connection tests and service checks. Current documentation describes endpoint-specific behavior. |
| Quota exhausted | Restricted requests may return HTTP 402 until quota is increased or a new plan becomes active. |
| Plan expired | Restricted requests and panel operations may be unavailable until access is extended. |
| Unused quota at expiration | Unused requests expire with the plan and do not carry over unless a written offer expressly says otherwise. |
| Renewal or upgrade | The plan, quota, usage and expiration shown in the panel or Account API reflect the resulting account state. |
Quota is a limited right to submit requests during the applicable plan period. It is not money, stored value or a transferable asset. Stopbot's metering records control unless you identify a reproducible error and report it promptly with non-sensitive evidence.
Published plans may change for future purchases. A price or feature change does not retroactively change the quota and duration already purchased for an active plan, unless required for security, law or a separately accepted migration.
5. Prices, payments, renewal and refunds
The price, currency, discount, plan duration and quota displayed at checkout apply to that purchase. Payment may be processed by an available third-party gateway. You authorize the selected provider to process the transaction and agree to its applicable terms.
Except where applicable law requires a refund or Stopbot expressly agrees otherwise in writing, completed payments are non-refundable. This includes unused quota, partial use, configuration mistakes, failure to integrate, account inactivity and a decision to stop using the Service.
- Payment status. A pending, expired, cancelled or failed payment does not activate a plan. Activation occurs after the required confirmation is received.
- Taxes and fees. You are responsible for applicable taxes, bank charges, gateway fees, blockchain network fees and currency-conversion costs unless checkout states they are included.
- Digital-asset payments. Blockchain payments may be irreversible. You are responsible for the correct asset, network, amount and destination shown by the payment provider.
- Unauthorized charges. Contact support promptly if you believe a charge is unauthorized. Fraudulent or abusive chargebacks may lead to suspension while the transaction is investigated.
- Automatic renewal. A plan renews automatically only if automatic renewal is clearly offered and you expressly enable it. You may cancel future renewal through the available account or support process; cancellation does not retroactively refund the current plan.
- Future pricing. We may change prices and discounts for future purchases. The amount confirmed for a completed transaction remains the amount for that transaction.
Nothing in this section limits refund, cancellation or other rights that cannot lawfully be excluded in your jurisdiction.
6. Legacy subscription transfers
If Stopbot offers a transfer from the legacy stopbot.net platform to the current panel, the transfer screen and its confirmation form part of these Terms. The current transfer program is intended for a matching, active, paid, non-Trial legacy subscription with remaining quota.
| Transfer rule | Effect |
|---|---|
| Account matching | The registered email must match the eligible legacy account. |
| Transferred quota | Only 50% of the eligible remaining legacy quota is transferred and added according to the transfer confirmation. |
| Plan and expiration | The eligible package and expiration are applied to the current panel as described in the transfer flow. |
| Legacy access | The old account is no longer active after a successful transfer. |
| Final action | A completed transfer is immediate, one-time and cannot be reversed through the self-service flow. |
Review the confirmation carefully before submitting. A rejected or disputed transfer must be reviewed through support and does not guarantee eligibility or restoration of the legacy account.
7. API use and integration responsibilities
Follow the current technical contract
You must use the documented endpoint family, parameters, methods, authentication format and response fields for your integration. Legacy V1 and current services can have different URLs, field names, nesting, status codes and SmartURLs verification behavior. Backward compatibility between API generations is not guaranteed.
Current technical requirements are published in the Stopbot documentation. You are responsible for URL encoding, input validation, request limits, HTTP status handling, timeouts, retry backoff and a safe fallback when the Service cannot be reached.
Protect credentials and request data
API keys must be used from trusted server-side infrastructure. Because current authentication and service inputs can use query parameters, full request URLs may appear in browser history, reverse-proxy logs or diagnostics. Do not place passwords, session cookies, bearer tokens, private keys, payment data or unrelated sensitive information in URL, user-agent, params or headers fields.
Apply decisions safely
Stopbot returns signals and configured response instructions. You decide how your website or application enforces them. isBot identifies a bot classification, while blockAccess identifies the configured access decision. A request can have isBot: 0 and blockAccess: 1 because another customer rule denied access.
- Test configurations with controlled traffic before enabling production enforcement.
- Review false positives, allowlists, blocklists, country rules and detection reasons.
- Validate SmartURLs and Blocker V2 destinations before redirecting a visitor.
- Prevent redirect loops when the current URL matches the configured destination.
- Do not call traffic endpoints for static assets unless the integration expressly requires it.
- Use bounded retries with backoff and do not create tight retry loops during an outage.
- Keep a safe local response for invalid JSON, timeouts, unavailable dependencies and rejected credentials.
Official integrations
Official clients and plugins simplify specific use cases but do not replace your responsibility to configure, test, update and secure the integration. Local logs, database tables, proxy settings, redirect exclusions and server permissions remain under your control.
8. Customer data, visitor data and privacy
You retain your rights in data, configurations and content you submit to the Service ("Customer Data"). You grant Stopbot a limited, worldwide right to host, transmit, process, reproduce and analyze Customer Data only as reasonably necessary to provide, secure, support and improve the Service, comply with law and enforce this agreement.
You represent that you have the rights, authority and lawful basis needed to submit Customer Data, including IP addresses, URLs, user agents, email addresses, phone numbers, request parameters and selected headers. You are responsible for notices, consent, data-subject requests, retention and other obligations applicable to your visitors and users.
- Collect and submit only data needed for the configured purpose.
- Remove secrets and unrelated personal or sensitive information before calling the API.
- Do not submit regulated data unless the Service, your agreement and your compliance program support it.
- Limit access to visitor logs and exported records.
- Respond to individuals who question a block, redirect or record associated with your application.
Our handling of account and service data is further described in the Privacy Policy. A signed data processing agreement controls covered processing when applicable.
9. Acceptable use
You may use the Service only for lawful website, application, network, fraud-prevention, validation and traffic-management purposes. You must not use, assist or permit the Service to:
- Violate a law, court order, sanction, export restriction or the rights of another person.
- Operate phishing, credential theft, malware, ransomware, deceptive redirects, unauthorized surveillance, spam or harassment.
- Make high-impact decisions about employment, credit, insurance, housing, education or healthcare without an independently valid legal basis, required safeguards and meaningful human review.
- Probe, attack, overload, disrupt or gain unauthorized access to Stopbot, its providers, another customer or a third-party system.
- Bypass quota, authentication, rate limits, account restrictions, access controls or security monitoring.
- Use another customer's key, configuration, visitor data or account without authorization.
- Reverse engineer non-public portions of the Service, scrape the panel, or systematically extract datasets except where law expressly permits and cannot be restricted.
- Resell, sublicense, timeshare or provide shared API access without a Custom Partner agreement.
- Submit false registration, billing, affiliate, abuse-report or support information.
- Use results as proof of a person's identity, intent, physical location, mailbox ownership or phone ownership.
- Remove notices, obscure Stopbot ownership, impersonate Stopbot or falsely claim an integration is endorsed.
- Use the Service in a way that creates unreasonable operational, legal or security risk.
We may investigate suspected misuse and cooperate with lawful requests. Reasonable technical restrictions may be applied immediately when necessary to protect the Service or others.
10. Affiliate and referral features
If affiliate or referral features are available to your account, commissions and payouts are subject to the records, thresholds, review status, payout methods and timing shown in the panel. Participation does not create employment, agency, franchise or partnership.
- Do not create self-referrals, duplicate accounts, fabricated users or artificial transactions.
- Do not use spam, misleading claims, impersonation, trademark-confusing domains or unlawful advertising.
- Commission is earned only from eligible, completed transactions and may be reversed for refunds, chargebacks, fraud, duplicate credit or invalid activity.
- You are responsible for tax reporting and for providing an accurate payout method and destination.
- Blockchain payouts may be irreversible; Stopbot is not responsible for an incorrect address, asset or network supplied by you.
We may hold, adjust or reject an affiliate balance or payout while investigating fraud, ownership, payment reversal, policy breach or a technical calculation error. Program rates and eligibility may change prospectively, and Stopbot may end the program with reasonable notice where practicable.
11. Ownership, licenses and feedback
Stopbot service
Stopbot and its licensors retain all rights in the hosted Service, private source code, interface, branding, documentation, compiled datasets, models, detection logic and other materials not expressly granted to you. Subject to these Terms and an active plan, we grant you a limited, non-exclusive, non-transferable, revocable right to use the Service for your internal or authorized customer-facing applications.
Open-source clients and plugins
Publicly distributed code is governed by the license included with its repository or package. At the date of these Terms, the official Stopbot WordPress plugin states GPL-2.0-or-later, while the current SmartURLs client repositories state CC0-1.0. The license file distributed with the relevant version controls if this summary differs.
An open-source license for a client or plugin does not grant free access to the hosted API, paid quota, private datasets, Stopbot trademarks or the panel. Use of the hosted Service remains subject to these Terms.
Customer materials and feedback
You retain ownership of your original configurations, application code and Customer Data. If you voluntarily provide suggestions or feedback, you grant Stopbot a perpetual, worldwide, royalty-free right to use it without an obligation to compensate you, provided we do not publicly identify you as the source without permission.
12. Third-party services and external data
The Service may depend on hosting, network, security, payment, authentication, analytics, chat, email, threat-intelligence, IP, DNS, carrier, geolocation or other providers. Third-party services are governed by their own terms and may change, delay, reject or discontinue functionality.
Stopbot is not responsible for third-party websites, payment-provider decisions, blockchain confirmations, browser behavior, hosting configuration, customer software or external data beyond our reasonable control. We may replace a provider or dataset when needed to maintain the Service.
Links to GitHub, WordPress.org, documentation hosts, status pages, social media or payment pages do not transfer ownership or responsibility to Stopbot for those independent services.
13. Availability, support and service changes
We aim to operate the Service reliably, but availability is not guaranteed. Maintenance, security events, provider failures, network conditions, database or cache failures, regional routing and events outside our reasonable control may interrupt or delay requests.
- No implied SLA. A service-level agreement applies only when separately signed.
- Support access. Support channels may be available at any time, but a response or resolution time is not guaranteed unless a written support commitment says otherwise.
- Status information. Public status information is provided for convenience and may not describe every customer-specific issue.
- Maintenance and security. We may perform planned or emergency maintenance and may act without advance notice when necessary to address risk.
- Changes and deprecation. We may add, modify, replace or discontinue features, response fields, providers or endpoint generations. We will use reasonable notice for material deprecations where practicable.
You are responsible for monitoring documented changes, maintaining supported integrations, testing upgrades and implementing a fallback appropriate to your application.
14. Suspension, expiration and termination
We may restrict, suspend or terminate access when reasonably necessary because of:
- a breach of these Terms, the Privacy Policy, a plan rule or a signed agreement;
- unauthorized, fraudulent, abusive or illegal activity;
- credential exposure, security risk or harm to Stopbot, a provider, customer or third party;
- payment failure, chargeback, expired access or exhausted quota;
- a legal request or a change that makes continued operation unlawful or impracticable; or
- discontinuation of the Service or relevant feature.
Where the risk is not urgent, we may provide notice and an opportunity to correct the issue. We may act immediately when delay could create harm, security exposure or legal risk.
You may stop using the Service at any time. Stopping use or deleting an account does not create a refund right. Before access ends, you are responsible for exporting any records you are entitled to retain. We do not guarantee continued panel access or recovery of configurations and logs after expiration or termination.
Provisions that by their nature should survive will survive, including payment obligations, ownership, disclaimers, liability limits, indemnity, dispute terms and obligations concerning data already processed.
15. Warranties and service disclaimers
To the maximum extent permitted by law, the Service is provided "as is" and "as available". Stopbot disclaims implied warranties of merchantability, fitness for a particular purpose, title, non-infringement and any warranty arising from course of dealing or usage of trade.
In particular, we do not warrant that:
- every bot, human, threat, proxy, VPN, hosting network, suspicious URL or abusive request will be classified correctly;
- the Service will be uninterrupted, secure, error-free or compatible with every environment;
- IP, hostname, ASN, company, ISP, location, timezone, carrier or device information is complete, current or exact;
- Email Validation proves that a mailbox exists, belongs to a person or will accept a message;
- Phone Number Identify proves ownership, current assignment or reachability of a number;
- a SmartURLs destination, customer redirect, blocklist, allowlist or configuration is safe, legal or correct; or
- results satisfy a particular legal, regulatory, security or compliance requirement.
You must use professional judgment, layered controls, appropriate human review and your own testing. Stopbot results are not legal, financial, identity-verification or compliance advice.
16. Limitation of liability and indemnity
Limitation of liability
To the maximum extent permitted by law, Stopbot and its owners, personnel, affiliates, licensors and providers will not be liable for indirect, incidental, special, exemplary, punitive or consequential damages, or for lost profits, revenue, business, goodwill, opportunities, data or use, arising from or related to the Service, even if advised that such damage was possible.
To the maximum extent permitted by law, Stopbot's total aggregate liability arising from or related to the Service will not exceed the amount you paid to Stopbot for the affected Service during the twelve months immediately before the event giving rise to the claim.
These exclusions and limits do not apply to liability that cannot lawfully be excluded or limited. Some jurisdictions do not allow certain limitations, so part of this section may not apply to you.
Indemnity
To the extent permitted by law, you will defend, indemnify and hold harmless Stopbot and its owners, personnel and affiliates from third-party claims, damages, losses, liabilities and reasonable costs arising from your Customer Data, applications, configurations, redirects, violation of law, infringement of third-party rights, misuse of the Service or breach of these Terms.
We will provide reasonable notice of a covered claim and allow you to control the defense, provided you may not settle a claim in a way that admits fault by or imposes an obligation on Stopbot without our written consent.
17. Disputes and general legal terms
Informal resolution
Before filing a formal claim, contact us with a clear description of the issue and requested resolution. Both sides will use reasonable efforts to resolve the dispute informally for at least 30 days, unless urgent relief or a legal deadline requires earlier action.
Governing law and forum
Any governing law or exclusive forum stated in a signed order form or separate written agreement controls for that agreement. Where no such term exists, applicable conflict-of-law rules and mandatory consumer-protection law determine the governing law and available forum. Nothing in these Terms removes a right or remedy that cannot lawfully be waived.
Other provisions
- Electronic communications. You agree that account, service, billing and legal notices may be provided electronically through the panel, registered email, website or documentation update log.
- Assignment. You may not assign this agreement without our written consent. We may assign it in connection with a reorganization, financing, merger, acquisition or sale of the relevant business or assets.
- Force majeure. Neither party is liable for delay or failure caused by events beyond reasonable control, except that payment obligations already due remain payable.
- Severability. If a provision is unenforceable, it will be limited to the minimum extent necessary and the remaining provisions continue.
- No waiver. Failure to enforce a provision is not a waiver of that provision or a later breach.
- No agency. These Terms do not create employment, partnership, joint venture, franchise, fiduciary or agency relationships.
- Entire agreement. The documents described in Section 1 are the entire agreement for the Service and replace prior discussions on the same subject.
- Headings. Headings and summaries improve readability but do not change the meaning of the full provisions.
18. Changes to these Terms
We may update these Terms for service, security, legal or operational reasons. We will update the date at the top of this page and, when appropriate, provide additional notice through the panel, registered email, website or update logs.
Changes apply from the stated effective date. Continued use after that date means you accept the updated Terms. If you do not accept a change, you must stop using the Service before it becomes effective. Material changes will not retroactively change the price, quota or duration of a completed purchase except where required by law, needed to address security or expressly accepted by you.
Terms contact
Questions about these Terms?
Contact Stopbot before purchasing or integrating if a term is unclear. Do not include passwords, complete API keys, payment credentials or session tokens in a support request.