What we store

YakPack is a small open-source side project, not a company. This page describes exactly what the running app does with your data. If you self-host it, you are the one holding the data and this page describes your copy, not ours.

What an account stores

When you create an account, the database holds:

• Your email address and a hashed password, handled by Supabase Auth. We never see your password.
• A display name you choose.
• Your trip content — packing items, categories, what is checked off, and your itinerary.

That is the whole list. There is no profiling, no advertising, and nothing is sold or shared with anyone.

Your OpenAI key

If you add an OpenAI key to use the AI guide, it is kept in your browser and attached to each request you make to the AI. It is never written to the database, never logged, and is not readable by us. Clearing your browser storage removes it, and signing in on another device means entering it again.

Messages you send to the AI go to OpenAI under your own key and are covered by OpenAI's policies, not ours.

What leaves the app

• Open-Meteo receives the latitude and longitude of an itinerary stop to return a forecast. No account data is attached.
• OpenAI receives your AI messages, under your own key, only if you add one.
• Supabase hosts the database and authentication.
• Vercel hosts the site and collects anonymous traffic and performance measurements (page views, load timings). This is not tied to your account.

What your device stores

So the app keeps working without signal, your browser holds a cached copy of your pack list, plan and last known forecast, plus any check-offs made offline that have not synced yet. AI conversations are kept in your browser only. Clearing site data removes all of it.

Deleting your data

Ask for deletion through the repository's issue tracker or by contacting the maintainer, and the account and its trip content are removed. There is no retention period and no backup we hold on to afterwards.

Changes

If this changes, the date at the top changes with it. The history of this page is public in the repository.