Skip to content

Privacy Policy

Back to docs

Last updated: 2026-05-17

This privacy policy describes what data Zeeker MCP collects when you use the anonymous-tier MCP server at mcp.zeeker.sg. Zeeker is a read-only connector — it does not accept user registrations, store user data, or operate on behalf of callers beyond proxying requests to public Singapore legal datasets at data.zeeker.sg.

1. Data Collected

Each request to the MCP server generates one structured log line. The logged fields are exactly:

Field logged Description
request_id Random UUID generated per request; used to correlate log entries
tool Name of the MCP tool called (e.g. search, query_table)
database Database name requested (e.g. pdpc, zeeker-judgements)
table Table name requested (e.g. enforcement_decisions)
duration_ms Time in milliseconds from request receipt to response sent
status HTTP response status code (e.g. 200, 429, 500)
ip_prefix Truncated IP prefix — first three octets of the caller's IPv4 address (e.g. 203.0.113, the /24 network), or the /48 network base address for IPv6. The full IP address is never retained. Inputs that do not parse as a valid IP address are recorded as the fixed sentinel _invalid instead.
error_code Error code if the request failed (e.g. rate_limited, unknown_table)

What is NOT logged:

  • Filter values (the content of filters[*].value parameters)
  • Search query text (the query parameter to search)
  • Full IP addresses (only a truncated network prefix is retained — /24 for IPv4, /48 for IPv6)
  • URLs passed to fetch
  • Column projection lists
  • Any other user-supplied parameter values

This design implements the no-echo guarantee from the server's injection-resistance posture: user-supplied values are not present in any stored or transmitted log data.

2. Log Retention

Log lines are retained for 30 days on a rolling basis. After 30 days, log entries are deleted. No log data is archived beyond this window.

Retention is enforced by two mechanisms on the host: the container's log output is rotated by the Docker daemon at a 10 MB segment size with a maximum of 30 retained segments (a hard upper bound on disk usage), and a daily host-side prune deletes rotated segments whose modification time exceeds 30 days. No log shipping (rsyslog forwarding, SIEM agents, file backup) is configured on the host, so log data does not leave the server.

3. Third-Party Data Flow

All MCP tool calls are proxied to data.zeeker.sg (the upstream Datasette instance hosting the Singapore legal datasets). Requests are forwarded and responses are returned verbatim.

  • No data is sent to third parties for analytics, advertising, or tracking purposes.
  • No upstream request metadata is shared with any third party.
  • Responses from data.zeeker.sg to MCP tool calls (search results, table rows, fragment texts, fetched URLs) are not cached — each tool call is a fresh upstream request, and no retrieved dataset content is stored on the Zeeker server.
  • The upstream catalog at data.zeeker.sg/-/metadata.json (the list of databases, tables, and license strings — public, non-personal) is cached in memory with a 30-minute TTL so the server does not re-fetch the catalog on every tool call. This cache holds no user data and no upstream dataset content.

4. Cookies and Tracking

Zeeker MCP uses no cookies. There are no tracking pixels, analytics scripts, or user-tracking mechanisms of any kind. The server holds no user-identifying session state.

The MCP streamable-HTTP transport may emit a protocol-level mcp-session-id header during the connection handshake; this identifier is scoped to a single transport session, is not tied to any user identity or account, and is not retained after the connection ends.

5. Contact

For privacy inquiries, contact: privacy@zeeker.sg

6. Jurisdiction

This server operates under Singapore law. The upstream datasets at data.zeeker.sg are also hosted in Singapore under Singapore law. Any disputes regarding this privacy policy are subject to the jurisdiction of the courts of Singapore.