Privacy Policy

Local processing

Where a Logrun Lab tool is designed to process files or data directly in the browser, that processing happens on the user's device.

Logrun Lab does not upload or store the contents of such files unless a tool explicitly states that server-side or external processing is required.

Accounts and user profiles

Logrun Lab currently does not require user registration for its public tools.

Logrun Lab does not currently maintain user profiles, personal workspaces, or server-side histories of processed files and results.

If accounts or persistent user data are introduced later, this policy will be updated before those features become part of the public product.

Usage events

Logrun Lab counts a limited set of product events to understand whether its tools are being used and where technical problems occur.

These events may include actions such as:

• opening a tool;
• adding input;
• starting or completing processing;
• exporting a result;
• encountering an error;
• reaching a technical limit;
• expressing interest in a future tool.

Only predefined event names are sent to the Logrun Lab analytics endpoint.

File contents, filenames, document contents, and text entered into tools are not included in these analytics events.

Analytics counter

Selected product events are forwarded to a Logrun Lab counter hosted on PythonAnywhere.

The current counter stores only limited aggregated information, including:

• event name;
• project source;
• total event count;
• time of the latest recorded event.

The current analytics system does not provide Logrun Lab with user accounts, user profiles, sessions, retention data, UTM attribution, geography, or device-level analytics.

Third-party infrastructure

Logrun Lab uses third-party infrastructure to host and deliver the website.

These infrastructure providers may process standard technical information required to serve web requests, such as IP addresses, browser information, and request metadata, according to their own policies and operational requirements.

Logrun Lab does not use this infrastructure to build individual user profiles.

AI and external processing

Logrun Lab does not assume that every tool uses AI.

If a tool sends user-provided content to an external AI or other processing provider, this will be disclosed before that data flow is enabled for the public product.

Where possible, Logrun Lab prefers to keep processing local to the user's device and to send external services only the data required for the requested operation.

Payments

Logrun Lab does not currently process payments through the public website.

If paid features are introduced, the relevant payment and data-processing information will be added before public payment flows are enabled.

Changes to this policy

Logrun Lab may update this Privacy Policy when its tools or infrastructure change.

In particular, the policy will be reviewed before introducing material new data flows such as:

• server-side file processing;
• external AI processing;
• user accounts;
• persistent storage;
• payments;
• additional analytics.

The effective date at the top of this page will be updated when material changes are made.

Contact

Questions about this policy can be sent by email.