// privacy policy
This policy explains what LaraBench collects through the website and the desktop app, how we use it, and where data stays local to your device.
Effective date: July 10, 2026
When you use the LaraBench website, we may collect information you provide directly to us and information collected automatically through the site.
If you create an account, we store your name, email address, and a hashed password. If you contact us through the contact form, we receive the name, email address, optional company name, and message you submit. If you start or manage Premium billing, billing flows are handled through Stripe and our website stores the account and subscription information needed to manage that relationship.
The website uses Google Analytics to understand aggregate traffic and usage patterns. Google Analytics may collect information such as IP address, browser and device details, pages viewed, referrers, and approximate location derived from network information. Google requires sites that use Google Analytics to disclose that use and explain how Google collects and processes data.
Google’s own disclosures are available at Google Analytics Privacy Disclosures Policy and Google Privacy Policy.
The website uses session and security mechanisms to keep you signed in, protect forms, and manage desktop authentication tokens when you sign in from the app.
LaraBench is designed to keep core working data on your machine. Connections, snippets, run history, appearance preferences, and similar app state are stored locally in the app’s own files on your device unless you sign in and use Premium cloud sync for supported data.
The desktop app sends first-party telemetry only to LaraBench-controlled website endpoints. The current telemetry is limited to install-level activity and release adoption. It includes a stable anonymous install identifier, the events app_installed and app_seen, and coarse technical fields such as app version, platform, architecture, release channel, whether the app is signed in to an account, and the current plan key if one exists.
The desktop app telemetry does not include snippet code, Artisan commands, project paths, hostnames, database names, SQL queries, log contents, or benchmark and run activity.
If you sign in to a LaraBench account from the desktop app, the app sends your email address and password to the LaraBench website over its authentication API and stores a desktop authentication token locally so you can stay signed in.
Connection profiles remain local to the device where you use the app. LaraBench does not sync local paths, hostnames, usernames, container names, key paths, or other connection details.
If you use Premium cloud sync, LaraBench stores your saved snippets, saved Artisan commands, saved custom theme colors, device metadata needed for sync, and sync timestamps on LaraBench servers. Run history sync is off by default and only uploads history after you enable it in the desktop app.
Run history can include snippet code, Artisan command text, selected output, SQL/query details, errors, project labels, and run timing. The desktop app lets you keep output details out of history sync.
We use website account, billing, and contact data to operate the website, authenticate users, process subscription flows, respond to messages, and provide account-related features.
We use Google Analytics on the website to understand aggregate traffic, marketing performance, and which pages are being used.
We use app telemetry to understand install counts, active installs, version adoption, and broad platform mix without collecting code or workflow details.
We may share data with service providers that help us operate LaraBench, including Google Analytics for website analytics and Stripe for billing. We do not sell your personal information.
Website account, billing, and support data may be retained for as long as needed to operate the service, meet legal obligations, resolve disputes, and enforce agreements. Desktop app local data remains on your device until you remove it. Telemetry records may be retained as operational product data for understanding installs, releases, and usage at an aggregate level.
You can choose not to create a LaraBench account, and you can stop using the desktop app or website at any time. You can also block or limit Google Analytics through browser settings, browser extensions, or privacy controls made available by Google and your browser. At the moment, the LaraBench desktop app does not provide an in-app telemetry toggle; if that changes, this policy will be updated.
If you have privacy questions, contact LaraBench at [email protected].