Methodology

Privacy and local list storage

What stays in your browser, how to export it and how to remove it.

🔒 No account. Data stays local.

Illustration for: Privacy and local list storage

What stays in your browser, how to export it and how to remove it.

This page explains the assumptions, data and limits used by WalizkaTo. The goal is a result that is understandable and independently checkable.

The service does not hide its logic behind a score or artificial intelligence. You can change quantities, weights and limits, and exports preserve your own settings.

Time-sensitive information carries a verification date. Before travel, always check your booking conditions and official airline and airport notices.

What is stored locally

Practical rules

  • The browser keeps the current checklist, checked state, consent choice and a short-lived network-footer cache.
  • List content is not sent to a WalizkaTo server because the service has no user accounts or user database.
  • JSON export creates a file only after a user action and enables manual transfer between devices.
  • The delete button removes WalizkaTo keys without affecting data from other websites.

Key value moment

After a few inputs you get a result tailored to “privacy and local list storage” that can immediately be adjusted and saved.

Worked example

For a five-day trip with laundry, set five days, laundry after day three and carry-on. Then remove items supplied by the accommodation.

Limitations

The result does not replace airline conditions, manufacturer guidance or professional advice. Weight, use and capacity values are estimates.

Frequently asked questions

Do I need an account?

No. Lists, settings and history are kept locally in the browser.

Is the result binding for an airline?

No. A profile helps with planning, but you must check the conditions attached to your booking.

Can I edit the result?

Yes. Quantities, weights, categories and custom items can be changed before export.