Privacy Policy
Last updated: May 25, 2026
At AELog, we believe that development tools should respect developer and end-user privacy. Because AELog is an open-source library that runs entirely on your client application, this Privacy Policy explains exactly how data is handled.
1. No Data Collection by Us
AELog is a client-side logging and debugging library. We do not host any remote backend servers for this library, and we do not collect, store, or transmit any data logged or tracked by AELog. All data captured by AELog remains local to the device running your software.
2. Local Storage and Logging Behavior
AELog gathers logging, network requests, and crash dump information locally. Depending on how the library is configured, this data is stored in one of two ways:
- In-Memory (RAM): Transient log buffers (such as Ktor/OkHttp logs and system traces) are saved in memory and wiped entirely when the application is closed.
- Persistent Disk Storage: Specific plugins (such as
CrashPlugin) write crash records and diagnostic data directly to the device's local file system. This ensures reports survive application restarts for debugging purposes.
3. Third-Party Integrations
AELog includes plugins to format, print, or capture data locally. It does not auto-forward log data to any third-party software analytics providers (like Firebase Crashlytics, Sentry, or Datadog) unless you explicitly write custom plugins to send that data to those services.
4. Security of Data
Since data is stored on-device, its security depends entirely on the sandbox policies and encryption mechanisms of the host operating system (Android, iOS, or JVM platform). We recommend configuring sensitive data filtering on network interceptors to prevent logging credentials, passwords, or personal identity numbers.
5. Open Source Auditing
AELog is fully open-source. Developers are encouraged to audit the source code in our repository to verify our logging, storage, and persistence mechanisms.
6. Changes to this Policy
We may update this Privacy Policy from time to time. Any updates will be pushed directly to this website and the GitHub repository.
7. Contact
If you have any questions about this Privacy Policy, please open an issue on the AELog GitHub Issue Tracker.