Privacy Policy

Introduction

This service lets you create restaurant bills locally in your browser and, if you sign in and enable cloud history, save selected bill data to your account. This Privacy Policy explains what we store, why we store it, and how menu-image recognition is handled.

What stays local

• Anonymous bill drafts stay in your browser's local storage.
• PDF/PNG/print export works without signing in.
• If you do not enable cloud history, your bill stays local even when you are signed in.

What we store in your account

When you sign in and use account features, we may store:

1. Account information — name, email address, authentication/session data, and security events needed to operate your account. We also process activation and password-reset email delivery records. Open and link-click events are recorded only when the site operator explicitly enables those email tracking options.
2. Saved bill history — bill details you explicitly allow us to save when cloud history is enabled, including bill number, date/time, business fields, line items, totals, payment method, and a redacted render snapshot used for history and reprint.
3. Business profile and menu settings — your saved business information, logo reference/data, billing defaults, and menu items so the generator can auto-fill and quick-pick dishes for your account. These settings are stored when you use those features; they are not controlled by the cloud-history toggle.
4. Analytics data — structured totals, currencies, time buckets, and saved bill item facts used to show revenue, payment mix, peak hours, and top dishes in your dashboard. Analytics is derived from bills you chose to save through cloud history.
5. Legacy saved bills — if bills were stored before the current disclosure flow, we keep them visible until you choose to keep-and-use them or delete them.

Website usage analytics

We use Google Analytics to understand how the website and its main product flows are used. It may process page and referrer information, device/browser information, approximate location, and product-action events. The events we send cover successful account registration, successful bill export, successful AI menu recognition, checkout initiation, and a confirmed subscription purchase.

These event payloads contain only coarse product metadata such as export format, template identifier, currency code, item count, recognition destination, public subscription-plan details, purchase value, and a non-personal transaction identifier used to prevent duplicate purchase reporting. We do not send names, email addresses, restaurant/customer fields, menu or line-item text, uploaded images, bill numbers, or bill contents in these event parameters. Website usage analytics is separate from the saved-bill business analytics shown in your account.

Menu photo recognition and third-party AI processing

If you upload a menu image for AI recognition:

• the image is sent to a third-party AI provider for OCR/vision processing;
• we store recognition-related account, menu, and task metadata needed to deliver the feature, handle retries/failures, and audit abuse or incidents;
• we do not keep raw uploaded images indefinitely as long-term account content;
• recognition results can be reviewed and, when your plan includes the menu library, saved there if you choose; otherwise they stay as temporary bill quick-picks.

We may also keep short-lived operational records such as timestamps, status, provider identifiers, and error metadata to operate and protect the service.

How we use stored data

We use saved data to:

• render and reprint bills you chose to save;
• keep your business profile, menu, and billing defaults available across sessions;
• generate analytics from saved cloud-history bills only;
• process support, abuse prevention, reliability, and account-security workflows.

Data sharing

We do not sell your personal information.

We may share data only with:

• service providers that help run authentication, hosting, storage, payment, or AI recognition;
• Google as our website analytics service provider;
• legal or regulatory authorities when required by law;
• security and abuse-prevention systems when needed to protect the service and other users.

Retention and deletion

• Local drafts remain in your browser until you clear them.
• Saved bill history remains in your account until you delete it or your account is removed, subject to operational/legal retention requirements.
• You can delete individual saved bills, delete all saved bill history, and resolve older pre-disclosure saved bills inside the product.

Security

We use access controls, authentication, and transport security to protect stored data. No online system is perfectly secure, but we limit stored fields, avoid long-term raw-image retention for AI menu recognition, and review operational logs and access paths.

Your choices

You can:

• export bills locally without enabling cloud history;
• enable or disable cloud history for future saved bills and analytics only;
• keep or delete older saved bills created before this disclosure flow;
• delete saved bill history from your account.
• use browser privacy controls or content blockers to limit website analytics, subject to their capabilities.
• contact us if you want more information about operational email delivery or tracking records.

Changes

If this policy changes materially, we will update the effective date and, when appropriate, surface an in-product notice.

Contact Us

If you have questions about this Privacy Policy, how we handle your data, or a privacy-related request, contact us at support@restaurantbillgenerator.org.