Privacy and lookup history

We store account details, hashed browser-session tokens and hashed API-key secrets to authenticate your account. API usage counters support quotas and billing. API requests, public lookup pages and upload-tool inputs are not added to account lookup history.

Optional manual lookup history

History is disabled by default. If you enable it, lookups you make on Dashboard → Lookup history save the target, a response summary and the lookup timestamp. You can star records and add labels. No API-key secret is stored in history.

Choose 7, 30 or 90 days. Expired records are excluded from reads and exports, and deleted when you next visit history or when the cleanup command runs. Shortening retention immediately expires older records; increasing retention does not extend existing records until you look them up again. Stars follow the same expiry rules. Each account retains at most 500 distinct targets; oldest unstarred records are removed first, followed by oldest starred records if necessary.

Targets, response summaries and labels use authenticated AES-256-GCM encryption with a server-held key. Account IDs, timestamps, star flags and a keyed target index remain visible in the database. The server decrypts records for your authenticated requests; this is not end-to-end encryption. Access to both the server key and database can reveal their contents.

Search and filtering run in your browser over your own records. Private pages and exports use no-store cache headers. Downloaded exports remain on your device until you delete them.

Deletion

Delete individual records, purge all history, or set retention to Off to disable collection and delete all active records. Deleting your account also deletes its history. Deletion removes records from the live database; copies in database backups follow the database operator’s backup lifecycle. Operators must publish their backup retention separately. We cannot remove copies you have downloaded.

Contact support@ip-api.dev for account privacy requests.