Privacy Policy
How TraceIP collects, uses, and protects data.
Last updated: July 11, 2026. This policy explains how TraceIP handles account data, lookup activity, API usage, and support information.
1. Overview
TraceIP provides IP validation, geolocation, network intelligence, API access, reports, and dashboard tools. We design the platform to collect only the information needed to operate the service, secure user accounts, maintain usage limits, and improve reliability.
2. Information we collect
When you sign in with Google, we may collect your name, email address, Google account identifier, profile picture, login status, and authentication metadata needed to create or update your TraceIP account.
When you use TraceIP, we may collect IP lookup inputs, lookup results, API key metadata, API request timestamps, request status, usage counts, risk labels, country and ASN summaries, export activity, and operational logs.
When you contact support, we may collect your name, email address, selected topic, message content, and any troubleshooting details you provide.
3. IP lookup data
IP addresses submitted through website lookup and production API endpoints are processed to validate the address, classify it, enrich it with public IP intelligence data, and display or return the result. Production API lookups may be stored in your account history for dashboard usage, reporting, quota tracking, and abuse prevention.
Website lookup requests use authenticated session protection and request validation. Website lookup usage is separate from production API usage stats unless explicitly stated in the product.
4. Google authentication
TraceIP uses Google sign-in for authentication. The frontend receives a Google credential and sends it to the backend for verification. After successful verification, TraceIP issues its own session token for future communication with the backend.
We do not ask for your Google password. Google controls the sign-in experience and may process data under Google's own privacy policies.
5. API keys and security data
API keys are used to authenticate production integrations. We store API key records, names, descriptions, environment labels, expiry dates, status, last-used timestamps, and related history events. Full API key secrets are shown only when created or rotated; you should store them securely.
Security signals such as proxy, VPN, Tor, blacklist, abuse, and risk labels may be stored with lookup records when available. These signals are provided for operational context and should not be used as the only basis for decisions that materially affect a person.
6. Cookies, analytics, and tracking
TraceIP may use cookies, local storage, or similar browser storage to keep users signed in, remember interface preferences, support security controls, and maintain application state.
The site may use Google Analytics and Google Tag Manager to understand page usage, performance, and conversion behavior. These tools may collect device, browser, page view, referrer, and interaction information according to their configuration.
7. How we use information
We use collected information to provide IP intelligence, authenticate users, maintain accounts, enforce package limits, generate dashboard statistics, improve reliability, detect misuse, respond to support requests, and maintain legal and operational records.
8. Data sharing
We do not sell personal information. We may share information with infrastructure, analytics, authentication, hosting, database, email, security, and support providers when needed to operate TraceIP. We may also disclose information if required by law, to protect the service, or to investigate abuse or security incidents.
9. Data retention
We keep account information while your account is active. Lookup history, API usage records, login records, API key history, support messages, and operational logs may be retained for as long as needed for product functionality, auditing, security, billing, dispute resolution, and legal compliance.
Deleted records may remain in backups or logs for a limited period before they are removed through normal retention cycles.
10. Your choices
You can stop using TraceIP at any time, rotate or delete API keys, and contact support to request help with account data. Some information may need to be retained where required for security, billing, legal, or abuse-prevention reasons.
11. Security
TraceIP uses technical and operational safeguards intended to protect account access, API keys, and service data. No internet service can guarantee absolute security, so you are responsible for protecting your account, browser session, and API keys.
12. International use
TraceIP may be operated using infrastructure or service providers in different regions. By using the service, you understand that information may be processed where TraceIP or its providers operate.
13. Children
TraceIP is designed for developers, cybersecurity analysts, network administrators, IT teams, SaaS companies, and general technical users. It is not directed to children.
14. Changes to this policy
We may update this Privacy Policy as the product, legal requirements, or operating practices change. The updated version will be posted on this page with a revised date.
15. Contact
For privacy questions, contact TraceIP support through the support page or by email at [email protected].