MakeInvoice.ai is built so invoice drafts stay on your device by default. This guide explains how local browser storage, lightweight analytics, and user choice work together without turning invoice drafts into profile data.
Invoice drafts, history, and related editor state are stored in your browser as part of the core product workflow. That storage exists so the editor behaves like a local-first tool, not so draft content can be harvested into analytics.
Local storage here is product functionality. It is separate from advertising or cross-site profiling logic.
When you choose to participate, the site uses Google Analytics 4 to understand traffic, feature interest, and product usage. The goal is product improvement and SEO measurement, not turning invoice drafts into profile data.
Analytics events should avoid personal data such as email addresses, names, invoice line items, or free-form draft content.
In every region, non-essential analytics remains off until you explicitly allow it. Declining or making no choice does not limit the invoice editor or its essential functions.
The point is to keep the product honest: local editing should keep working, and measurement should remain a separate choice.
The waitlist form is a separate submission flow and should not be treated as part of analytics measurement. Email addresses and free-text feedback belong in the form system, not inside analytics event payloads.
This distinction matters for privacy compliance and for keeping product measurement clean.
You can reopen analytics choices at any time. Allowing anonymous analytics helps improve the product; choosing not now keeps the core editor working without non-essential measurement.
This control affects analytics measurement only. It does not delete invoice drafts stored locally in your browser.
The invoice editor is local-first by design, so local browser storage and analytics are two different systems. This notice explains how they stay separate: local functionality, measurement defaults, and user choice.
Use the privacy page for broader data-handling details and the terms page for rules around product use.
No. Local draft and history storage is part of the browser-side product workflow. It is distinct from advertising or profiling logic.
Yes. Anonymous analytics remains off in every region until you explicitly allow it.
No. Personally identifiable information such as email addresses should not be sent to Google Analytics.
Use the privacy page for data handling and the terms page for the rules around site use and user responsibility.