Privacy, plainly.
How this marketing website handles information. Last updated October 20, 2026.
Scope of this notice.
This notice covers the NextStock marketing website. The NextStock application is a separate service where account and warehouse information may be processed. Review the app’s applicable terms and privacy information before providing operational data.
The interactive previews.
The warehouse preview uses sample data. Preview searches, calculator inputs and setup-guide choices are handled in page memory. An optional operation choice can appear in the setup-guide URL, browser history and technical hosting logs. No sales inquiry is created. A setup brief is generated in your browser and saved to your device.
Website delivery.
Vercel hosts this website and may process technical request information such as IP addresses, requested URLs and device or browser details to deliver, secure and operate the service. Its handling of that data is described in Vercel’s privacy notice.
Cookies and analytics.
When website analytics is enabled, PostHog measures visits and interactions such as page views and clicks. PostHog stores a random visitor identifier in a cookie. NextStock also sets an ns_analytics cookie on .nextstock.io for 90 days, holding that random identifier and your first visit’s campaign tags, referring site and landing page, so the app can connect a signup to the visit that led to it. Do not enter personal or confidential information into the sample previews or tools. Links to the separate NextStock app and external sites follow those services’ own practices.
Your choices.
You can explore the site without creating an account. Do not enter personal or confidential information into the sample preview. Leaving or reloading the page clears unsaved interactive changes, while URL parameters may restore initial planner selections. Use your browser and device controls to clear history or remove downloaded files.
Links to the app.
Signup, sign-in and demo links carry campaign tags (utm_source, utm_medium, utm_campaign, utm_content and utm_term), a referral label and the original landing-page path when available. A per-tab session-storage record keeps this context while you browse the site. Other query parameters are not copied. This helps connect a visit to its entry point. Browser storage restrictions may prevent context from persisting across reloads.