Each pricing fetch includes a random install id created on your machine. It is not tied to an account. This site stores that id with the first fetch time, the latest fetch time, and how many times pricing was fetched.
Request metadata and token counts stay in local extension storage.
Cursor usage API uses your existing Cursor sign-in to read dashboard data — cached locally only.