Privacy

API, MCP, maps and llms.txt

For each request to the API, the MCP server, the map geometry or llms.txt, we record:

• the time, method, path and route, the response status and how long it took;
• the API key and account that made it, if any;
• whether it was refused, for a missing or invalid key or for the daily limit;
• the user agent, and the kind of client we read from it, such as the CLI, an MCP client, a browser or a crawler;
• the CLI command's name, such as "agencies get", which the CLI leaves out when you set DO_NOT_TRACK=1;
• the id of a jurisdiction looked up by id;
• your network, not your address: the first three parts of an IPv4 address (a /24) or the first three groups of an IPv6 address (a /48).

We never record query strings, so an address or coordinates you send to juricode are not kept in this log. We never record a command's arguments.

How long we keep it

Each request is kept for 90 days, then deleted. Before that, we total each day by source, client, route, command, response status, account and API key, with counts and response times. Those daily totals carry no network or user agent, and we keep them.

Web pages

We count page views on our own server: one count per day, page type and kind of client. Counting uses no cookie and no script, and it keeps no network, user agent or account. The site uses no third-party analytics. The site's own session cookie keeps you signed in and protects forms, and it is used for nothing else.

Juricode searches

When you search an address with juricode, we record the address, where it was found and which jurisdictions it falls in, so we can see where coverage is missing. The record has no network or user agent. It is tied to your account only when you are signed in, so you can see your own searches.