Privacy
Krites is run by Quinn Lott, a sole proprietor doing business as Krites, who is the controller of the information described here. Contact: hello@krites.dev.
The short version: this site sets no cookies, counts visits with Cloudflare's analytics, which Cloudflare says uses no cookies, keeps three daily counts of its own, and loads everything else from krites.dev itself. The plugin sends me nothing unless you opt in to a weekly ping.
This website
krites.dev sets no cookies and has no ads or tracking pixels, and every file it loads, fonts included, comes from krites.dev, with one exception: Cloudflare Web Analytics adds a small script from static.cloudflareinsights.com that counts visits. For each page view it records the page, the referring site, your country, device type, browser, operating system, and how long the page took to load; Cloudflare says it uses no cookies or local storage and does not fingerprint visitors, and I see only totals. Cloudflare hosts the site. Like any web host, it processes your IP address and request details to deliver pages and to protect the site from abuse, and it asks your browser to report pages that fail to load (Network Error Logging) so it can keep the site reachable; those reports go to Cloudflare, not to me. See Cloudflare's privacy policy. Its dashboard shows me request statistics and security events, which can include IP addresses; I use them only to keep the site running and safe.
The home page also keeps three counts of its own: page views, times at least half of the Pro section was on screen, and clicks on the founding-seat link, each at most once per page load. Your browser sends only the event's name to krites.dev/count. I store that name and the day it arrived (UTC), added to a daily total, and nothing else: no IP address, request headers, cookies, or identifiers. If your browser sends Global Privacy Control, the page sends none of them.
I do not track visitors across other sites. Global Privacy Control turns off the three counts above; Cloudflare's analytics runs either way, and Do Not Track changes nothing. Apart from Cloudflare, as my host and through its analytics as described above, no other party collects information about your activity through krites.dev.
The plugin
- The plugin sends your code, diffs, check output, prompts, and receipts nowhere. Receipts are written into your repository, and the signing key stays on your machine. The gate's output goes to your coding agent, which handles it, like the rest of your session, under its own vendor's terms.
- Telemetry is off until you answer yes. A yes allows one ping at most once a week with no name or account in it: a random install ID, the plugin version, your operating system, and a timestamp. The install ID stays the same from ping to ping, so the ping is pseudonymous rather than anonymous.
/krites:telemetry-offstops it. - Plugin 0.1.0 has no endpoint, so it does not ask and sends nothing. From 0.1.1, a yes sends the ping to krites.dev/ping, which I run on Cloudflare. I store the install ID, plugin version, operating system, timestamp, and the day it arrived; I never store your IP address or request headers, and I delete pings after 12 months. To stop abuse, Cloudflare counts the requests sent to krites.dev/ping and krites.dev/count per IP address per Cloudflare data center, and when an address sends more than 20 in 10 seconds, refuses its requests to those two paths for 10 seconds. On top of that, krites.dev/ping and krites.dev/count each use Cloudflare's rate limiter, which refuses an address that sends more than about 20 requests to that path in 60 seconds. These counts are kept by Cloudflare, keyed by your IP address, not by me. If you set
KRITES_PING_ENDPOINTyourself, pings go to your endpoint, not to me. - Installing the plugin downloads it from GitHub, which handles that request under its own privacy statement.
Founding seats
Checkout runs on Stripe's pages, and your full card number never reaches me: Stripe shows me the card brand, its last four digits, its expiry date, and the country that issued it, and, for fraud checks, the IP address and rough location (city or region) the payment came from. Stripe's checkout page uses its own cookies and device data to detect fraud across the businesses that use Stripe; see Stripe's privacy policy. I receive your name, email address, billing country and postal code, what you paid, and the ship-by date you pick. I use them to deliver your seat and license key, email you when Pro ships and before renewal, handle refunds, and keep the records tax law requires. To buy a seat you must give your name, email address, and payment details; without them I cannot sell one.
Pro is not out yet. Before it ships, this page will cover what it adds, such as the license check it makes online every 14 days.
Email and calls
If you email hello@krites.dev, I keep the thread so I can reply and follow up. If you book a call, Cal.com handles the booking with your name, email address, chosen time, your answers to three questions (which coding agents you use daily, whether you pay for more than one AI coding subscription, and where you found Krites), any additional notes you add, the email addresses of any guests you add, and your choice of Google Meet or Cal Video for the call; see Cal.com's privacy policy. Calls are not recorded.
Who else sees it, where, and for how long
I share personal information only with the providers named on this page and the email service that hosts hello@krites.dev, which handle it for me, and with authorities or advisers when the law requires it. If you choose Google Meet for a call, Google processes the call; see Google's privacy policy. I am in the United States, the services named here keep your information there or where they operate, and Cloudflare serves each visit from a data center near you; data protection law in those places may differ from yours. I keep seat and payment records for 7 years after the sale, email threads and bookings for 2 years after the last contact with you, and telemetry pings for 12 months.
What I never do
I do not sell personal information, share it for advertising, or combine it with data about you from elsewhere, and I make no decisions about you by automated means alone. Nevada residents: I do not sell covered information, but you may send a verified request not to sell it to hello@krites.dev, and I will answer within 60 days.
Your rights
Email hello@krites.dev to get a copy of what I hold about you, to correct or delete it, to restrict or object to a use of it, or to receive it in a portable format for yourself or someone you name. You can withdraw consent to telemetry at any time with /krites:telemetry-off; pings already sent stay lawful. I answer within one month.
I rely on my contract with you for seat purchases, on your consent for telemetry, and on my legitimate interests for the rest: running and protecting the site, counting visits, answering email and bookings, screening payments for fraud, and keeping the records tax law requires. To complain, email hello@krites.dev with "Complaint" in the subject; I acknowledge it within 30 days. You can also complain to the data protection authority where you live; in the UK, that is the ICO (ico.org.uk).
Children
Krites is not directed at children under 16, and I do not knowingly collect their information. If I learn I have, I delete it.
Changes
If this page changes, the date at the top changes with it. If a change affects a seat you hold, I will email you first.