Last updated: 10 October 2026. This policy describes the client-side behavior found in the current application code during a code review on this date. It is not an independent audit of the hosting provider or production network configuration. The host may separately process routine requests and keep server logs; its identity, retention period and practices have not been verified here.
Information entered into the tools
Invoice and billing details—including business and customer names, contact and address details, tax identifiers, line items, amounts, payment instructions and notes—are entered and calculated in your browser. The current application code has no invoice-upload endpoint and does not send those form values to an application server to create a preview or download. PDF, DOCX and XLSX exports are generated in the browser.
Browser storage
Drafts can be saved in local storage on the same browser and device. Saved drafts may contain invoice and customer details, tax settings, payment instructions, custom fields and a logo image encoded for local preview/export. If you enable the remember-business option, selected business and payment details may also be saved separately. Country/document drafts, numbering counters, calculator currency/country/tax-label preferences and display preferences may also use local storage.
One-time invoice-conversion and calculator handoffs use session storage in the current tab. A handoff may contain the details needed to open the selected document or calculation in the shared editor. The receiving page removes the handoff when it imports it; until then it may remain available to scripts running in that same tab session.
Use the editor’s Clear Saved Data control to remove the supported saved drafts, remembered business details and numbering counters. It does not promise to clear every tool preference or every browser session value. To remove all site data, use your browser’s site-data controls. Local and session storage are not encrypted by this site; anyone with access to the same browser profile or device may be able to access saved information.
Local workspace
The optional workspace stores documents, clients, products and services, payment records, business/brand/payment profiles and business images in the browser’s IndexedDB database on the same browser and device, with small local-storage pointers and preferences. Your business documents and saved workspace are stored locally in your browser; this site does not provide cloud document storage and never uploads workspace data to an application server. Workspace backup export downloads a JSON file containing your real records (documents, clients, catalog entries, payment records, payment reminders, recurring templates and preferences) — store it safely — and restoring a backup imports it back into the same browser. Workspace search, filters, totals and payment records all run locally. Clearing browser/site data may remove the workspace, so export a backup if your documents are important. Share, email, download and print actions pass data to the application or destination you choose; review it before sending.
Service worker and offline cache
The site can install as an app and work offline using a service worker with Cache Storage. That cache holds application files only (pages, stylesheets, scripts, configuration, icons) so previously opened tools reopen without a connection. It does not contain your document database: workspace documents, clients, payments and profiles stay in IndexedDB and browser storage, which the service worker never clears or migrates. App updates replace cached files only, after your current work is saved. Installing the app does not back up your data and creates no cloud copy — export a workspace backup for important records. Removing the site’s browser data may remove both the offline cache and the workspace.
Logo files, previews and exports
A logo file you choose is read, resized and held in browser memory for preview and export; the resulting image data may be included in a locally saved draft. The current editor code does not upload that file to an application server. Downloads are created in the browser, and printing uses the browser’s print interface.
Sharing and external services
Sharing is an action you choose. The current invoice share/copy controls prepare a short summary (document type, reference and totals/dates) rather than the invoice file or customer details. Email, messaging, clipboard and operating-system share features are handled by your chosen application or external service after you activate them. Review the destination and content before sending. Links to government and other external sites open those sites, which have their own privacy practices. Payment links and payment instructions are user-provided; this website does not process payments.
Workspace share controls (Copy summary, Open in Email App, Open in WhatsApp, device share, Download PDF) each run only when you activate them. Email drafts open in your mail application and WhatsApp messages open in WhatsApp with the recipient you enter — the site has no mail server, sends nothing on your behalf and never guesses a missing country code. A PDF attached through device share goes only to the destination you select.
Payment reminders and recurring invoices
Payment-reminder wording is generated in your browser from built-in tone templates and the invoice's own details, in the language you select. You review and edit every reminder before you copy or send it; nothing is sent automatically and no message leaves your device until you choose a destination. The site does not track delivery or opens: reminder history records only the action you took (generated, copied, opened in an email app, opened in WhatsApp, or shared through the device menu). Reminder text is never sent to analytics. Recurring schedules are local templates: nothing runs while the browser is closed, due occurrences wait for your review, and a new invoice is created only after you confirm it. No public or hosted invoice links are created — documents leave your browser only through an export or share action you trigger.
Analytics, cookies and third-party code
The current client code includes a local allowlisted event adapter that dispatches limited events within the browser. It has no event listener or analytics backend in this codebase, does not store those events and does not transmit them. Event metadata is restricted to tool, document-type, country and template identifiers—not invoice or customer content. The reviewed application code does not call document.cookie or load an advertising, chat, heat-map or third-party analytics service. This describes the reviewed code, not cookies or processing that a hosting provider may apply at the network layer.
Questions
For privacy questions, email freeinvoicegeneratorr@gmail.com. Please do not email invoice contents or customer records.