dlogify is built to keep as little of your log data as it can, for as short a time as it can. This policy is part of the Terms of Service and the Privacy Policy of Pimzee LLC.

dlogify only processes the events that your applications or collectors send to it with an API key. It never connects to your servers, databases, source code, cloud accounts or internal services, and it cannot read anything you do not send. An API key can only send events; it cannot read data or manage your account.

To let you replay what led to a ticket, we keep a history of your redacted log lines. An admin can turn it off for any project:

• Log history: the redacted lines that reach our engine, of every level you send. Each line holds its time, level, service, environment, message and trace ID, and its message is cut at 2 KiB. Stack traces and attributes are not part of it. Lines wait in an internal queue for at most 7 days, usually minutes, and are then stored on Cloudflare R2 in the United States.
• If you turn it off for a project, new lines stop being stored, and lines already stored are deleted when their retention ends.
• Deleting a project or an organization removes its stored lines within 30 days.
• INFO events are also counted per time window, with at most 3 redacted example lines per message pattern.
• The last 50 lines of each stream are also held in memory, to give context to an error, and are lost when the service restarts.
• Of ERROR and WARN events, we keep at most 10 redacted samples per error group, each with up to 30 redacted surrounding lines.
• Group history: counts of occurrences per environment and hour, and the releases a group was seen on. It holds no log content.
• Live tail displays redacted log lines in the dashboard as they arrive, and keeps nothing of its own.
• Passwords and API keys are stored only as hashes. Webhook signing secrets are stored encrypted.

Before an event is stored or sent to any provider, its message, stack trace and attributes are redacted. The following values are replaced by a marker such as <email> or <secret>:

• email addresses;
• payment card numbers;
• IP addresses;
• JSON Web Tokens, bearer tokens and keys with well-known prefixes, such as Stripe, GitHub, GitLab, Slack, AWS and Google keys;
• values that follow password, secret, token, api_key or access_key;
• the whole value of attributes named like password, secret, token, authorization, cookie, api_key or session.

Redaction is automated and works by recognizing patterns. It is designed to remove personal and secret values, but it cannot recognize every format, such as names, postal addresses or secrets with an unknown shape. Do not log passwords, secrets, payment card data, health information or other sensitive data: you are responsible for what your applications send.

Retention is applied automatically every hour, using the current plan of each organization. After a move to a plan with shorter retention, older data is deleted at the next run.

To classify errors and write tickets and summaries, we send redacted excerpts to the AI providers listed in the Privacy Policy, never full log streams. Requests are made with settings that disable training on the data and, where the provider offers it, storage of the request. What the providers retain is governed by their own terms.

An owner can ask us to delete a project, an organization or an account by writing to [email protected] from the owner's email address. We delete the data within 30 days of the request. To stop sending data at once, revoke the project's API keys in the dashboard.

Questions about this policy: Pimzee LLC, [email protected].