1. Scope
"Cookies" are small text files stored by your browser. "Similar technologies" include localStorage, sessionStorage, and indexed storage used for the same purposes. This policy covers the public marketing site (home, pricing, contact, legal pages, signup, and login) and the authenticated Hotflow web application.
2. Summary of what we use today
| Technology | Typical name / key | Purpose |
|---|---|---|
| localStorage | Auth session key (per deployment) | Keeps you signed in to the dashboard; stores access token and session metadata |
| localStorage | hms-locale | Remembers your selected interface language |
| localStorage | hms-search, hms-notifications, UI preferences | Optional in-app preferences for search and notifications where enabled |
| sessionStorage | Session lock, module visit tracker, cached snapshots | Session security, faster reload of workspace data, draft POS orders in some modules |
Our review of the frontend and backend did not identify standard HTTP cookies set by Hotflow for authentication or analytics on the marketing site. Third-party payment or embedded widgets, if added later, may set their own cookies under their policies.
3. Marketing and auth pages
Public pages such as the home page, pricing, contact, signup, and login do not require cookies for basic viewing. Signup and login submit data to our API; after a successful login, the browser stores session data in localStorage as described above.
We do not currently deploy Google Analytics, Meta Pixel, or similar third-party marketing trackers in the frontend codebase reviewed for this policy.
4. Authenticated application
While using the dashboard, the application may store additional keys in localStorage or sessionStorage for features such as layout and navigation preferences, housekeeping or module snapshot caches, restaurant/bar order drafts, and data-sync helpers. These are functional storage items tied to your session or workspace, not advertising profiles.
Real-time updates may use a WebSocket connection to our API; that connection uses your authenticated session and does not rely on third-party ad cookies.
5. Guest-facing features
Guest QR ordering or public invoice links load data from our API for the specific business and token in the URL. These flows may use minimal browser storage for order tracking where implemented; they do not use Hotflow marketing cookies.
Optional web push notifications register a push subscription with your browser and our servers when a guest or user explicitly opts in on supported pages.
6. Managing cookies and browser storage
You can clear cookies and site data through your browser settings. Clearing Hotflow storage will sign you out and remove saved preferences such as language. Blocking all storage may prevent the web application from working correctly.
For questions about this policy, contact support@gethotflow.com.
7. Updates
We will update this page when we materially change how we use cookies or browser storage. See also our Privacy Policy.