1. Summary
InventoryOS uses cookies, browser storage and similar technologies to make the website and app work. We do not currently use advertising cookies on the public website.
Last updated: 22 October 2026
Cookie Policy
This page explains how InventoryOS uses cookies, local storage and similar technologies on the public website and app.
2. What we use
Essential cookies/storageUsed for login, security, sessions, plan flow and keeping the app working.
Local storageUsed for app preferences such as selected inventory, selected workspace, theme, API base and login token storage. The public marketing site separately saves your light or dark appearance choice in this browser; this preference does not contain account or login data.
StripeStripe Checkout and billing pages may use cookies or similar technologies for payment, fraud prevention and checkout security.
Email importsShipping-label forwarding uses your email provider and does not require a Google OAuth connection or Google cookies in InventoryOS.
AnalyticsOur website delivery includes Cloudflare Web Analytics to understand page visits and performance. Cloudflare describes this as cookieless analytics without cross-site individual profiling. The animation libraries do not add their own analytics or advertising pixels. If additional non-essential analytics or storage is introduced, we will update this policy and obtain consent where required.
3. Why cookies and storage are used
- To keep you logged in and protect your session.
- To remember workspace, inventory and theme choices.
- To support billing, checkout and fraud-prevention flows.
- To support optional printing and dispatch integrations.
4. Your choices
You can block or delete cookies in your browser settings. Some essential parts of InventoryOS may not work correctly if you disable cookies or browser storage, including login, billing and workspace selection.
Where non-essential cookies or similar technologies require consent, we will offer a clear choice before using them. Refusing optional tracking will not prevent access to the public marketing information.
5. Updates
We will update this policy if InventoryOS adds analytics, advertising, tracking pixels, embedded third-party tools or other non-essential storage technologies.
6. Marketing animation and locally served assets
The marketing redesign uses GSAP, Lenis and React Bits for presentation and scrolling. They are bundled with the site, and the font is served from our own site. These animations do not need advertising cookies, a third-party analytics account or marketing pixels. Pointer effects use the pointer position to draw the effect in your browser; the redesign does not send those positions to InventoryOS or an advertising provider.
Reduced-motion preferences are respected. Links to Stripe, app login, email and external providers open those separate services when you choose to use them; their own notices apply there.
7. Retail PWAs, pairing and pending sales
Installed Retail apps can use service workers, cached app assets, browser storage and local databases for the requested app experience, store selection, device pairing, authenticated till sessions and pending cash-sale sync. These can include business and transaction data on a shared device. Use the relevant app sign-out or till lock and keep the device secure.
Clearing site data, uninstalling an app or resetting a browser can remove unsynced sales or device pairing. Sync pending records on the original device before doing so. Browser storage is not an independent backup of your business records.
InventoryOS Shop basket
The Shop saves product references, selected variants and quantities in local storage on your device so the basket survives page changes. A temporary checkout copy is kept in session storage to update that basket when you return. These records do not store card details, addresses or marketing email addresses. Clear the cart or your browser’s site storage to remove them.