Quick answer
Which local checks are permitted?
As of 15 October 2026, LocalSERP Proxy is for authorised local-search observations, ad landing-page verification, price checks and testing your own applications. No KYC and crypto payment do not waive access rules. Keep Google Search and Maps checks manual, respect target refusals and report abusive traffic through the dedicated abuse contact.
1. Scope and responsibility
This policy forms part of the Terms of Service for every plan, gateway credential, sub-user and API key. You are responsible for requests made through access you control, including work performed by an employee, contractor or client. Read the destination’s access rules before starting a project. A publicly visible page is not a promise that all automated access is allowed. The service supplies a connection and does not confer ownership of data or permission from a destination.
2. Suitable local-check activity
Examples include a person comparing public local results between US cities, an advertiser inspecting its final landing URL, an ecommerce team testing its own delivery messages and a developer checking authorised localisation behaviour. Keep the method limited to the question. A city-selected exit alone does not certify a physical location or an exact map coordinate. Record conflicting location signals honestly. Repeatedly manufacturing page views, rankings or interactions is outside the purpose of a local observation.
3. Search, maps and advertising
Google Search and Maps workflows on this site are manual. Honour robots instructions and site terms; do not run automated access against disallowed routes. Use official reports and appropriately authorised services for scheduled measurement. Start campaign diagnostics with the advertising platform’s own preview and diagnosis tools. Inspect a final destination directly instead of clicking a paid advertisement. Do not create artificial clicks, impressions, installs or engagement, and do not manipulate reviews, ratings or business listings.
4. Prohibited conduct
Do not use the service for fraud, stolen payment instruments, credential attacks, unauthorised access, malware distribution, phishing, spam or denial-of-service traffic. Do not probe systems without the owner’s permission or collect private data by defeating access controls. Do not impersonate a business, create deceptive local reviews or falsify evidence for a client. Do not use a connection to defeat identity, payment or security checks. Activity that facilitates violence, exploitation or other illegal conduct is prohibited.
5. Blocked destinations and ports
Blocked categories: Banking, government and payment-portal sites, plus SMTP (email-sending) ports 25, 465 and 587. These restrictions apply across products. Do not try alternate hostnames, indirect routes or another account to defeat a service restriction. A destination can also choose to deny a request that the gateway would otherwise carry. Respect that decision. After a refusal, stop the affected operation, review the destination’s rules and use its official access route where one exists. A working proxy does not establish access permission.
6. Pace, credentials and shared resources
Set a reasonable pace for authorised requests and reduce activity when the target indicates overload or asks for a pause. Avoid floods of retries and repeated failed authentication. Keep passwords and API keys private, use separate project credentials where appropriate and remove access no longer needed. Use your port from several of your own devices and tools at the same time; bandwidth is shared between them. Reselling or sharing access with third parties is not allowed. Proxy (data) access only: no SMS, no calls, and no direct access to the SIM card or the device. An unlimited-data description remains subject to the fair-use condition stated beside that product.
7. Eligibility and service refusal
We may refuse or suspend service in case of abuse, fraud or a legal obligation. The service is not available in countries and regions under comprehensive sanctions. Some countries are not available, for legal or sourcing reasons, including countries and regions under comprehensive sanctions. Do not purchase or use access for a prohibited person, entity or place, or misrepresent who controls an account. Follow the rules applicable where you operate and where a destination is located. This policy is a service condition, not an assurance about the legality of a particular project.
8. Reporting and response
Send suspected misuse to [email protected] with an exit IP, the event time and time zone, destination hostname and a concise description. Include only evidence necessary to explain the event and redact credentials or unrelated personal details. Abuse reports are reviewed by a person, and confirmed abuse leads to suspension. We may restrict affected access while reviewing a report or protecting the service. Closure for a breach is handled under the terms; unused traffic can be lost. See privacy for the records available when a report is assessed.
Sources (3)
- Ad Preview and Diagnosis — Google Ads (2026-10-15)
- Terms of Service — Google (2026-10-15)
- Crawler instructions — Google (2026-10-15)