Privacy and cookies

The MCP server

Requests to /mcp are answered and forgotten: we don't store the arguments you send or the results. For your dashboard and our own statistics we record, per account, which tool was called, whether it succeeded, how long it took, how many credits it used, and the client name your MCP client reports when it connects (for example “claude-ai” or “cursor”).

Your account and API keys

An account needs only your e-mail address. We store it, your plan, your monthly credit balance and your call counts per tool.

API keys are stored only as a one-way hash, with a name you choose, the first and last characters for recognition, and when the key was created and last used. When you connect an app with OAuth, we store which app it is and when you connected it, until you disconnect it.

Payments

Paid plans are sold by Polar (polar.sh), the merchant of record, which handles card details, VAT and invoices under its own privacy policy. We receive the subscription's status, product and renewal date, linked to your account, and never see your card.

What we measure

We count page views, copies of the connection settings, live example runs, source requests, reports, and calls to the MCP server and the playground. This happens on our own server, not at Google or anyone else. For visitors who aren't signed in, we count unique visitors per week with a one-way hash of the week number, IP address and browser type, made with a secret key. The hash changes every week, so visits in different weeks can't be linked, and the IP address itself is never stored. Measurements are deleted after 13 months.

For address reports we store which kommune the address is in and how long the report took, not who looked it up.

Cookies

• dv_kilde: remembers that your visit started on the front page, and the campaign name from the link (utm_source) if there was one. It holds no identifier and is only used to compare our own pages. Kept for 180 days.
• dv_lang: remembers whether you chose English or Danish. Kept for a year.
• Sign-in cookie: only if you sign in. It keeps you signed in.
• OAuth consent cookie: set for a few minutes while you approve an app, so the approval can only be completed in your browser.

We use no cookies for statistics or marketing, which is why there is no cookie banner.

Source requests

When you request a data source we store what you asked for, what you'd use it for, and your e-mail if you gave one. We only use the e-mail to reply about the request, and delete it when you ask us to.

The playground

Your conversations are stored so you can come back to them, and are visible only to you; you can delete one at any time. If you start a conversation from an address report, the address and the report's main figures are stored with it so the assistant knows them. If you rate an answer, we store the rating with a short excerpt of the answer and your user id, to improve the answers.