Scope and current features
This policy explains how the current Benchlight website handles information while you browse guides, use its local tools, or prepare a contact draft. The site does not require an account, accept payments, or provide a hosted workspace for your tool inputs. Privacy contact: [email protected].
This description concerns the functions implemented in the site. Browser features, your device, your email provider, websites you choose to visit, and the server delivering pages can handle information separately. Local tool processing should not be understood as a promise that opening a website creates no network requests or browser records.
Tool inputs and selected files
Tool calculations run in JavaScript in the open page. Pasted payloads, configuration samples, token text, and other tool inputs are processed there. The tools do not send those payloads to a processing API, upload them, or write them to localStorage, sessionStorage, or an application database.
Asset Budget Planner uses the names, MIME types, and byte sizes of files you choose. It does not read their contents or upload the files. Metadata itself can be sensitive: a filename can reveal a customer, project, or person. Choose files accordingly, particularly on a shared screen or device.
Tools that compose requests only create a textual draft. They do not contact the destination you enter. Inspectors do not navigate to a URL, fetch a source map, or query an identity provider to validate a result.
Search terms and URL history
The tool directory is different from a tool's input workspace. Its search text and category are placed in the page URL as query parameters so the view can be restored, bookmarked, or shared. The directory uses the browser history API to update that URL.
Those terms can therefore appear in browser history, copied links, bookmarks, and screenshots. Loading or reloading a URL containing them sends that URL to the server serving the page; navigation and browser referrer behavior can also disclose URL information. Do not put secrets or private records into directory search. Clear the filters and inspect the address before sharing a directory link.
Copying, downloading, and browser features
Copy controls write the selected result or contact draft to your clipboard only when you activate them. Clipboard history, synchronization, other applications, and the security of the device are outside the site's controls. A failed clipboard action is reported so you can select and copy the text manually.
Download controls create a local text file from the result. Your browser chooses how that file is saved and whether it appears in download history. The site does not receive a copy through that action. Check outputs before copying them into another product or sending them to someone else.
Benchlight does not create a saved tool history. Browsers may nevertheless cache pages, restore form values, autofill fields, or recover an open tab. Clear or close a workspace when appropriate, and use your browser's controls for data that it retains. We do not promise that a refresh, reset button, or private-browsing window erases every device-level record.
Contact drafts and direct email
The Contact page checks required fields and email formatting locally, produces a readable draft, and offers a copy action. It does not transmit the draft or create a server-side message record. Name and reply email are optional. The draft and fields remain on the page until you clear, edit, or leave them, subject to the browser behaviors described above.
If you separately send email to the displayed address, your email service and the recipient's email service handle that communication. The address, headers, message, and attachments you choose to send are not part of the local-only form check. Avoid including sensitive records in an initial inquiry. To ask about handling or deleting information you have sent by email, use the contact address and identify the relevant message without resending sensitive attachments. A local draft check does not confirm email delivery.
Page delivery, cookies, and technical records
The current site does not set application cookies or include analytics, tracking pixels, advertising scripts, remote fonts, or remotely embedded media. Its scripts, styles, and images are served as site resources. Loading these resources still involves ordinary requests to the server providing the website.
That server or its infrastructure may receive connection and request information, such as an IP address, requested URL, time, and browser-supplied headers. These delivery records are separate from locally processed tool payloads. Clearing an input does not request deletion of server records. For questions about delivery records or a specific visit, contact us with the relevant page and approximate time; do not include the private input you were processing.
External links and advertising information
Guides and reference sections link to standards organizations and other websites. Following a link starts a separate visit. That destination can process technical information and apply its own cookies or policies; review its information before entering personal data there.
Advertising and analytics are not enabled in the current site. The following Google resources are provided for information and user control, rather than as evidence that a Google advertising integration is active:
- Google ad personalization controls — may require a Google sign-in.
- How Google uses information from partner sites and apps — an explanation of data use, not an opt-out switch.
Adding advertising, analytics, remote resources, or a transmitting contact form would require updated disclosures and any controls applicable to the actual implementation. The presence of these links alone does not provide a consent mechanism.
Your choices and privacy inquiries
You can use the workbench without registering, choose what to enter, clear current fields, decline clipboard actions, and avoid downloads or external links. Browser settings provide separate controls for history, saved forms, cache, site data, and cookies.
Depending on applicable law and on information actually held by a responsible party, access, correction, deletion, or other privacy requests may be available. Use the Contact page to identify the page, behavior, and request. Do not send identity documents or a sensitive dataset merely to ask which information exists. Locally processed inputs that were never sent to the site cannot be retrieved from a site account or message database that does not exist.
The tools are designed for development and technical learning, and do not ask children to create profiles or provide a location. Guardians should review shared-device and browser settings where relevant. If you have a concern involving a child's information, begin with a minimal description through the contact address.
Security and policy updates
Use an up-to-date browser, follow your organization's rules for test data, and avoid entering credentials into a shared or untrusted device. Browser-local processing does not protect against device compromise, malicious extensions, an exposed clipboard, or an unsafe destination where you later paste an output. A page does not provide a guarantee of absolute security.
We will revise this page when the site's implemented data flows change. The date above identifies this policy revision. For related information, see Contact, About Benchlight, and the Terms of Use.