Who we are
IsoKron is operated by Stormhaven Enterprises LLC (“we”). We audit and build MCP servers. For anything on this page, write to hello@isokron.ai.
This website
- No accounts, no advertising. The site loads no advertising or cross-site tracking scripts. A theme choice (light, dark or system) is kept in your browser’s local storage if you pick one; we count which theme is picked, without cookies. Analytics cookies are set only if you accept them (see Analytics).
- Vercel Web Analytics. We count page views with Vercel Web Analytics. It uses no cookies. It records the page viewed, the referring site and any campaign (UTM) tags in the link, and the visitor’s country, browser, operating system and device type. It also counts four actions when they happen: a click on the payment link or the booking link, a sent request form and a newsletter sign-up, each with the kind of page and the offer, and nothing you typed.
- Hosting. Vercel hosts the site and keeps standard request logs (IP address, user agent, requested page, time) to run and secure the service. We do not combine them with anything else. Fonts are served from our own domain. If the site’s content security policy would block something on a page, your browser may report it to us; we log only the rule, the blocked site and the page’s path.
Analytics
We use PostHog (PostHog, Inc., US Cloud) to see which pages and articles lead to enquiries and where the site is hard to use. The browser sends analytics to our own domain (isokron.ai/rl), which passes it on to PostHog. When you first visit, a bar at the bottom of the page asks whether you accept analytics cookies. PostHog’s privacy policy applies to its processing.
Before you choose, and if you decline
- No analytics cookies, no identifier, no recordings. PostHog runs in its cookieless mode: it sets no cookies, stores no identifier in your browser and records no sessions. Only a decline itself is saved (see “Your choice”).
- What is counted: the pages you view and when you leave them (with how far you scrolled), visits to pages that do not exist, page-load performance (web vitals), the referring site and campaign tags, and named actions on the site:
- when an offer or package card, or an offer box in an article, comes into view;
- clicks on calls to action, offers, booking, payment, contact and outside links, links to files and feeds, and email links (with the address the link points to), recorded with the link’s text and its address, without the query string except the offer named in a link to the request form;
- how far down a page or an article you read, which sections of the main pages come into view, and which FAQ questions you open;
- when a page fails and shows its error page (the kind of error, never its message);
- copying a command, the theme you pick, and newsletter sign-up results;
- when the analytics bar is shown, and the choice you make in it;
- whether the request form was started, refused a field, was sent or failed. For the form we record field names and reason codes, never what you typed.
- With each event PostHog receives the page address, your browser, operating system, device type and IP address, and the country your request came from: a two-letter code our host, Vercel, reads from your IP address. Until you accept, no location finer than that country is used. To count visitors without a cookie, PostHog computes a hash of your IP address, browser details and a value that changes every day, so the same browser cannot be followed from one day to the next.
- Global Privacy Control and Do Not Track. If your browser sends either signal, we treat it as a decline: the bar is not shown and only the cookieless counting above applies.
- What our server counts. Our own server also sends PostHog three kinds of count, with nothing that identifies you and without your IP address: how each request-form post ended (delivered, refused or failed, with a reason code and the offer it named), content security policy reports from browsers (the rule, the blocked site and the page’s path), and errors in the server’s own code (the kind of error, its message with any email address removed, and the route).
If you accept
- An identifier. PostHog stores a random ID in a first-party cookie and in local storage (names starting with
ph_), so visits from the same browser are linked. PostHog’s cookie lasts up to a year. - More detail: clicks and other interactions anywhere on the page, click and scroll heatmaps, repeated or unresponsive clicks, JavaScript errors, and session recordings of how pages are used. In recordings every input and all text inside forms is hidden, and network requests are not recorded.
- How you first arrived. The site keeps the page you first landed on, the referring site, any campaign tags and the date in local storage (
isokron-first-touch), so a later request can say what brought you here. - Approximate location. PostHog also derives an approximate location (city and region) from your IP address.
- If you then send the request form, we link your analytics to an ID made from a one-way hash (SHA-256) of your email address, so we can see which pages led to the request. Your email address itself is not sent to PostHog.
Your choice
- Your choice is kept in local storage (
isokron-analytics-consent, and PostHog’s own record,isokron_ph_consent) so the bar does not come back. Change it at any time with the “Analytics choices” link in the footer. Declining after accepting deletes the stored first-visit details, resets PostHog’s ID and returns to cookieless counting. - Blocking cookies or scripts in your browser, or using a content blocker, also works; the site works the same without analytics.
- How long it is kept: PostHog keeps events and recordings for the default retention period of our PostHog plan; we have not set a custom period.
The request form
- What it collects: your name, work email, company site (optional), what you are asking for, whether you are building or adopting a server, the repository or server URL, a rough tool count, your main concern and, if you choose to say, how you heard about IsoKron. The form warns you never to include tokens, passwords or keys.
- How you reached the site: the form also sends, in hidden fields, the page you landed on (on this visit, or on your first visit if you accepted analytics), the referring site, any campaign tags, the page you sent it from and, if you accepted analytics, a link to the session recording. They go into the same email and nowhere else.
- How it is delivered: our server checks the fields and sends them to us by email through Resend, which acts as our email processor. We do not store submissions in a database, and our server logs record only whether delivery worked, not what you wrote.
- How long we keep it: the email stays in our mailbox for about 24 months, longer only if a client relationship needs it. Ask and we delete it sooner.
- If the form cannot send, it offers to open your own email app instead; that message goes from your mail provider straight to our mailbox.
Research emails
- What it collects: only your email address, when you sign up on a research page.
- Who processes it: Kit (kit.com) holds the list and sends the emails, under Kit’s privacy policy. Kit sends a confirmation email first, and you are not subscribed until you click the link in it.
- What we send: new research, about twice a month, and occasional news about IsoKron’s services. We never sell or share the list.
- Leaving: every email has an unsubscribe link. Unsubscribing stops all emails; ask and we delete your address from Kit entirely.
Payments
Card payments and invoices are processed by Stripe. Stripe collects your payment details directly; we never see or store card numbers. We receive your name, business name, email, the server you entered and the payment status, and keep them with our accounting records as the law requires. Stripe’s privacy policy applies to the payment itself.
Booking a call
Scoping calls are booked through Cal.com. When you book, Cal.com collects the details it asks for, and Cal.com’s privacy policy applies to that booking. We receive the booking details by email and keep them like form enquiries.
Audit engagements
- Test access only. We work on test tenants with tokens scoped to them. We never ask for production credentials or customer data.
- Tokens end with the engagement. At the end of an engagement we revoke or delete the tokens we were given, and we ask you to revoke them on your side too.
- Evidence. Reproduction scripts, logs, tool outputs and reports are kept for the period set in the engagement agreement, then deleted.
- AI model providers. Our audits are AI-assisted. Test data from your test tenant, tool outputs and session transcripts may be processed by the AI model providers we use, under their API terms. The engagement terms name those providers. This is one more reason testing never uses production data.
- Confidentiality. Reports are private by default. We publish nothing about an engagement without your written consent.
Our open-source tools
Our open-source tools run locally on your machine and send us nothing.
Your rights
You can ask what personal data we hold about you, ask for a copy, or ask us to correct or delete it, under GDPR, CCPA and similar laws where they apply. Write to hello@isokron.ai. We aim to confirm within two business days and act within thirty days.
Changes
If this page changes materially, the date at the top changes with it.