Privacy policy

The short version: this website keeps aggregate visit counts and nothing about you personally. What the CLI collects is your project’s engineering decisions, and they stay in your repository. The newsletter holds exactly one thing — the email address you gave it. The detail is below.

Who we are

inkentry is made by Usercise Ltd, which operates this website and is the data controller for anything described here. For questions or requests about your data, email privacy@inkentry.com.

This website

We measure this site with Vercel Analytics and Cloudflare Web Analytics: aggregate counts of visits, pages read and rough geography. Both work without cookies, without advertising identifiers and without following you to other sites, and neither gives us a profile of any individual visitor. There is no advertising here. Your theme choice is saved in your own browser’s storage and never sent to us.

The site is served by Vercel, whose infrastructure keeps standard request logs — things like IP address and browser type — used to operate the service and defend it against abuse. We do not use them to identify visitors.

The newsletter

If you subscribe to the inkentry newsletter, we hold the email address you gave us and use it to send you the newsletter — nothing else. The list is run on Kit (formerly ConvertKit), which processes addresses on our behalf. Every issue carries an unsubscribe link, and unsubscribing removes you from the list. We do not sell or share the list.

The CLI and the team server

inkentry runs on your machine, and what it collects is the thing it exists to keep: your project’s engineering decisions. That record lives in your repository, on your machine — not on our servers. The CLI sends us no telemetry, no usage statistics and no crash reports, and no account is needed to use it. The self-hosted team server is the same: it runs on your infrastructure, and we do not see it.

If you point harvest at a model provider, that traffic goes directly from your machine to the provider you configured. We are not in that path, and the provider’s own privacy terms apply to it.

inkentry cloud

The hosted tier is where personal data enters the product. If you use inkentry cloud, we hold your login details — the email address and credentials for your account, which the CLI also uses when it signs in on your behalf — and the decision log your team syncs to it. We use them to run the service and for nothing else: no selling, no advertising. The cloud app is measured with the same cookie-free analytics as this site.

Two processors sit behind an account. Sign-in is handled by WorkOS, our identity provider. Payments are handled by Stripe: card details go to Stripe and do not touch our servers. Pricing and availability are still to come, and this section will grow specifics — data location, retention, deletion — before general availability.

Your rights

If we hold personal data about you — for most visitors that is at most a newsletter address; for inkentry cloud users, their account details — you can ask what it is, have it corrected, or have it deleted by emailing privacy@inkentry.com. If you are in the UK or the EU, you also have the right to complain to your data-protection authority; in the UK that is the ICO.

Changes

When this policy changes, the date at the top changes with it, and material changes are noted in place rather than silently edited.