There are no accounts and no API keys, so there is very little to collect and nothing to link back to you.
Last updated 31 July 2026
Requests are served by Cloudflare Workers. As with any HTTP service, request metadata passes through in order to answer the call: the path and query, timestamp, response status, user agent, and the IP address of the caller. Cloudflare processes this as our infrastructure provider and retains aggregate analytics for a limited period.
We use that data to run the service — detecting abuse, enforcing rate limits, and measuring coverage and latency in aggregate.
The entity or query string you send is part of the request and appears in operational logs. Do not send personal or confidential information in a query — there is no reason to, since the service only looks up public encyclopedia entries.
We keep no application-level request logs of our own beyond what is needed to serve and cache the response. Cloudflare's edge logs and aggregate analytics are retained under their standard retention, typically days rather than months.
Responses are cached at Cloudflare's edge. Cached objects contain only public encyclopedia content — never anything specific to a caller.
Email you send us is stored in our mail provider so we can reply. We do not add you to a mailing list.
Business customers necessarily give us billing contact details and we keep usage records for invoicing. Those records are limited to volume and timing, not query content.
Because we hold no identifiers for anonymous API use, we usually cannot locate data "about" a given person — there is nothing to key on. If you have corresponded with us or hold a paid plan and want that information accessed, corrected or deleted, write to us and we will do it.
The service is not directed at children under 13 and we knowingly collect nothing from them.
Privacy questions: wikexa.com/contact.