Rug Cleaner uses limited operational analytics to understand which features are useful, maintain performance, prevent abuse, and diagnose failures. When you request an analysis, we also process the public token or wallet address you submit. Rug Cleaner does not use advertising trackers or build cross-site marketing profiles.
No advertising tracking
We do not use advertising tags or retargeting pixels.
No cross-site profiles
Rug Cleaner does not build or use cross-site marketing profiles.
14-day ordinary logs
Ordinary Rug Cleaner application and infrastructure logs are retained for 14 days.
What Rug Cleaner collects
Information you submit
Public token mints or wallet addresses that are needed to provide the analysis you request.
Page and feature usage
Which pages and product features are used, without advertising profiles.
Performance and failures
Response status, timing, performance, degradation, and short-lived operational identifiers.
Why we collect it
- Provide the token or wallet analysis you request
- Keep the service reliable and diagnose failures
- Apply rate limits, prevent abuse, and investigate security incidents
- Understand which features are useful and need improvement
How Cloudflare is involved
Cloudflare sits in front of Rug Cleaner to deliver the site, secure connections, reduce abuse, and measure performance. Cloudflare Web Analytics helps us understand page and browser performance. Cloudflare states that this analytics service does not use cookies or local storage to collect its metrics.
Cloudflare also processes operational and security information under its own terms and policies. Rug Cleaner does not directly control or delete every provider-side copy. Cloudflare's documented retention periods are identified separately below.
Your choices and contact
Browser privacy or content-blocking settings can reduce browser analytics, although they may affect site or security behavior. Requests still pass through Cloudflare's delivery and security systems when you use Rug Cleaner.
The Privacy Policy provides the broader description of how Rug Cleaner handles information and the material service categories involved. For privacy questions or requests, email support@rugcleaner.io with the subject Privacy Request.
Material changes will be identified in the Service and reflected in the last-updated date above.
Technical detailsExact identifiers, routes, systems, and provider behavior
Rug Cleaner operational telemetry
Rug Cleaner uses minimized first-party operational telemetry plus Cloudflare delivery, security, Web Analytics/RUM, and Network Error Logging. We do not use Google Analytics, Plausible, PostHog, advertising tags, retargeting pixels, or cross-site marketing trackers in the anonymous beta.
- Page and feature use needed to understand service demand and failures
- Request and trace identifiers used for debugging, rate limits, abuse control, and support
- Status, latency, cache, degradation, and Web Vitals or performance measurements
- Scan and analysis events that may include a submitted public token mint, wallet address, run ID, risk/status label, and timing
Ordinary logs are configured to omit unnecessary query strings, request bodies, cookies, authorization values, and secrets. Wallet and token identifiers are retained only where needed for the requested analysis or a documented operational purpose.
Cloudflare routes and services
For a proxied site, the Web Analytics beacon may be loaded from static.cloudflareinsights.com and report through Rug Cleaner's /cdn-cgi/rum route. Cloudflare states that Web Analytics does not use client-side state such as cookies or local storage to collect its metrics.
Cloudflare Network Error Logging may receive browser reports about failed or degraded network requests. Cloudflare states that client IP addresses are not stored in that NEL pipeline after processing, although reports can contain network-condition information. Cloudflare edge and security systems may separately process operational request data under Cloudflare's terms and policies.
Cookie and retention implementation
Rug Cleaner may set first-party rc_trace_id and rate-limit identifiers for up to 24 hours. Production cookies use Secure and SameSite=Lax; server-only rate-limit cookies also use HttpOnly. They support request correlation, reliability, and abuse controls—not advertising. Cloudflare may set or process separate strictly necessary security identifiers as part of its edge service.
Rug Cleaner ordinary application, proxy, container, Loki, and tracing logs are retained for 14 days. Security-incident evidence, when deliberately isolated, may be retained for up to 90 days after closure. The Cloudflare periods describe provider-documented service behavior; Rug Cleaner cannot directly delete provider-controlled copies.