Privacy

How Online Receipt Maker handles drafts, accounts, and support data.

Browser draft state can stay local on your device, while account-backed templates live in the configured backend database. This page summarizes the current product behavior in plain language.

Open the editor Contact support

Browser draft storage

The live editor can keep in-progress work in the browser so refreshes do not immediately destroy your current receipt draft.

Local draft state depends on the current browser session.
Unsigned users can still experiment without creating an account first.
Clearing browser storage may remove unsaved local work.

Account-backed templates

When you register and save templates, those saved records are linked to your authenticated workspace and stored on the backend.

Saved templates are tied to the authenticated account.
Sessions are maintained with secure cookies handled by the auth flow.
Password resets revoke old sessions after the password changes.

Contact and operational data

Contact requests use the configured API path and verification flow. If you deploy publicly, you should document retention, access, and delivery systems in full.

Production deployments should disclose email providers and retention periods.
Analytics, logs, and abuse monitoring should be documented separately.
Operational details may differ by hosting environment.

Before you launch publicly

Publish a complete privacy policy that covers storage duration, analytics, infrastructure providers, email delivery, user deletion, backups, and incident handling. This summary is intentionally product-focused, not a substitute for full legal documentation.