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 and does not appear on your other devices. It leaves the phone only when you share a trip that shows it, when you tap Packlier Style, or, signed in, when Smart match names it; both are below.

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 before launch, to tell you the app was out. A message sent from the support page is stored with the address you gave so that we can answer it. 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.

To show a photo of where a trip is going, the app sends the destination’s name, and nothing else, to Wikivoyage, Wikidata and Wikimedia Commons, and loads the photo from Wikimedia’s servers. The request carries no account identifier. Each answer is kept on your phone so a place is asked about once. The photos belong to their photographers, who are named under each one with its license.

If you tap Packlier Style on a wardrobe photo, that photo is sent once, through a Packlier server function, to OpenAI, which draws the same garment again in the style of our catalog and sends the picture back to your phone. Packlier stores neither the photo nor the picture. OpenAI does not train its models on it and keeps the request for up to 30 days to detect abuse, then deletes it. We keep a record that a restyle happened, when, what it cost and whether you reported the result, so that your allowance can be counted. It needs an account, and nothing is sent unless you tap the button.

When you are signed in and add a wardrobe piece from a photo, a small copy of that photo (768 pixels on its long side) is sent once, through a Packlier server function, to OpenAI, which says what the piece is, which catalog piece it is most like and what color it is. Only those words come back. Packlier stores neither the copy nor the answer, and OpenAI does not train its models on it and keeps the request for up to 30 days to detect abuse, then deletes it. We keep a record that a photo was matched, when, how many pieces were found and what it cost, so that your monthly allowance can be counted. Signed out, nothing is sent and you say what each piece is yourself.

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.

We count what people do in the app and on this website — a trip solved, a screen opened, a shared link viewed — with PostHog, and we collect crash reports with Sentry. The counts and crash reports carry nothing you wrote or chose: no destination, no traveler names, no garment you typed in and no photograph. A trip is reduced to its shape, such as four nights and two travelers. This website stores a PostHog cookie so a returning visit is not counted as a new one. Nothing is used for advertising.

To find the places where the app is confusing, PostHog also records about half of all sessions in the app, as a series of screenshots with your taps. Unlike the counts, a recording shows what was on screen, so it can include trip names, destinations, traveler names and the names of garments. Every photo and anything you are typing is blanked out on the phone before a recording is sent, and app logs are not included. Recordings carry the same anonymous or account id as the counts, are watched only by us to fix problems, and are deleted after 90 days at most. Write to us and we will delete yours sooner.

No advertising identifiers, no cross-app or cross-site tracking, no profiles sold or shared with anyone, and no ads. The app does not link to retailers.

The app works signed out. Trips are then stored on the device. What leaves it is the climate lookup, and the counts, crash reports and recordings described above, which are tied to an anonymous id rather than to you.

Delete a trip and it is removed from your account. Delete the account itself from the account screen in the app, or at packlier.com/account/delete without the app, and it is removed at once along with every trip, traveler, shared link and shared photo in it; backups follow within 30 days. Photos of your own garments stay on the phone that took them, and a subscription is canceled in the store that sold it, not by deleting the account. If you cannot sign in, write to us from the address on the account and we will delete it for you. Signing out only clears the device.

On Supabase infrastructure in the United States, with the counts, recordings and crash reports above held by PostHog and Sentry, and Packlier Style and Smart match requests handled by OpenAI, also 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.