Privacy Policy

Website access may produce basic logs such as request time, path, browser type, IP address, and error information for security, troubleshooting, and service reliability.

When you use cloud relay, bot pages, or download services, we may process connection status, device type, version, session identifiers, request metadata, and necessary transport logs to deliver messages, downloads, and diagnostics.

If you contact us through GitHub, email, chat platforms, or other channels, we process the contact details, issue descriptions, screenshots, log excerpts, or support materials you provide.

lsbot encourages local operation and end-to-end encryption by default. We do not intentionally read, train on, or sell your chat content, AI prompts, keys, model outputs, contact lists, or local files.

If you disable encryption, submit logs, or transmit data through third-party chat platforms or AI providers, those services may process the information under their own policies.

We use information only to provide, maintain, and improve lsbot services, including operating cloud relay, displaying bot pages, distributing installers, diagnosing errors, preventing abuse, responding to support requests, and meeting legal obligations.

We do not sell personal information to third parties or use private content for advertising profiles.

lsbot client and server configuration is usually stored and controlled by you. Cloud services retain only the information necessary to operate and delete or anonymize it when it is no longer needed.

Security, error, and operations logs are retained under a minimum-necessary approach for audit, abuse prevention, and troubleshooting. Support materials you provide are cleaned up within a reasonable period after the issue is handled.

lsbot can connect to AI providers, chat platforms, code hosting platforms, object storage, CDN, payment, or download infrastructure. When you enable these integrations, relevant data is sent to the selected service as required by its API.

Before enabling a third-party integration, review that service provider's privacy policy and terms, and confirm you have the right to send the relevant data.

We use measures such as end-to-end encryption, local-first design, least privilege, access control, and log minimization to reduce exposure risk.

No system is absolutely secure. Keep API keys, access tokens, bot links, and local configuration files safe, and avoid posting sensitive logs publicly in issues or chat channels.

You can stop using cloud relay or delete locally deployed data. For support information you provide to us, you may request access, correction, or deletion.

If you use lsbot on behalf of an organization, ensure you have the required authorization and provide appropriate notice to end users under applicable law.

We may update this policy as the product, legal requirements, or security practices change. Material changes will be published through the website or project repository.

For privacy requests, contact us through the GitHub repository issues or your existing contact channel with the lsbot team.