COOKIES & LOCAL STORAGE

Cookie & storage policy

A clear view of the small things this browser remembers—and how to stay in control.

FRONTEND EDITION · CURRENT BEHAVIOR

Browser-only preview

This edition has no connected backend. There is no real account authentication, AI, OCR, payment processing or message delivery. Document search and rule-based invoice processing happen locally. Demo passwords are not verified or stored.

Choosing Save stores extracted source text or results in this browser’s local storage (up to 20 items / approximately 1 MB of JSON text). A demo profile stores only a name and email. These are not encrypted, account-isolated or synced. Anyone using this browser can access them. Do not enter sensitive information. Delete saved items and the demo profile separately in Tools → Saved. Clear session only clears working inputs.

The cookie acknowledgement is kept locally too. No AI-provider requests are made by this edition.

No tracking service is installed

This supplied website does not install an analytics SDK, advertising pixel or third-party font service. Accepting the acknowledgement does not activate tracking. Fonts and the PDF reader are served with the website.

What this browser remembers

The cookie acknowledgement is stored in localStorage under flowmint-consent with your choice and its time. Explicit workspace saves and optional demo-profile details use separate localStorage entries. This is browser storage, not a secure user account or cloud backup.

Change or remove your data

Use Cookie preferences in the footer to reopen the acknowledgement. Delete saved work in Saved and clear a demo profile separately in Settings. Clear session removes working inputs only. Clearing website data in your browser can remove all local preferences and saved work.

Hosting and future changes

The hosting provider may keep normal page-request logs under its own policies. If analytics, accounts, AI services or other external integrations are added later, the operator must update the notices and any required consent controls before enabling them.