Read only with permission
Ganox reads Claude and Codex history only after you authorize it. The local app can find project signals before it sends usage data.
Your work stays private.
Ganox keeps product data separate from marketing data. Advertising systems never receive project names, plan names, local file paths, session IDs, prompts, responses, or imported history.
Usage data by default
The project report stores usage, cost source, work labels, match confidence, and the reason for each match. Saving raw prompts and responses is a separate setting.
Corrections keep history
A correction adds a new choice and a reason. It does not delete the original usage record or earlier match.
Planning connections belong to your account
You authorize Regrok for one Ganox account. Ganox gives the local app only the plan details needed to find a match.
Cost sources stay separate
Ganox keeps provider bills, subscription shares, API price estimates, and unknown costs separate in the app and exports.
Marketing data is limited
Ganox records how a visitor found the site, important signup steps, the selected plan, and payment totals. It does not add product data.
Common questions
Does Ganox send project or session data to ad platforms?
No. Marketing records the campaign that brought someone to the site and the signup steps they complete. The server rejects project, plan, session, prompt, response, path, file, and matching details.
Can a browser mark its own payment as complete?
No. Ganox waits for a signed confirmation from the payment provider before it activates paid access.
What does Ganox read from Regrok?
Plan IDs, names, web addresses, visibility, and current revision IDs. Ganox does not put the Regrok access token, plan text, prompts, responses, or raw sessions in the matching catalog.
Can Ganox work without Regrok?
Yes. Ganox can build the project report from usage and session details alone. Regrok adds optional plan and revision details.