Privacy Policy
This page explains how PrairieLog API handles data and what third-party services may apply when you use the service.
Last updated: July 3, 2026.
Log data
PrairieLog is a log alerting relay. At present, the service does not persistently store your application log events. Your logging data will not be sold, rented, or otherwise used for commercial purposes.
Log events may be held in memory for approximately one minute to group logs related to an ERROR. After that window, they are discarded. PrairieLog does not provide long-term log retention, search, or archival. PrairieLog is not responsible for the data you choose to log.
Alert delivery
When you configure Slack or Discord webhooks, summarized alert content is sent to those services using the webhook URL you provide. How those platforms store or process that data is governed by their own policies. Any misuse of webhook URLs is the responsibility of the user. Webhook URLs are sensitive credentials. Users are responsible for controlling access to any Slack or Discord webhook URLs they submit.
Third-party AI models
If using AI analysis alerting, PrairieLog API may send selected alert content, log messages, metadata, and related context to third-party language model providers.
PrairieLog is not responsible for how those third-party providers collect, store, train on, or otherwise use data submitted to them. Their handling of your data is subject to their own terms and privacy policies. Use analysis features only if you accept that risk.
Account and service data
To operate the service, PrairieLog stores account-related records such as user profiles, registered apps, hashed ingestion tokens, and alert destination configuration (including webhook URLs). This is operational metadata needed to authenticate ingestion and deliver alerts — not a copy of your full log stream.
Website analytics
This developer portal may use third-party analytics (such as Google Analytics) to understand general site usage. That data is separate from log ingestion and is governed by the analytics provider's policies.
Sensitive data
Users should not send passwords, API keys, access tokens, secrets, payment data, health information, or other sensitive personal information through PrairieLog API. Users are responsible for reviewing and filtering the data their applications send to the service.
Changes
If PrairieLog's data practices change — for example, if persistent log storage is added — this page will be updated. Material changes will be reflected here with a revised date.
Questions about this policy can be directed to Robert Sima on GitHub or LinkedIn.