BeanNestTools

Privacy

Your files should stay yours.

Most BeanNest tools process working input in your browser. When a tool needs remote access, such as URL to Markdown, its page explains exactly what is sent and why.

Last updated September 9, 2026. BeanNest is operated and published by LB DataForge Inc. Contact: Contact page.

Files and local processing

The tools do not send file bytes, filenames, page text, thumbnails, document metadata, image contents, or file fingerprints to BeanNest. Results and previews use temporary browser data that is removed when you replace files, reset a tool, close an Editor workspace, or leave the page. The AI Image Upscaler downloads static model files, but your image and generated pixels are not included in those requests.

Remote URL rendering

URL to Markdown is different from BeanNest's local file and text tools. The public page URL you enter is sent to BeanNest's same-origin Cloudflare endpoint and then to a private Cloudflare rendering Worker so a managed browser can load the target page and return Markdown. The target website receives a request from Cloudflare's managed browser and may process or log that request under its own policies.

BeanNest application code does not save the submitted URL, hostname, target page title, or returned Markdown in D1, KV, R2, browser storage, or another application history. The rendering path does not forward your BeanNest cookies, target-site login cookies, Authorization headers, custom target headers, or URL credentials. Local/private/special-network targets are rejected, and sites that block automated browsers are not bypassed.

Analytics

BeanNest may use aggregate Cloudflare traffic reporting to understand visits, requests, popular paths, countries, device categories, and data transfer. BeanNest has no visitor accounts and does not use its local management dashboard to build visitor profiles.

Google Analytics is currently enabled automatically on public production pages. When enabled, it helps BeanNest understand page use, internal navigation, and whether a tool is started, completed, cancelled, failed, or followed by a download.

Analytics may receive a page title, a path without its query or fragment, a broad site area, sanitized internal-link paths, and coarse tool events. They do not send filenames, file contents, document text, images, thumbnails, metadata, hashes, object URLs, precise dimensions, exact byte counts, quiz question/answer text, private quiz or recovery secrets, recovery email addresses, player answers or scores, user-entered values, source URLs, target hostnames, rendered Markdown, or raw error messages. Advertising storage, personalization, Google signals, User-ID, and cross-domain tracking are not enabled through this analytics setup.

Analytics providers may process standard technical data needed to offer their service, such as timestamps, first-party identifiers, browser and device information, language, screen size, and IP-derived location.

Product feedback

After a tool successfully produces a result, BeanNest may show a small optional feedback prompt. A rating uses only the tool ID and one of five fixed rating categories. If you choose to write a note, that note is sent to BeanNest's same-origin feedback endpoint and stored in a dedicated Cloudflare D1 database so the publisher can review what should be improved.

The feedback form does not ask for your name, email address, account, filename, or file contents. Please do not put personal or sensitive information in the optional note. Written feedback is not sent to Google Analytics. The application feedback schema stores a generated response ID, time, tool ID, rating, optional note, and schema version. Rows older than 180 days are scheduled for opportunistic cleanup when new feedback arrives.

Advertising

Advertising is currently disabled. When enabled, only configured ad slots load the approved provider script. File processing stays separate, and the tools do not provide PDF or image contents to the advertising service.

Contact messages

Messages sent through the Contact page are handled through Gmail. The sender address and message are used to reply, investigate a report, or handle a privacy or security request. They are not added to a newsletter or marketing list.

Google processes and stores those messages as the email provider. Do not send private files, passwords, identity documents, financial records, medical information, or other sensitive content. Messages are kept only as long as reasonably needed for the inquiry, security, recordkeeping, or legal requirements. You may use the same address to request access, correction, or deletion, subject to applicable retention requirements.

Device and output limits

Browser processing uses your device memory, CPU, and, for the AI Image Upscaler, graphics hardware. Safety limits may reject large jobs before they destabilize the browser. Some PDF operations rasterize pages or can remove selectable text, forms, links, annotations, signatures, bookmarks, or accessibility structure. Keep every original and check the result before relying on it.