What this website stores, what the tourkit packages store on your users' devices, and what the optional AI feature sends. Last updated 24 August 2026.
There is no account system, no newsletter and no form that collects anything, so there is nothing for you to submit. The typefaces are downloaded at build time and served from this domain, so viewing a page makes no request to a font provider.
The site is hosted on Vercel, which keeps standard server access logs, including IP address and user agent, for operational purposes. Those logs are Vercel's, governed by their privacy policy, and are not read, exported or combined with anything else by this project.
The interactive demo on this site runs entirely in your browser. Its state lives in your own localStorage, under keys beginning tour: for tour progress and tourkit:hint: for dismissed hints. It never leaves the device, the demo panel has a control that clears it, and it goes with the rest of your site data whenever you clear that.
This site runs no analytics, sets no cookies and embeds no tracking pixels or third-party scripts.
The library collects nothing and sends nothing. There is no telemetry, no usage reporting, no license check and no phone-home of any kind. tourkit operates no servers.
@tourkit/react writes one record per tour to localStorage in your application, holding the tour id, its version, the step the user reached and a timestamp. That is what lets a tour resume where someone left it and not restart forever. It stays on the user's device. On React Native nothing is stored at all unless you pass a storage adapter. You control the adapter, so you decide where the record lives and when it is cleared.
@tourkit/ai is optional and off unless you install and wire it. When you do, the model call happens on your own backend with your own API key. The question a user typed and the list of target ids currently on screen go from your server to whichever model provider you configured, under that provider's terms. Nothing is routed through tourkit infrastructure, because there is none. The client half of the package contains no key handling at all.
tourkit record starts a server on your own machine, by default bound to 127.0.0.1, and writes a tour file into your repository. Nothing is uploaded. Passing --host binds every network interface so a phone can reach it, which also means anyone on that network can; the CLI reference says so at the point where you would use it.
This page is versioned in the site's public repository, so its history is the change log. Questions go to the issue tracker.