Privacy policy

A destination, dates, the travelers you added with their ages, the palette and the garments in the grid. Trips are stored in your account so they open on any device you sign in to. Access is enforced per account at the database level; one account cannot read another’s trips. A photo you take of your own garment stays on that device; it is never uploaded, so it does not appear on your other devices and we never see it.

It is the only credential we hold. We use it to send sign-in codes, to reply when you write to us and, if you joined the waitlist, to tell you when the app launches. There is no password.

If you sign in with Google or Apple, we receive the email address on that account and a token confirming it is yours. Nothing else is requested.

Your destination and dates are sent through a Packlier server function to Visual Crossing, which returns the forecast or the seasonal normals for those dates. The request carries no account identifier, and Visual Crossing never sees who asked. If it fails, the app calculates a fallback on the device and nothing is sent.

Google Play and the App Store handle payments in the app. We never see a card number. We are told whether a subscription is active and when it renews.

No advertising identifiers, no third-party analytics in the app, and no sale or sharing of data. The app does not link to retailers.

The app works signed out. Trips are then stored on the device and nothing leaves it except the climate lookup.

Delete a trip and it is removed from your account. Ask us to delete the account and we remove it and its trips, including backups, within 30 days. Signing out only clears the device.

On Supabase infrastructure in the United States. If that changes, this page will say so before it does.

Accounts are for adults. A child in your party is stored as a first name and an age, used only to choose clothes. We do not knowingly create accounts for children under thirteen.