Privacy policy.

Overview

Crunchy Codes projects are designed to avoid collecting personal information unless clearly stated in the relevant project documentation.

Project data

Tools may store local settings or workspace data when needed for functionality. This data stays on your device unless a specific project states otherwise.

Telemetry

Crunchy Codes projects do not collect telemetry by default. If a future project, including an editor extension, uses telemetry or connects to an external service, its documentation will describe what is collected and how it is used.

Contact

For privacy questions, use the support details provided on the relevant project repository or documentation.

Memoryium

Matching Pairs and Glance run in your browser without an account, analytics, cookies, or saved game results. Answers and round scores stay in the open page and are cleared when you reload or leave it. The games do not send answers or results to a server. The website's hosting infrastructure may process normal page-request metadata.

Token Trail hosted demo

When you generate a Token Trail trace, the page sends your prompt and generation settings over HTTPS to a public Hugging Face Space. The Token Trail application processes the prompt in memory to return token probabilities. It does not save prompts or responses or collect application telemetry. Hugging Face and network infrastructure may handle request metadata under their own policies. Do not enter sensitive information in the demo.

Noteboard

Noteboard stores Boards and settings locally. Its synthetic demo and loopback-only Ollama mode do not need a hosted inference service. When you choose ChatGPT plan usage, the complete request context and any attached files are sent to OpenAI with storage disabled for the request. Enabling web search also permits the hosted search tool and records returned citations and source URLs in the Board. OpenAI and network infrastructure may process request data under the policies applying to your account and service.

Account credentials stay separate from Boards and exports. On macOS, a signed build protects them with Touch ID or the system password via the data protection Keychain; other supported platforms use secure operating-system storage and refuse insecure fallbacks. Local rotating diagnostic logs are never uploaded automatically and exclude prompts, responses, attached files, credentials, account identities, raw errors and URLs.

Codex Local Meter tools

The Codex Local Meter VS Code extension and native macOS app read local Codex session files to show derived usage estimates. By default, each tool processes that data only on the device. Optional live account telemetry is disabled by default; when enabled, the tool uses the locally installed Codex App Server and existing Codex authentication to request current account rate-limit metadata. This may contact Codex services, but does not start a model turn or send session content. Neither tool collects analytics, modifies Codex files, or displays prompts, responses, code, or tool output.