Free Invoice Generator / Privacy Policy
Legal

Privacy Policy

This guide explains what data MakeInvoice.ai handles, what remains local, how self-operated Form Intake and minimum account records work, and when processors such as Google Analytics 4 and Stripe are involved.

What we collect

MakeInvoice.ai can process several categories of data depending on how you use the site:

  • Invoice draft data that you enter into the generator
  • Browser storage data used to keep local drafts and history on your device
  • Site analytics and usage events used to understand traffic and product usage
  • Email addresses, selected feature or interest, and free-text feedback that you submit through Form Intake
  • Basic Form Intake context such as page, language, and device information
  • Minimum account data needed for login and entitlement: an email or login identifier, watermark entitlement state, a stable opaque documentId used only for permanent single-invoice entitlement recovery, and basic security timestamps
  • Payment details handled by Stripe for one-time checkout and payment records

What stays local in your browser

The main invoice workflow is designed to be local-first. Invoice drafts and history remain in your browser by default and are not sent through Form Intake or attached to an account.

For permanent single-invoice entitlement recovery, the account stores only a stable opaque documentId. Invoice content is not uploaded or stored with it.

This means the normal create-edit-download flow does not rely on server-side invoice storage as its primary mode.

Form Intake and third-party processors

Form Intake is operated by MakeInvoice.ai on its own infrastructure. It receives waitlist or feedback email, selected feature or interest, free-text feedback, and basic page, language, or device context. It does not receive invoice drafts or history.

Some other parts of the site use third-party processors:

  • Google Analytics 4 for website analytics and product usage measurement
  • Stripe for one-time checkout and payments through the MakeInvoice.ai payment account of VALID INDUSTRIAL SYSTEMS LIMITED; MakeInvoice.ai does not receive or store full card numbers

When you use a processor-backed flow, the relevant data may also be handled under that processor’s terms and privacy practices.

Analytics, cookies, and consent

MakeInvoice.ai uses analytics to understand traffic, usage, and product performance. In every region, non-essential analytics remains off until you explicitly allow it.

For more detail, read the Cookie & Analytics Notice. This site should not send personally identifiable information such as email addresses to Google Analytics.

URL-prefill and invoice data caution

The site supports URL-based invoice prefilling. If you generate or share a prefilled invoice URL, the data embedded in that URL may be visible to anyone who receives or accesses it.

Do not use URL-prefill links as a secret or secure transport mechanism for sensitive information. Use them only when that sharing model is appropriate for the invoice draft involved.

How long data is kept

Local draft and history data remains in your browser until you clear it, overwrite it, or remove local site data. Form Intake submissions and minimum account records are retained only as needed to handle the request or account and to meet applicable legal or security obligations.

Analytics and Stripe payment records follow the relevant processor settings and legal retention requirements.

Do you store my invoices on your server by default?

No. Drafts, history, and invoice content stay in your browser by default. For permanent single-invoice entitlement recovery, the account stores only a stable opaque documentId; invoice content is not uploaded or stored with it.

Do you collect email addresses?

Yes. Form Intake receives email and feedback when you submit a form, and an account uses the minimum account data needed for login and entitlement. Both flows are separate from the local-first invoice editor.

Do you use analytics?

Yes. Anonymous analytics remains off in every region until you explicitly allow it.

How can I contact you about privacy questions?

At this stage, the site does not publish a dedicated privacy mailbox. Use the available site feedback or waitlist form and clearly mark your request as a privacy or data question until a dedicated contact channel is published.

Need the related legal pages?

Read the terms of use and the cookie notice if you want the operational and analytics details that sit next to this privacy summary.

Terms of Use