IPIN.IO (“we”, “us”, or “our”) is a set of lightweight networking tools for IP intelligence lookups, proxy checking, and log analysis. We built IPIN.IO with a zero-retention approach: no registration, no accounts, no query history, no saved inputs, no saved results, and no saved uploads. This policy explains—plainly and specifically—what we do and do not do with your data when you use our website and APIs.
Core Promise: IPIN.IO does not retain your query inputs or outputs. We do not store the IPs you look up, the proxy lists you test, the logs you upload, or any query logs. This is designed to reduce privacy risk and to help prevent accidental exposure of sensitive data (such as credentials mistakenly pasted into tool inputs).
1) How We Handle Your Information (No Accounts, No Retention, Only Per-Request Processing)
No registration and no user profiles. IPIN.IO does not provide an account system. You can use our tools without signing up or logging in. We do not ask you for personal identifiers such as your name, phone number, government ID, or payment information. We also do not create a persistent user ID to track you across sessions, and we do not build behavioral profiles from your activity.
Your inputs are processed only to produce the immediate result, and then discarded. When you submit an IP address, a batch list, a proxy endpoint, or a log file, our system must temporarily receive the data to compute a response. That temporary handling occurs in the course of fulfilling your request. We do not write your inputs to databases, long-term caches, object storage, or analytics pipelines. We do not save your outputs either. Once your request is completed, the data is not retained by IPIN.IO.
Tool-specific clarifications. For IP lookup, bulk IP/ASN lookup, and IP range analytics, the IPs and text you submit are used only to compute and display the requested information. For “My IP”, we necessarily observe your public IP address at request time in order to return it to you, but we do not store a history of those requests. For proxy checking (HTTP or SOCKS5), if you provide proxy authentication credentials, they are used only to attempt the connection for that test and are not stored by us. For log analysis, uploaded log content is parsed to generate statistics and charts for the current session, and then it is not retained by IPIN.IO.
No query logs. We do not keep query histories, and we do not store the mapping between your request and the input content you submitted. We do not use query contents to train models, create datasets, or share them with third parties. We also do not perform advertising tracking. If we must apply real-time abuse protection (for example, to keep the service available under heavy automated traffic), we aim to do so in a way that does not require storing your query content.
Cookies and local storage. We do not use cookies for advertising. If IPIN.IO stores preferences (such as language selection) in your browser, it is done only to improve usability and is not used to build profiles. You can clear your browser storage at any time; core tools will remain usable.
2) Third-Party Data Sources and Network Infrastructure (What We Don’t Control, and What You Should Know)
Multi-platform IP comparisons may send the target IP to third-party providers. Some IPIN.IO tools can compare results across multiple external IP intelligence or geolocation data sources. To fetch those results, we may transmit the target IP address you entered to one or more third-party API providers and then display their responses. IPIN.IO itself does not retain your target IP after the request, but the third-party provider may record requests for its own purposes (for example, rate limiting, abuse prevention, diagnostics, or service improvement) according to its policies. If you prefer not to involve third parties, avoid using features that explicitly rely on multi-source comparisons.
Proxy checking involves outbound connectivity tests. Proxy check tools work by making a connection from our servers to the proxy endpoints you provide. Your proxy server, upstream network, or hosting provider may keep its own logs of incoming connections (time, source IP, volume, etc.). Those logs are under the control of your infrastructure providers, not IPIN.IO. Our promise remains: we do not store the proxy lists you submit and we do not store proxy credentials.
Log analysis: you control what you upload. Server logs can contain sensitive information such as tokens, cookies, account identifiers, or other personal data. Even though IPIN.IO does not retain uploaded logs, you should upload only content you are authorized to process and you should remove or mask sensitive fields whenever possible (for example, Authorization headers, cookies, access tokens, or secrets). If you upload highly sensitive data, the primary risk is the act of submitting it over the network; we therefore recommend not uploading secrets at all.
Infrastructure realities. While IPIN.IO is designed not to persist your query content, internet infrastructure outside our control may generate transient records. For example, your ISP, corporate gateway, browser extensions, or network security appliances may keep logs. If we use a CDN, DDoS protection, or cloud hosting, those providers may also generate network-layer event logs for security and reliability. We strive to minimize exposure and keep our own systems free of retained query content, but we cannot guarantee how third-party networks handle traffic.
Legal requests. If we receive a valid legal request, we will comply as required by law. Because we do not retain query inputs or query logs, the historical data we can provide is typically very limited.
3) Your Rights, Security Measures, and Policy Updates
Your rights and practical limits under a zero-retention model. You may contact us to ask questions about privacy or to raise a concern. In many cases, because we do not operate accounts and do not retain query history, we do not have a dataset tied to you that can be searched or deleted on request. If you email us, we will use your email address and message only to respond and to provide support. Please do not send passwords, tokens, private keys, or other secrets by email.
Security practices. We use HTTPS/TLS to encrypt traffic in transit. We also apply basic operational security practices to keep the service stable and to reduce abuse (for example, request validation and rate control). Our most important security measure is architectural: we do not design flows that require storing your query contents. However, no internet service can be perfectly secure; you should avoid submitting highly sensitive data.
Changes to this policy. If we introduce features that materially change how data is handled (for example, an optional account system, API keys, paid subscriptions, or opt-in history), we will update this page and change the “Last Updated” date. Continuing to use IPIN.IO after an update means you accept the revised policy.
If you have questions or concerns, contact us at business@ipin.io.Operator information: 【IPIN ChainLink Limited】.
Summary: IPIN.IO is designed to be useful without becoming a data holder. We do not require registration and we do not retain your queries, uploads, results, or query logs. Some features may call third-party data sources and those providers may log requests independently.