Privacy Policy

Account information — your name, email address, and password (stored as a salted hash, never in plain text) when you register.

Organization and project data — names of organizations and projects you create, and who belongs to them.

Log data— whatever your applications send to Peeng's ingestion API using your API key: log messages, levels, timestamps, service names, status codes, stack traces, and any metadata you choose to attach. You control what your systems send us — avoid including secrets or sensitive personal data in log content you submit.

Usage and audit data — a record of actions taken in your organization (e.g. a member invited, an API key created or revoked, an alert changed), used for the audit log feature and basic operational logging.

Contact form submissions — the name, email, and message you provide are emailed to our team and are not stored in our database.

To operate the product: authenticate you, enforce access control within your organizations and projects, run the log search and dashboard features, evaluate alert thresholds you configure, and send transactional email (verification, password reset, team invites, alert notifications, and replies to your contact messages). We don't sell your data or use it for advertising.

The "Explain with AI" feature sends the content of the specific log entries you select — message, level, stack trace, and metadata — to a third-party AI provider (DeepSeek, with Gemini and OpenAI as fallbacks if the primary provider is unavailable) to generate a plain-language explanation. This only happens when you explicitly trigger it for a log or a selection of logs — it is not run automatically on all ingested data. Explanations are cached so the same log isn't re-sent to the AI provider on repeat requests.

We use a small number of providers to operate Peeng, each of which processes only the data necessary for its function:

• Resend — sends transactional email on our behalf (account verification, password resets, invites, alert notifications, contact form replies).
• DeepSeek, Gemini, and OpenAI — process log content you explicitly submit to the "Explain with AI" feature, as described above.
• Infrastructure providers — our database and application hosting run on standard cloud infrastructure used to operate the service.

Peeng uses a single essential cookie to keep you signed in — an httpOnly session cookie that isn't readable by JavaScript and isn't used for tracking or advertising. We don't use analytics or advertising cookies.

We retain your account, organization, and log data for as long as your account or project exists. We don't currently automatically delete old logs — if you need data removed sooner, email us and we'll handle it manually while we build self-service controls for this.

Passwords are hashed, never stored or logged in plain text. API keys are hashed and shown to you in full only once, at creation or regeneration. Your session's long-lived refresh token is kept in an httpOnly cookie inaccessible to page scripts; the short-lived access token used by the app lives in memory only and is never written to local storage.

You can update your name and password from your account settings at any time. To request a copy of your data, a correction, or deletion of your account, email hello@peeng.dev.

Peeng is a developer tool intended for business use and is not directed at children. We don't knowingly collect information from anyone under 16.

As Peeng moves from private beta toward general availability, we'll update this page and revise it with proper legal review. We'll note material changes here.