Novus AI Stats
Your AI Stats account, and getting your data back out
Novus AI Stats is the one app in the portfolio that is account-based by design, because it keeps a history of your own AI usage and has to know whose history it is. This is what the account holds, what the privacy defaults do, and how to take everything out or delete it.
Almost every app in this portfolio works fully signed out. AI Stats does not, and the reason is structural rather than a business decision: the product exists to show you a history of your own AI usage over time, and a history has to belong to somebody. There is nothing to show an anonymous visitor except a demonstration. Novus Restaurant is the other exception, for the same kind of reason — its public price data is open to everyone, while the operator workspace at /app is per-restaurant and signs you in to a tenant.
That makes the account worth understanding properly rather than clicking through. This tutorial covers what it stores, the settings that decide how much of it is kept, and — the part most people want and few products make easy — how to get the whole thing back out or remove it.
Contents
Two ways to finish
Set it up correctly
Profile, privacy defaults and notifications, before you import anything.
Get your data out
Full CSV and JSON export, and account deletion.
- 1
1. Understand why this one needs an account
The dashboard, sessions, projects, insights, the Activity Atlas, reports, recaps and achievements are all views over a history. Without an identity there is no history to view, which is why the demonstration data exists: it lets you see the shape of the product before deciding to import anything real.
Sign up at aistats.novusstreamsolutions.com with an email address and password, or with Google if that is set up on the deployment. It is free and there is no paid tier.
- The one account-based app in the roster, and it says so rather than implying otherwise.
- Demonstration data exists precisely so you can look before you import.
- 2
2. Set the privacy defaults before you import
Settings carries a Privacy defaults section, and it is worth visiting first rather than after. What it decides applies to the imports that follow, and changing a default later does not retroactively change what an earlier import kept.
The same page holds your profile and the analytics calendar, which sets the period the dashboard summarises, and notification preferences. Appearance and accessibility choices live there too.
- Privacy defaults apply going forward, not backwards. Set them first.
- The analytics calendar decides what "this period" means everywhere on the dashboard.
- 3
3. Connect sources, and check what was actually accepted
Connected sources lists what you have imported. Read it after an import rather than assuming success: the provider registry is strict about file shapes, and a format that is not accepted is refused rather than parsed on a guess.
Cursor is the clearest example. A legacy ItemTable SQLite snapshot with a known schema is accepted; the current cursorDiskKV database shape is not accepted at all, because it splits headers from bubble bodies and no rights-cleared structural fixture exists for it yet. Exported Markdown works either way.
- Seven supported sources: ChatGPT, Claude, Gemini, Claude Code, Codex CLI/Desktop, Gemini CLI and Cursor.
- An unrecognised shape fails closed. That is the product being careful, not broken.
- 4
4. Take the whole thing out whenever you want
Your data controls offers two full exports: every normalized session as CSV, and the complete record as JSON. Neither is a sample and neither is capped — the page states that exports include every normalized session with no ten-thousand-row limit.
This matters more than it sounds for a product like this. An analytics tool that makes its own history hard to leave with is a lock-in mechanism wearing a dashboard. Doing a full export once, early, tells you what you would be able to take with you before you have accumulated a year of it.
- Download all sessions as CSV, or the complete record as JSON.
- No row cap on either export.
- 5
5. Manage sign-in, or close the account
Settings has a Security page for sign-in methods and connected accounts — useful if you started with a password and later want to attach Google, or the reverse.
Delete account is on the data controls page, and it does what it says. Export first if you want a copy: deletion is meant to be final rather than a soft hide.
- Sign-in methods and connected accounts live under Settings, Security.
- Export before deleting. There is no undo behind a delete.
The test to apply to any analytics product
Ask two questions early: can I get all of it out in a format something else can read, and can I make it stop? AI Stats answers both on one page — uncapped CSV and JSON exports beside account deletion — and that is the right place for them to be. A product that buries the export, caps it at a round number, or offers deletion only by email is telling you something about how it regards the data, and it is worth noticing before you feed it a year of your working history.
Frequently asked questions
Quick answers to common questions about this topic.
Why can I not use AI Stats without an account?
Because it shows a history of your own AI usage over time, and a history needs an owner. Almost every app in the Novus portfolio works fully signed out; this one and Novus Restaurant’s operator workspace are the two deliberate exceptions, and demonstration data exists so you can see the product before importing anything.
Is there a limit on the export?
No. Both the CSV and the JSON export include every normalized session with no row cap.
Does changing a privacy default fix an earlier import?
No. Defaults apply to imports made after the change, which is why setting them before your first import is worth the two minutes.
Why was my Cursor database rejected?
Almost certainly because it is the current cursorDiskKV shape rather than the legacy ItemTable one. That format is not accepted yet and is refused rather than parsed on a guess. Exported Markdown is the reliable route.
Related workflow
Turn your AI work into a report you can actually show someone
Measure what you built with AI assistants over a period, then package the numbers into a document with the caveats attached.
- Import your history and read the quality labelsNovus AI Stats: Token and session figures differ in how reliably each provider reports them; the labels say which numbers can carry an argument and which cannot.
- Assemble and protect the reportNovus PDF Studio: Merge the exported pages into one document and apply a password before it leaves your device.
Related troubleshooting
Was this page helpful?
Your answer stays in this browser, it is not sent anywhere and no account or cookie is involved.