Current approach
Packminder uses browser storage to provide the service. Optional first-party product analytics only starts on a browser after you choose to allow it. Packminder does not currently use third-party advertising cookies.
Functional storage
- Local storage: can hold the current trip and checklist recovery data, theme, guest packing preferences, a first-party analytics visitor identifier and other product state needed to keep Packminder consistent between visits.
- Session storage: can hold session-specific product state, temporary account-flow information and a first-party analytics session identifier.
- IndexedDB: stores travel-document files you deliberately add to the Documents area. Those file contents remain local to that browser/device and are not intentionally uploaded by the Documents feature.
- Authentication storage: Supabase uses browser storage needed to keep you signed in and maintain your authenticated session.
Optional first-party analytics
If you allow analytics, Packminder records first-party product analytics such as qualified visits, page views, broad acquisition source, device/browser category, broad country code, engagement time and list generation. A persistent browser identifier is used to avoid counting the same consenting browser repeatedly because of refreshes or additional tabs and to exclude known Admin/internal browsers.
Packminder does not use the analytics event stream to store raw trip prompts or uploaded travel-document contents, and it does not use this analytics identifier for advertising or cross-site tracking.
Analytics choice
Product analytics is off until you actively allow it on this browser. You can withdraw that choice at any time. Functional storage needed for trips, documents, preferences or sign-in is separate and can still be used whether analytics is allowed or not.
Travel-document storage
Packminder may ask the browser to keep document storage persistently where that capability is available. Persistent browser storage reduces the chance of automatic eviction but is not a guarantee. Clearing site data, resetting the browser/device or other browser/device behaviour can still remove local copies.
Third-party services
Authentication, payment, weather and other requested features may involve third-party services. Those services can set or use storage under their own domains when you interact with them, for example during Google sign-in or Stripe-hosted checkout. Their own privacy and cookie notices apply to those external pages.
Your controls
You can clear Packminder storage using browser settings. Doing so may sign you out, remove locally stored trip/checklist state, reset preferences and analytics identifiers, and permanently remove local document copies from that browser.
Changes
If Packminder introduces advertising, new non-essential tracking or materially different storage, this page and the relevant consent experience will be updated.