Privacy

What we process

Two different things, and the distinction matters. Account data is what you give us to have an account: your email address, your name if you provide one, your projects, your team members, and billing records. Log data is what your application sends to our ingest endpoint: log lines, stack traces, release and environment tags, and whatever context your code attaches to them.

We decide what account data we need. You decide what log data reaches us.

How long we keep it

Log data is deleted when its retention window expires. The window depends on your plan and is stated on the pricing page. Account and billing records outlive the logs, because tax and accounting rules require it. Deleting a project deletes its log data; closing your account deletes the rest, except records we are obliged to retain.

What we do not do

We do not sell personal data. We do not use your log data to train models. We do not read your logs except when you ask us to help with a specific problem, or where we must to keep the service running or to meet a legal obligation.

Your rights

You can export your data, correct it, or have it erased. Most of this you can do yourself from settings without asking us. For anything you cannot, write to privacy@loghq.org and we will handle it.

Keeping logs clean

Logs pick up personal data by accident more than by design. If something has reached us that should not have, deleting the project removes it, and we will confirm a targeted deletion if you ask. The surest protection is to scrub at the source, before the line is written.

Self-hosting

If you run loghq yourself, none of your log data reaches us and this policy does not apply to it. That option exists precisely for teams who cannot send logs to a third party.