Privacy

LLMPing is built to minimize sensitive data collection.

The current MVP is a frontend-first diagnostic toolkit. It provides official status links, static troubleshooting guidance, cURL generation, and local UI interactions without user accounts, saved monitors, or stored API keys.

What we do not collect

Secrets and payloads stay out of LLMPing storage.

API keys or bearer tokens.
Prompt content or provider response content.
Saved monitors, because this phase has no monitoring backend.
User accounts or account identifiers.
API keys in localStorage, query parameters, or analytics events.

Current data behavior

Tool usage is local unless you choose to contact us.

Provider pages, error explanations, cURL commands, and diagnostic output are generated from static configuration in the app. Waitlist forms in this MVP record intent in the browser session only unless a third-party form or backend integration is explicitly added.

The analytics wrapper currently logs events to the browser console so future product analytics can be added deliberately. It must not include API keys, pasted error payloads, prompts, or generated command secrets.

Limitations

Browser diagnostics are not production monitoring.

Browser-side checks may fail because of CORS, preflight headers, corporate proxies, local network rules, browser extensions, or provider policies. Official provider status may not reflect your specific account, region, quota, model access, or runtime. For reliable alerting and uptime history, a future server-side monitoring product would be required.

Privacy questions: contact@llmping.dev.