Who is responsible
Filipe Carboni Fim (@fcfim) develops and maintains Seen Context and Seen Usage Pulse. Seen Context is the brand; it is not a separate legal entity or publisher. For privacy questions, see Support.
This website
The public pages are static. They do not ask you to sign in, submit a form or provide Codex account data. We do not embed an analytics script, advertising tracker or third-party media player in these pages. The local light/dark control on the home page changes the current page only.
The website is hosted by Vercel. To deliver and protect pages, Vercel may process ordinary request data such as IP address, browser and request information under its own privacy notice. Links to GitHub and other external sites are governed by those sites' notices when you follow them.
Seen Usage Pulse
The 0.3.0 local candidate reads Codex quota and token-activity data through your locally configured, already authenticated Codex App Server. Usage data is processed locally and is not transmitted to Seen Context. Quota and activity snapshots are cached in memory and disappear when the plugin server stops. The configured Codex account may differ from the account visible in another Codex surface.
The dashboard theme may be stored locally in ui-preferences.json beside the plugin settings. The plugin settings contain a configured executable path, not Codex credentials. The plugin does not collect cookies, passwords, authentication tokens or a new login. The Codex executable and host continue to apply their own data handling.
Logs and sharing
Operational output is local to the host and may be retained by it. Detailed diagnostics are opt-in. Seen Context does not receive those logs automatically. The plugin has no remote analytics or relay for your usage data. If you invoke its public tool, returned quota and activity information is supplied to the Codex host/model for that request; dashboard-only state is supplied to the interface.
Your choices and requests
You can stop using the local plugin to stop its reads. You can reset the saved dashboard theme by stopping the plugin and removing ui-preferences.json from its installed directory. Do not remove Codex account files to reset a theme. A direct public contact for privacy requests has not been published yet; the Support page records the current status. That contact must be added before this notice is used for public plugin submission.