A plain-language distinction between fully local tools, High Accuracy cloud OCR and the data the account system actually retains.
Batch renaming, image conversion/resize/enhancement, text-to-document export, built-in or custom document backgrounds, PDF merge/split and images-to-PDF, CSV/TSV/JSON conversion, SHA-256 duplicate detection and ZIP packaging run in your browser. Except for High Accuracy OCR described below, selected file contents are not sent to a FileNest conversion server, and originals are never overwritten or automatically deleted.
After explicit user confirmation, High Accuracy mode transiently submits selected JPG, PNG or WebP images to the FileNest OCR Worker, which uses Azure Document Intelligence prebuilt-read for the recognition request. The third-party OCR provider processes that request under its service; FileNest's current implementation does not write OCR source images to R2, KV or the FileNest database. If you do not want an image to leave your device, choose Local Privacy OCR. Local Privacy mode uses Tesseract.js in the current browser; selected images are not uploaded for OCR recognition. OCR runtime assets or language data may download on first use. Both modes can make recognition errors and require human review before export.
Core batch renaming needs no account. Image, OCR, text-document, PDF and data conversions that consume credits require a free account. The server stores only the account identifier, conversion time, tool type, count and status to enforce the rolling 24-hour quota. FileNest's account database does not store OCR source images, other tool file contents or entered text. Clearing site data, private browsing or changing browsers does not reset the server quota.
The hosting provider may process request time, path, browser, device and network logs for security, troubleshooting and performance. High Accuracy OCR image content enters only the explicit OCR request path and is transiently processed by Azure Document Intelligence for the recognition request; FileNest does not intentionally copy file contents into diagnostic logs.
The account service retains only the identifiers, membership state, quota, naming templates and job metadata needed to operate FileNest. It does not store browser-local file contents or High Accuracy OCR source images. Stripe processes card details, and FileNest never stores full card numbers. If you have accepted analytics and start Pro checkout, FileNest may also store a tightly bounded checkout-attribution snapshot so we can measure which channels and tools actually produce revenue. That snapshot can contain source/medium/campaign tags, the FileNest landing path, first tool used and most recent successful tool, but not file names, file contents, entered text, full referrer URLs, email addresses or card details. Optional browser attribution state is kept for at most 30 days; raw server-side checkout-attribution snapshots are retained for no more than 400 days, with scheduled cleanup deleting rows after a 397-day threshold to leave execution headroom.
Saved naming templates will not be deleted after expiry, payment failure or cancellation; execution of advanced templates may pause with membership status. A first renewal failure enters a limited grace period rather than immediately deleting templates or clearing membership data.
FileNest uses Google Consent Mode. When a page opens, the Google tag starts with analytics_storage=denied and advertising-related storage also denied, so GA analytics cookies are not read or written. Before you consent, or after you Reject, Google may receive limited cookieless measurement and consent-state signals for basic measurement and modeling; these signals can include technical information such as page URL/referrer, browser and device details. Full site analytics starts only after Accept, including page views, referral source, browser/device category, approximate region, tools used, counts of files added and task success. After consent, FileNest can also keep a limited acquisition context in this browser for up to 30 days so a later pricing visit can be connected to first/recent source and successful-tool context; Reject clears this optional local attribution state. FileNest does not intentionally send file names, file contents, entered text, email addresses or card details to GA4, and FileNest custom tool events, file-count events and FileNest checkout-attribution snapshots are not created before consent. You can change your choice at any time through Analytics settings in the footer.
Send privacy questions to filenest12@gmail.com. Material changes will update the date on this page.