Skip to content
LeMaker
Menu

Privacy and data handling

FleetCare development preview. Public signup and payments are closed.

LeMaker

Support: support@lemaker.org ยท Privacy: support@lemaker.org

LeMaker handles FleetCare account and service information. Contact support@lemaker.org with privacy questions or requests for access, correction, export or deletion.

Account information includes your email, authentication and security records, organisation membership, roles, customer/site/device labels and billing references. Stripe handles card details and payment records through its hosted Checkout and billing portal. FleetCare uses the associated customer, subscription, invoice and event references to administer access and billing.

An enrolled agent sends a random installation identity, OS/version, architecture, kernel and agent version, plus the selected CPU, memory, uptime, filesystem and available temperature observations. Your chosen labels and filesystem aliases appear in the service. Availability, incidents, report coverage and gaps are derived from received observations. The product documentation describes the collector's fixed scope and unavailable readings.

The free local report workflow processes the selected report in your browser. Hosted monitoring begins through explicit account trial and device-enrolment steps. Network services receive connection metadata, including source IP addresses, when handling requests.

FleetCare uses Hetzner for application hosting, Cloudflare for network protection, transactional email and encrypted off-host backups, and Stripe for payments. Providers can process information in multiple countries. Their service agreements and privacy notices explain their own processing. Contact LeMaker for information about the arrangements applying to your account.

Essential host-only session and security cookies support authentication and request protection. Public LeMaker guides use Umami through first-party proxy routes for page and placement interactions. Approved attribution records can connect a public guide with account activation. Operational reports and device measurements belong to the authenticated service.

While an account is active, five-minute telemetry aggregates are retained for seven days. Hourly aggregates, resolved incidents and reports use 90-day retention. Expired monitoring data is cleaned up after the 30-day export window. Account and membership records support your account until the relevant deletion operation. A keyed trial-use marker is retained after identity deletion to enforce the one-trial policy. Stripe maintains its payment and financial records under its own retention requirements.

Origin web logs use 14-day rotation. Application-process logs use three rotated files of up to 10 MB each. Ingestion access logging is disabled. Encrypted database backups use the configured 30-day expiry rule, so a deletion request can take additional time to age out of historical backups. Recovery handling must reapply completed deletion requests where restored information requires it. Cloudflare maintains delivery events and operational execution records under its provider policies. Email-body previews are disabled in the configured Cloudflare activity viewer.

Use the authenticated export and deletion controls or contact support for help. Account deletion and organisation deletion have separate effects, particularly where other members or an active subscription remain. Share the minimum information needed for a support request.