Quick answer
Which records does LocalSERP Proxy retain?
As of 15 October 2026, LocalSERP Proxy keeps connection metadata for up to 30 days for billing disputes and abuse reports, plus account and transaction records. No KYC means no signup ID upload; crypto transactions can remain public. Request content, full URLs and page data are not logged by our service.
Who is responsible for these records?
ProxyGoat LLC, a limited liability company in Delaware, United States, operates LocalSERP Proxy and is responsible for the account and service records described here. Write to [email protected] about privacy, a correction or a rights request. For harmful traffic affecting your website, use [email protected] instead. An exit IP and event time can support an investigation, but a report should avoid exposing unrelated users or confidential content.
What is the retention rule?
We do not log the content of your requests, full URLs or page data. To handle abuse reports and billing disputes, we keep connection metadata (time, account, exit IP, target hostname, bytes) for up to 30 days, then delete it. We keep your account number, orders, top-up records and traffic totals while your account is open, and afterwards only as long as accounting rules require. We disclose records to authorities only when the law requires it. Our upstream network provider may keep its own logs under its own policy.
Records, purposes and retention
| Record | Purpose and retention |
|---|---|
| Account number and optional email | Account access and recovery. Account records remain while the account is open, then only as accounting rules require. |
| Order and top-up records | Delivering purchases, credit decisions and bookkeeping. Account lifetime, then required accounting retention. |
| Traffic totals | Displaying consumption and resolving billing questions. Account lifetime, then applicable accounting requirements. |
| Time, account, exit IP, target hostname and bytes | Billing disputes and abuse handling. Up to 30 days, then deleted. |
| Messages you send to support | Answering the request and maintaining the related support record. Ask for the applicable period for your request. |
| Settings and credentials | Providing the account features you choose, including sub-users and revocable keys. Do not include secrets in support email. |
What does no KYC mean for privacy?
No KYC: no ID, no selfie, no documents to sign up, top up or buy. We do not request an identity document, selfie or proof of address to create an account, fund it or purchase a plan. An optional account email is different from an identity check and is useful for recovery. If you volunteer personal information in a support message, it becomes part of the message we receive. Minimise it: do not attach identity documents or complete client reports when a redacted error would explain the problem.
Who receives information?
Upstream networks carry the traffic and may handle operational records under their own policies. Their visibility is separate from the records held by our service. Blockchain networks and explorers can expose transaction amounts, times and addresses publicly; paying in crypto does not remove that public record. Information may be disclosed to authorities when the law requires it, limited to records we hold. We do not offer customer records for advertising. Read sourcing for the provider’s attributed confirmation and the limits of a reseller’s inspection.
What legal bases apply where GDPR covers processing?
Where the EU or UK GDPR applies, providing the requested account and service relies on performance of a contract under Article 6(1)(b). Required accounting or legally required disclosure relies on a legal obligation under Article 6(1)(c). Abuse prevention, service security and handling a relevant support request can rely on legitimate interests under Article 6(1)(f), subject to the applicable balancing and objection requirements. These bases explain processing purposes; they do not expand the categories of gateway data listed above.
What can I request about my information?
Subject to the law that applies, you can request access, correction, deletion, restriction or portability, and object to processing based on legitimate interests. Some transaction records may need to remain for legal accounting duties. Contact support from the email associated with the account when possible; do not send the account number or password in an email. Without an account email, we may be unable to verify control for an account-specific request. We respond within the applicable legal period, and you may contact the competent data-protection authority.
How do browser settings and account security fit in?
The public pages are static. Browser or account preferences may remain in browser storage, and the client area uses functional session and account settings. Clearing site data or signing out can remove local convenience settings; it does not request deletion of server-side records. Keep your main account number in a password manager and remove unused project access. We never ask for your account number by email or chat. Use an ordinary separate profile for local tests and avoid putting your customers’ personal data into evidence screenshots.
Where do updates appear?
The review date identifies the current policy text. Material changes to the service’s record categories or retention are explained in the changelog. An older screenshot of this policy is not a substitute for the current version. For questions about a record not assigned a fixed period above, ask support for the purpose and applicable retention. Do not assume that no KYC means that a connection, payment or support request leaves no records.
Sources (1)
- General Data Protection Regulation, Articles 6 and 12–22 — European Union (2026-10-15)