nock
Home About Get started Docs

Privacy policy

nock runs on your computer, and what it records about your project stays in your repository. We, Parallel Labs in Barcelona, receive only what you choose to send: a weekly usage report, if you said yes when nock asked; a reflection round's summary, when you confirm one; and a report you write with nock report, with nock's version and your platform.

The usage report is counts and categories under a random project id: never code, file paths, file or tool names, prompts, or what your decisions say. nock usage shows what the next one would carry, and share = false in .nock/config.toml stops them. A summary or a report holds what you saw before sending it, so read it first.

The website sets no cookies, runs no analytics and loads nothing from other sites; GitHub, which hosts it, sees your IP address. It keeps one thing in your browser, and only if you turn this summary off: that choice.

Our server is in the EU (Scaleway, France). It stores reports and summaries without your IP address for up to 12 months, and its access logs, with IP addresses, for up to 30 days. nock's agents run under your own coding agent's account: what they read goes to its provider, not to us.

For a copy of your data, a correction or deletion, write to support@logika.host with your project's id from .nock/project.json; we answer within a month. You can complain to the Spanish data protection authority (AEPD) or your own.

In short. The full text is the one that applies: turn TL;DR off to read it.

Last updated: 4 November 2026

This policy explains what personal data reaches nock's makers when you visit nock.dev or use nock, the open-source tool. nock is made by Parallel Labs, S.L. ("we", "us"), a Spanish company, NIF B05585526, Calle Calabria 171, 5º-3ª, 08015 Barcelona, Spain, which is the controller for what this policy covers. Contact: support@logika.host. It follows the EU General Data Protection Regulation (GDPR) and Spain's Organic Law 3/2018 (LOPDGDD).

1. In short

nock runs on your computer, and what it records about your project stays there, in your repository. We receive three things, and only these:

  • A weekly usage report, only if you said yes when nock asked: counts and categories only, under a random project id.

  • A reflection round's summary, only when you choose to send one, after seeing exactly what would be sent.

  • A report you write to us, only when you send one with nock report after seeing exactly what would be sent: your text, nock's version and your platform, which we store with the time it arrived, and no IP address, for up to 12 months.

The website sets no cookies and runs no analytics.

2. The website

nock.dev is a static site. It sets no cookies, runs no analytics and loads nothing from other sites. It keeps one thing in your browser's local storage, and only if you turn off the plain-words summary on these legal pages: that choice, so the pages remember it. It never leaves your browser. It is hosted by GitHub, Inc. (GitHub Pages) in the United States, which receives your IP address and browser details when you open it, as part of delivering it, and keeps its own server logs as a separate controller under its own privacy statement. GitHub is certified under the EU–US Data Privacy Framework.

3. The usage report

The first time you engage with nock on a machine (your first reflection round, opening nock studio, or your first review of or note on a decision), nock asks once whether to share a weekly usage report. Nothing is sent before you answer, and your choice is written to share in .nock/config.toml; change it there at any time (or per machine in .nock/local/config.toml). While sharing is on, nock sends a usage report from your machine once a week to api.nock.dev.

A report holds:

  • nock's version, Python's version and your platform (darwin, linux);

  • whether reminders and the consultant are on, and whether the project uses Logika;

  • counts of how nock was used over the week: sessions, tool calls, tokens and their cost, commands, decisions and reflection rounds;

  • the project's identifier: a random UUID, made when the first report is sent and kept in .nock/project.json, derived from nothing about you or the project.

It never holds code, file paths, file or tool names, prompts, command arguments, what your decisions say, or anything else written in your project. Reports carry no name, email or address, but each project's reports share one random identifier, so we treat them as pseudonymous rather than calling them anonymous. nock usage shows exactly what the next report would carry.

We use reports to learn how nock is used and to improve it, on the basis of your consent (GDPR Art. 6(1)(a)). You can withdraw it at any time by setting share = false; nothing further is sent, and withdrawal does not affect what was lawfully sent before. You can also ask us to delete your project's earlier reports, quoting the id from .nock/project.json.

4. Reflection summaries

A reflection round writes a summary of how nock is doing in your project. It leaves your machine only if you run nock share, review the text it shows you, and confirm. Before showing it, nock has an agent remove anything that could identify the project, its people, partners or customers. Read it before you confirm: if it still contains personal data, that data reaches us. We use summaries to improve nock, on the basis of your consent given by confirming, and never publish them.

5. What reaches our server, and what it keeps

api.nock.dev stores each report or summary with the time it arrived and the project id — no IP address and no request headers are stored with it. Like any server, ours sees your IP address when a request arrives; it uses it only to limit how often one address may send, and keeps it in its ordinary access logs for up to 30 days, for security. The server is in the European Union (Scaleway, France).

WhatKept for
Usage reportsup to 12 months
Reflection summariesup to 12 months
Server access logsup to 30 days

6. What nock does on your machine

nock's agents run under your own Claude Code (or other coding agent) account, on your machine, under your own agreement with its provider. What they read and send goes to that provider, not to us. When nock works with Logika (nock reflect logika), it reads your Logika project through your own logika CLI; that is covered by Logika's privacy policy, and nothing of it reaches nock's makers beyond the usage report above.

7. Your rights

You may ask us for access to, correction or erasure of personal data we hold about you, to restrict or object to its processing, or to receive it in a portable form, by writing to support@logika.host. Reports carry no identifier we can link to you ourselves, so to find yours, include your project's id from .nock/project.json. We answer within a month. You may complain to the Spanish data protection authority (AEPD, aepd.es) or the authority where you live.

8. Changes

We will say on this page when it changes, and update the date above. nock is not directed at children.

nock: open source, MIT licensed. Made for Claude Code by Parallel Labs. PrivacyTermsGitHub