Your workbook and your checkout details follow different paths.

Workbook comparison

When you use WorkbookLens Online, the two files are read into memory by JavaScript running in your browser. The workbook bytes, filenames, cell values, formulas and generated report are not submitted to the WorkbookLens Node server, Telegram, analytics, or an advertising service.

The comparison page loads its code from this site. After a real comparison finishes, it sends a same-origin operational event containing only whether positional or keyed matching was used, whether differences were found, the number of differences, and the completion time. The Node server forwards that event to the operator's configured private Telegram chat. Report downloads are created locally with browser objects. Refreshing or closing the page discards the current in-memory comparison when the browser releases it.

The page does not execute workbook macros or recalculate formulas. It parses workbook structures and compares stored data. Browser and operating-system internals may use normal memory caching; “local” means WorkbookLens does not transmit the workbook to our systems.

Operational and checkout Telegram notifications

The CLI checkout asks for a name, email address and platform. Those details are placed in short-lived, cryptographically signed checkout state so the license can be issued. The service does not write them to a customer database.

When the order is completed, the name, email address, selected platform, license identifier, contact preference and claim time are sent through the Telegram Bot API to the same private chat. This lets the operator provide fulfillment support. Telegram processes and retains both operational comparison events and checkout messages under its own terms and privacy practices.

The optional follow-up checkbox controls whether the customer is inviting product-feedback and setup email beyond necessary fulfillment communication. No payment-card data is requested or handled by this application.

Server records and cookies

The hosting provider may retain ordinary web-server records such as IP address, route, timestamp and browser information. WorkbookLens uses a short-lived, HttpOnly, SameSite comparison-session cookie to authenticate the operational event and rate-limit abuse; it expires after two hours. Checkout uses a separate short-lived, HttpOnly, SameSite cookie to prevent forged submissions, and that cookie is deleted when checkout completes. Signed download links expire after the configured period.

What we deliberately do not send

• Workbook files or their contents
• Workbook filenames or generated reports
• Payment-card information
• Signed download URLs or checkout security tokens in Telegram notifications

Questions or deletion requests

Use the contact route published by the operator of tools.devrefine.com. Because the launch site has no customer database, a request involving the Telegram notification must identify the email address used at checkout so the operator can locate the message.

Last updated: 17 August 2026.