Legal

Privacy Policy

Effective Date: June 23, 2026  ·  Last Updated: November 10, 2026

JetKit is a packing intelligence app. We collect what the app needs to work: your wardrobe photos, trip data, and account information. We also keep records of what you do in the app, saved with your account. Your closet photos go to OpenAI to identify your clothes, and if you import an outfit from a photo, that photo, which usually shows a person, goes to OpenAI so the clothes in it can be identified. The app asks you before either happens, and you can say no. If you connect an AI assistant such as Claude or ChatGPT to your account, it can read your trips, closet, and outfits, and it can add to them only when you confirm in a JetKit card. What the assistant reads also reaches the assistant's own provider. We also compile de-identified packing statistics across many travelers, which we may publish or license; you can switch your part in that off in Settings. We do not sell your data. We do not use your photos to train AI models.

1. Who We Are

JetKit ("JetKit," "we," "us," or "our") is an AI-powered travel wardrobe and packing intelligence application available on iOS, Android, and the web at jetkit.ai. JetKit is operated as a sole proprietorship.

If you have any questions about this Privacy Policy, contact us at info@jetkit.ai.

2. Information We Collect

We collect the following categories of information when you use JetKit:

Account Information

Wardrobe & Clothing Data

Trip & Packing Data

Location Data

Usage Data

Notifications

AI-Generated Insights

Messages You Send Us

Website Data (jetkit.ai)

Data Kept on Your Phone

3. How We Use Your Information

We do not use your photos or personal data to train AI models. Your clothing photos are processed by our recognition pipeline to extract attributes (category, color, style tags) and then stored securely in your account. Outfit photos used for outfit import are processed and not stored (see section 5).

4. Third-Party Services We Use

JetKit shares data with the following third-party services to operate the app and the jetkit.ai website, and to measure how the website is used:

Firebase / Google (Firebase Authentication, Firestore, Firebase Storage, Firebase App Check, Cloud Functions, Google Sign-In)

Your account data, clothing metadata, packing data, and AI insights are stored in Google Firebase, along with your usage records, Help form messages, email choice, subscription status, and scan count. Photos are stored in Firebase Storage. So are your import records and the pictures of each import (see section 5). Authentication is handled via Firebase Authentication, which also sends the password reset email when you ask for one. If you sign in with Google, Google confirms who you are and gives us your name, email address, and profile picture link. The app also attaches a Firebase App Check token to its requests to Firebase. The token is meant to show that requests come from the real app, and it holds no personal information. One Cloud Function, which is our own code running on Google's servers, passes each Help form message to our support inbox through Resend (see below). If you connect an AI assistant, you sign in through Firebase Authentication on a JetKit page, and the records of that connection (your agreement, the request counts, and the photo fingerprints in section 2) and your garment library records are stored in Firebase under your account. Google's privacy policy applies: policies.google.com/privacy.

Google BigQuery (Analytics Warehouse)

The de-identified packing events described under "Aggregated, de-identified packing insights" are copied from Firestore into Google BigQuery, a Google data warehouse, where we compute the aggregate statistics. BigQuery receives the same event records as Firestore holds: the one-way account code, a session identifier, the trip code, and the event's categories; never your account ID, name, email address, photos, or notes. Only JetKit reads the warehouse. Google's privacy policy applies: policies.google.com/privacy.

Apple and Google (Sign in with Apple, App Store, Google Play)

If you sign in with Apple, Apple confirms who you are, and the app asks Apple for your name and email address. If you subscribe to JetKit Pro, the purchase is made through your App Store or Google Play account. Apple or Google takes the payment, and we do not receive your card details. The app also opens the store's own pages when you choose to rate JetKit or manage your subscription. Apple's privacy policy applies: apple.com/legal/privacy. Google's privacy policy applies: policies.google.com/privacy.

OpenAI

Our server sends the following to OpenAI's API, and only after you have allowed it (the questions are described at the end of this entry). Nothing goes to OpenAI straight from your phone, and we send nothing to OpenAI to build packing plans.

We do not send OpenAI your name, email address, sign-in token, or the account ID itself, and a test on our server checks that none of these requests carries them. Each request does carry a one-way hashed identifier made from your account ID (not the account ID, your email address, or your name), so that OpenAI can detect abuse of its service, and OpenAI cannot reverse it to identify you. Every one of these requests, the photo requests and the text requests alike, is sent with OpenAI's setting that tells it not to store the request or the answer. The one exception is the request that draws a picture: OpenAI's image generation service has no such setting and refuses a request that carries one. For outfit import that request only ever receives the written description above, never your photo; for bulk imports and Redraw it receives an image instead, as described under "AI processing of your photos" in section 5. OpenAI's privacy policy applies: openai.com/privacy.

Before anything goes to OpenAI, the app asks you, in two separate questions, each the first time it is needed: once for your closet photos and the outfit text, and once for an outfit photo with a person in it. Saying yes to one does not open the other. If you say no, nothing is sent: you can still add items and type their details yourself, and the outfit generator still works with its own ranking and its own reason line. Only the AI scan, or the outfit import, stays off, and the rest of the app works as before. You can change either answer at any time in Settings (the switches are called AI clothing scan and AI outfit photo import). Your answers are stored with your account (see section 2). The AI clothing scan answer also governs photos you add through an AI assistant: with it off, the assistant's add-item card asks you to turn it on in the app and sends nothing.

OpenWeather

We use OpenWeather for weather data: the current weather at your location and at your trip destinations, and the weather for your trip's dates. To fetch it, the app or our server sends OpenWeather the place name or coordinates and, for trip weather, the trip dates. If you allow location access, your device's current coordinates are sent, at full precision, to show the weather where you are: from the app to our server, and from our server to OpenWeather. Versions of the app from October 30, 2026 on never contact OpenWeather from your phone: every request goes through our server. Versions from before October 10, 2026 ask OpenWeather themselves, and versions from October 10 to October 29, 2026 do so when they cannot use our server. Requests the app makes itself go straight from your phone, so OpenWeather also sees your device's IP address. When an AI assistant you connected asks for a packing plan or an outfit for a trip, our connector server asks OpenWeather about that trip's destination and dates in the same way, and checks that a destination you name is a place OpenWeather knows. No account information is sent to OpenWeather. OpenWeather's privacy policy applies: openweather.co.uk/privacy-policy.

Open-Meteo

When OpenWeather, asked for the weather for your trip's dates, does not answer in time or answers with a server error, our server (and our connector server, for an AI assistant you connected) asks Open-Meteo (OpenMeteo GmbH, Switzerland) for the same forecast instead. It sends Open-Meteo only the coordinates of your trip's destination: not your own location, your trip dates, or any account information. The request comes from our server, so Open-Meteo does not see your IP address. Open-Meteo deletes its server logs, which may include those coordinates, after 90 days. Open-Meteo's terms and privacy notice apply: open-meteo.com/en/terms.

Railway (Backend Hosting)

Our backend API servers are hosted on Railway. Request data passes through Railway's infrastructure, including the photos the app sends for recognition, your sign-in token, and, for the weather where you are, your device's coordinates. Our server does not keep photos on Railway. For an import, it saves the photo, the crops, and the drawn pictures to Firebase Storage (see section 5). While an import is being worked on, it also keeps your sign-in token in memory, never on disk and never in a log, so that it can ask our background removal service to cut out the pictures it draws for you (see Modal below). It also keeps, in memory for 24 hours, the AI's answer about a photo, under a fingerprint of the photo and your account ID, so that the same photo sent again is not sent to OpenAI twice. It does write log lines, which Railway keeps for its normal log retention period. These can include your account ID (when you delete your account, unsubscribe, or your subscription changes), the names, categories, and descriptions of items the AI recognized, the occasion and outfit mode of an outfit request, and a trip's destination and dates when a weather lookup fails. Our assistant connector (mcp.jetkit.ai) is also hosted on Railway. Its log lines name the tool an assistant called, how the call ended, how long it took, and a scrambled (hashed) tag for your account and for the assistant, never your account ID, email address, token, trip, or item. The recognition server's log lines for an item added through an assistant name a request ID or the item's ID and what kind of picture was made, never your account. Railway's privacy policy applies: railway.app/legal/privacy.

Vercel (Web App Hosting)

Our web application at jetkit.ai is hosted on Vercel. Standard web request logs may be retained by Vercel. When you join the waitlist, our website's server log on Vercel records that a sign-up was made and how it ended. It does not record the email address you entered. Until October 11, 2026 it did, and those earlier log lines last only as long as Vercel keeps logs. One exception remains: the unsubscribe link in a waitlist email carries your email address in encoded form, so when that link is opened, Vercel's request log may record it as part of the link's address. Closet photos you view in the web dashboard are fetched and resized by Vercel's image service. Vercel's privacy policy applies: vercel.com/legal/privacy-policy.

Vercel Web Analytics (Website Analytics)

Our website at jetkit.ai uses Vercel Web Analytics to count page views and see how visitors reach the site. It records the page visited, the referring page, and your browser, operating system, device type, and country. It does not use cookies: Vercel identifies a visit by a hash of the incoming request, discards that hash after 24 hours, and does not tie the data to any individual or IP address. It runs on every page of the website, including the pages you see when you are signed in, and not in the JetKit app. It loads whatever you choose on the website's cookie notice, and whether or not your browser sends a Global Privacy Control signal. Neither switches it off. We do not send it your name, email address, or account ID. The address of a page can contain the ID of a trip, a closet item, an outfit, or a share link. Vercel's privacy policy applies: vercel.com/legal/privacy-policy.

Google Analytics (Website Analytics)

Our website at jetkit.ai uses Google Analytics to understand how visitors use the site, such as which pages are viewed and how visitors find it. Google Analytics sets cookies in your browser and receives the pages you visit, the referring page, your browser and device type, and your IP address, from which Google derives an approximate location. It loads on every page of the website, including the pages you see when you are signed in, and not in the JetKit app. It loads unless you choose Decline on the website's cookie notice, or your browser sends a Global Privacy Control signal. Until you answer the notice it loads, so the page you are on when you choose Decline may already have been reported to Google. Choosing Decline switches Google Analytics off on that page, removes its cookies, and stops it loading on every later page. Your choice is saved in your browser, so it applies to that browser only. We do not send it your name, email address, or account ID. The address of a page can contain the ID of a trip, a closet item, an outfit, or a share link. Google's privacy policy applies: policies.google.com/privacy. Google explains how it uses information from sites that use its services at policies.google.com/technologies/partner-sites, and you can opt out of Google Analytics with Google's browser add-on at tools.google.com/dlpage/gaoptout.

YouTube (Videos on the Blog)

Some blog posts on jetkit.ai include a video. Opening one of those posts loads the video's preview image from YouTube (i.ytimg.com), and pressing play loads the player from youtube-nocookie.com. Both belong to Google and receive your IP address and browser details. Google's privacy policy applies: policies.google.com/privacy.

Modal (Background Removal Processing)

Clothing photo background removal runs on a service of ours hosted on Modal, a third-party cloud compute service. For each closet photo you add in the app, the app sends that service the photo, together with your sign-in token, and gets a cut-out picture back. This starts by itself after you add an item. Our own server also sends it the AI drawings it makes, to cut them out: with your sign-in token while our server still holds it from your own request (bulk imports and Redraw), or, for an item added through an AI assistant, with our server's own key and your account ID. In those cases the service receives the drawing, not your photo. The service accepts a request only with a valid sign-in token or our server's key. It holds the picture in memory while it works and does not store it. Modal's privacy policy applies: modal.com/legal/privacy-policy.

Resend (Email)

We use Resend to send email. Resend receives the address and the content of each email it sends for us:

Resend's privacy policy applies: resend.com/legal/privacy-policy.

RevenueCat

We use RevenueCat to manage in-app purchases and subscriptions. Your purchase history and subscription status are processed through RevenueCat to verify entitlements. So that a purchase can be matched to your account, the app gives RevenueCat your JetKit account ID. It does not give RevenueCat your name or email address. RevenueCat tells our server when your subscription starts, renews, changes, or ends, or when you buy closet scan credits, and we store the current status and a record of each notice with your account ID: the billing event log in section 2 (the kind of event, the product, the store, the time, and your account ID), kept for audit and deleted with your account. For scan credits we keep counts only, never a receipt. RevenueCat's privacy policy applies: www.revenuecat.com/privacy.

WorkOS (Sign-in for AI Assistants)

When you connect an AI assistant to JetKit, WorkOS runs the authorization handshake between the assistant and JetKit (the OAuth standard, through WorkOS AuthKit). You sign in on a JetKit page with your Google, Apple, or email account through Firebase, not at WorkOS. Once you have, our server tells WorkOS your JetKit account ID and your email address, and WorkOS keeps a user record with those two, plus the sign-in sessions and access tokens it issues to your assistant (an access token lasts about an hour). WorkOS does not receive your password, name, photos, closet, trips, or outfits. On each request from an assistant, our connector asks WorkOS which account the assistant's token belongs to, and remembers the answer briefly. Deleting your JetKit account ends every assistant connection, because the account the WorkOS record points to no longer exists. As part of the deletion, our server also asks WorkOS to end every session and token it issued for you and to delete your user record there (see section 6). WorkOS's privacy policy applies: workos.com/privacy.

Sentry (Crash Reporting in the Mobile App)

Preview and production builds of the phone app send crash reports to Sentry (Functional Software, Inc., sentry.io), a processor acting for JetKit, so we can fix crashes. Development builds and the web app send nothing, and builds of the app made before October 21, 2026 have no crash reporting at all. A crash report holds the error and where in the code it happened, the app version and build number, the device model and operating system version, the screen you were on, the time, and one word for the account type (user, admin, demo, or test), the same word our server uses in its own logs. Sentry also counts app sessions per version so we can see the share of crash-free sessions. The app may also send Sentry a diagnostic warning when one of its own configuration settings is missing at launch; the warning names only the missing setting and holds no personal data. A report never holds your name, email address, user ID, IP address, a photo, a closet item, a trip detail, your exact location, a screenshot, a request body, or console output: the app removes these before anything leaves your phone, and Sentry's own personal-data collection is switched off. Sentry keeps events for 30 days. Crash reports are not linked to an account and cannot be looked up by person. Our own testing (admin, demo, and test accounts) is reported under a separate internal label so it is kept apart from real users' numbers. Sentry's privacy policy applies: sentry.io/privacy.

Amazon (Shop Links)

When the app shows something you are missing, on a packing plan, the Intelligence tab or the Closet Optimizer, a Shop button opens an Amazon search page in a browser window inside JetKit.

The Shop button is an Amazon affiliate link. As an Amazon Associate, JetKit earns from qualifying purchases. The link carries only a search phrase and our affiliate tag; it does not include your name, closet or trip details. Once you are on Amazon, Amazon's own privacy notice applies and Amazon may set cookies on its site.

The search phrase may include your wardrobe style, such as men's or women's, and the type of garment the suggestion is about, such as "sweater". It never includes your name, photos, brands, sizes or trip details.

Before the page opens, the app saves a usage record of the tap (see section 2). Amazon's privacy notice is at amazon.com/privacy.

placeholder.com (Stand-in Images)

When a closet item has no picture, the app shows a stand-in image that it loads from via.placeholder.com. The request is the same for every user and holds nothing about you. Like any web request, it reaches that service with your device's IP address.

DiceBear (Mood Avatar Pictures)

The app's Harmony journal can show a small cartoon avatar for the mood of your latest entry. When a new entry's mood differs clearly from the one before it, the app fetches that avatar from DiceBear (api.dicebear.com), an open-source avatar service. The request carries only a mood word (happy, neutral, or sad), a background color picked from the entry's tone, and the picture size. It carries no seed, name, account ID, or words from your entry. Like any web request, it reaches DiceBear with your device's IP address. The picture is kept in the app's cache on your phone. DiceBear's privacy policy applies: dicebear.com/legal/privacy-policy.

We do not sell, rent, or share your personal information with advertisers or any third party for marketing purposes.

5. Photos and Image Processing

When you add clothing photos, they are processed through our AI recognition pipeline to identify garment type, color, and style attributes. As part of this process, your photo is sent to our server and on to OpenAI's API to perform the recognition, once you have allowed the AI clothing scan: the app asks the first time, and Settings has the switch (section 4 says exactly what is sent). Processed photos are stored in Firebase Storage and linked to your account. Background removal is processed via Modal, a third-party cloud compute provider, and starts by itself, with no question, whatever you answered about OpenAI. Recognition, once allowed, also starts by itself, with no further tap from you. That includes photos you added in bulk or on the website, which are processed the next time the app is open on your phone. If a clothing photo shows a person wearing the item, the person is part of what is sent. On the free plan, recognition stops once your free AI scans are used up. A photo you add through an AI assistant goes through the same recognition and the same drawing steps, on our server; see "Connecting an AI assistant" below.

For outfit recommendations, OpenAI also analyzes style attributes such as silhouette, pattern, texture, and aesthetic characteristics from your clothing photos.

Outfit import is different, and it is the most sensitive thing JetKit does. You choose or take a photo of an outfit, and the app asks for one where the person is clearly visible. The first time, the app also asks your permission, separately from the closet scan, and tells you that the whole photo, including the person's face and body and anything in the background, will go to OpenAI. If you say no, outfit import stays off and the rest of JetKit works as before. If you say yes, that whole photo, with the person in it, is sent to our server and on to OpenAI, which is asked to list every piece of clothing and every accessory the person is wearing. If the photo shows someone other than you, their image is sent too. For up to five of the pieces it finds, OpenAI's image model then draws a new product-style picture from a written description of the piece, and each picture is sent back to OpenAI once to check it. The pictures you keep are saved to your closet. They are drawn by AI, not cut out of your photo. The outfit photo itself is not stored by our server, in Firebase, or in your account. We do not use it to identify anyone, and JetKit has no face recognition feature.

Four other ways to import clothes are available to every account: Photo of my outfit, for a photo of you wearing the clothes; Clothes laid out or hanging, for one or more photos of several pieces (free accounts can send up to three photos per import); Screenshots from another app, for screenshots saved on your phone; and Film your closet, for a short video of your closet. The first time, the app asks your permission: for a photo of an outfit, with the same question as the Outfit photo import; for the other methods, with the closet scan's question. Screenshots show whatever was on your screen and are handled like photos: any text or other apps' content visible in them is sent too. For Film your closet, the video stays on your phone; the app reads a few still frames from it and sends those, like photos, to OpenAI, and your hand may appear in them. Each photo, screenshot, or still frame is sent to our server and on to OpenAI, which lists the pieces in it, where they are, and whether a person is with them. Our server then cuts each piece out of the photo (its crop). Each crop goes back to OpenAI once, to check that the piece is really there, and then to OpenAI's image model, which draws a new product-style picture of that piece alone from it. A crop from a photo of an outfit can show part of the person, such as a hand, skin, or the face; the model is told to leave the person out of the picture it draws. The photo itself is kept in Firebase Storage only while the import is being worked on, and deleted when it is done. A crop that can show a person is deleted once the clean picture exists, or when you save or discard the piece. Other crops, drawn pictures, and their cut-outs are kept with the import's record for 30 days after it ends, and the pieces you save are copied into your closet and stay until you delete the item or your account. Each import counts as one AI scan; if nothing is found, the scan is given back.

One further import method, importing from a screen recording, exists in the app but is available only to administrator and demo accounts today, not to regular users. The recording stays on your phone; the app reads a few still frames from it and sends those, like screenshots, to OpenAI. A frame of a recording is sent whole, with whatever else was on your screen. If it is opened to every account, this policy will say so first.

A profile photo you add in Settings is stored in Firebase Storage. It is not sent to OpenAI or Modal.

Your photos are never shared with third parties for advertising purposes, and we do not use your photos to train any AI or machine learning model.

AI processing of your photos

When you add clothing to JetKit, we use artificial intelligence to identify each item and create a clean picture of it.

What we send. Photos, still frames from videos, screenshots, and outfit photos you upload are sent to OpenAI, our AI provider. OpenAI uses them to detect clothing items, describe them (for example, type, color, and pattern), and draw a new, clean image of each item. For some plain basics on the free plan, we make the clean image ourselves on our own server from a stock picture of that kind of garment, recolored to match your item, and nothing is sent to OpenAI for that picture. If you use Redraw, we send the item's existing JetKit image to OpenAI to create a new version. Some images may also be processed by our own background-removal service, hosted by a cloud provider.

People in photos. Outfit photos may show you or other people. We instruct the AI to draw only the clothing, and we do not keep images of people as closet items.

How long we keep it. Once a clean image is saved to your closet, we delete the cropped piece of your original photo used to make it. Files from bulk imports (photos, videos, and screenshots) are usually deleted automatically within 30 days, and no later than 60 days. Photos you add one item at a time are kept in your closet as your original image until you delete the item or your account.

How OpenAI handles it. OpenAI processes this content to provide the service to us. Under OpenAI's API terms, data sent through its API is not used to train its models by default.

Screenshots from other apps. If you import screenshots from another app, we use them only to identify your items and create new images, and we do not save the original screenshot images to your closet. A screenshot shows whatever was on your screen and is handled like a photo: any text or other apps' content visible in it is sent to OpenAI too, and the crops are deleted once the clean picture exists.

Connecting an AI assistant

You can connect your JetKit account to an AI assistant that supports connections of this kind, such as Claude, ChatGPT, or Meta Muse, so that you can ask it about your trips and closet and have it plan with them. The connection is optional. Nothing in this section happens unless you set one up.

How you connect. The assistant opens a JetKit sign-in page. You sign in there with the Google, Apple, or email account you use in the app, or create one. By continuing on that JetKit sign-in page, you agree to our Terms of Service, to this policy, and to JetKit sharing your trips, closet, and packing plans with your assistant. Nothing starts until you continue. An email sign-in must have a verified address. If you have no JetKit account yet, connecting creates one with the same details the app's first sign-in writes: your account ID, your email address, and, when your sign-in provides them, your name and profile picture link. We record your agreement with your account (see section 2) and, the first time each assistant uses the connection, which assistant it was, read from the assistant's registered address (Claude, ChatGPT, Gemini, Copilot, or "other").

What the assistant can read. Through the connection the assistant can read your trips and the packing plan the app saved for each, your closet items (name, category, color, material, pattern, brand, tags, and when you added them) with a small picture of each, your saved outfits and signature looks, and the settings that shape a plan: packing mode, wardrobe style, temperature unit, time zone, and home city. It can also ask our connector server to compute packing plans, checklists, swaps, and outfits for you, with the same rules the app runs on your phone and, for the weather, the same OpenWeather and Open-Meteo lookups (section 4). Item pictures reach the assistant as small thumbnails, through links that work for 10 minutes and name no account or item, or inside a JetKit card shown in the assistant. The assistant never receives your original photos or the permanent addresses of your pictures.

What the assistant can change, and only with your confirmation. On your request, the assistant can prepare a new trip, a change to a trip or its deletion, a new outfit or look, a change to one or its deletion, and a new closet item from a photo. Each of these is a preview in a JetKit card: every field is editable, and nothing is written until you tap the card's button yourself (a deletion asks for a second tap). The tools that save, change, or delete are reachable only from the card you tap, not by the assistant. Nothing done through an assistant can edit an existing closet item, change a saved packing plan, or touch your account, your settings, or your subscription. An assistant that cannot show JetKit cards can read and plan but cannot save anything.

Photos you add through an assistant. The add-item card lets you pick a photo of one garment from your device. The card sends it to our connector server, which passes it to our recognition server. There it is re-encoded (its metadata removed, at most 1600 pixels on its longest side) and recognized with OpenAI exactly as the app's AI clothing scan recognizes a photo, behind the same gates: your AI clothing scan permission must be on (set in the app's Settings), the free plan's closet limit applies, and one AI scan is used. The photo is held in our server's memory for 10 minutes while you check what was recognized. When you tap Add to my closet, the item is saved and gets its picture the way an imported item does: a plain basic on the free plan may get a recolored stock picture, and everything else gets an AI drawing of the item alone, made by OpenAI's image model from your photo and the item's description, then cut out by our background removal service on Modal (which receives the drawing, not your photo). Your photo stands in as the item's picture only until the drawing is ready, and is then deleted. If no drawing can be made, the photo is deleted anyway and the item gets a stock picture or no picture. When the item gets a stock picture, your photo is kept as the item's original picture, as the app keeps a photo you add one at a time. A photo that shows a person never gets a stock picture and is never shown as a closet picture. A fingerprint of each photo, with what JetKit recognized in it, is kept for 30 days so the same garment of the same photo is not added twice (section 2).

The assistant's own provider. Everything the assistant reads from JetKit, your questions, and the answers it gives you pass through the assistant's provider: Anthropic for Claude, OpenAI for ChatGPT, Meta for Muse, or the company behind the assistant you use. Their own privacy policy and settings govern what they keep and for how long, and we do not control that. We learn which assistant is connected and keep a scrambled tag for it in our logs (section 4, Railway), and nothing more about it.

Limits. Each linked assistant may make 60 requests an hour and 500 a day for your account, and assistants may save at most 10 new trips and 10 new outfits a day for you. These counts are kept with your account.

How to disconnect. Remove JetKit in your assistant's connector or app settings (in Claude: Customize, then Connectors, then JetKit, then Remove). From then on the assistant no longer makes requests for your account; an access token it held lasts about an hour from when it was issued. To have us end a connection from our side, email us. Deleting your JetKit account ends every connection, because our server refuses an assistant whose account no longer exists, and removes your agreement record, the request counts, and the photo fingerprints with the account. The user record and sessions WorkOS keeps for the connection are deleted with the account too (section 4 and section 6).

Aggregated, de-identified packing insights

JetKit learns what travelers pack, as a group, so that we can make packing lists better and publish general findings about travel wardrobes (for example, "travelers to Lisbon in March pack an average of five tops, and one in three take only a carry-on"). This section describes that program. It started with app versions from November 7, 2026.

What we record. When you plan a trip, generate or edit a packing list, add or correct an item in your closet, accept or reject an outfit, tap a shopping suggestion, or answer the question about what you wore after a trip, the app records the decision as an event. There are thirteen kinds: a trip created, a trip updated, a packing plan generated, an item added to a plan, an item removed from a plan, an item swapped in a plan, a closet gap shown, a shop link tapped, an outfit accepted, an outfit rejected, a closet item created, a closet item corrected, and post-trip feedback. Each event carries only general categories:

What we never record in these events. Your name, email address, photos, free-text notes, item names, item IDs, exact location or coordinates, or your account ID. Your account is represented by a one-way code (a keyed hash) that our server computes with a secret held only on our servers; the app never sees the secret, the code cannot be turned back into you without it, and we never share the code or the secret. A trip is represented the same way. Our server refuses any event that carries a field it does not expect.

How we use these events. We copy them into Google BigQuery (section 4) and combine them across many travelers to compute aggregate statistics: which garment categories are packed for which destinations and seasons, which items travelers are commonly missing, how far ahead trips are planned, how much of what is packed is worn, and what brand and material mixes closets contain. We use these aggregates to improve JetKit's packing engine, we read them in a weekly internal summary, and we may publish or license them, for example to hotels, travel brands, airlines, and the press.

The minimum cohort rule. No statistic is computed, shown, published, or licensed unless at least 50 distinct trips stand behind it. Groups smaller than that are not reported at all, so no figure we publish can describe a single traveler or a small group. Only aggregates ever leave JetKit; the event records themselves stay inside JetKit's systems.

Your choice. This is on by default. You can turn it off at any time in the app under Settings, with the switch "Contribute anonymized packing insights". When it is off, the app records no new events from your account, and our server refuses any that still arrive. Turning it off does not delete events already recorded, and it does not affect any JetKit feature.

Retention and deletion. Events stay in our database and in the warehouse until you delete your account. When you delete your account, our server computes your account's code and deletes the events under it from our database. The warehouse keeps a history of what was copied into it, and that copy is not removed by account deletion today; it holds the one-way code and the event's categories, nothing that names you. Aggregates already computed are not affected, since they describe groups, not you.

Legal basis (EEA and UK). We process these events on the basis of our legitimate interest in improving JetKit and understanding travel wardrobes as a whole, with the safeguards above (de-identification, the minimum cohort rule, and the switch). You can object by turning the switch off.

6. Data Retention

We retain your data for as long as your account is active. A few things are removed on a timer: the records and pictures of an import, 30 days after the import ends, or 30 days after it started if it never finished (see section 5), and 30 days more when a closet item is still waiting for one of the import's pictures; the AI's answer about a photo that our server keeps in memory, after 24 hours; a push token, when the delivery service reports that the phone no longer accepts notifications; and the photo fingerprints for items added through an AI assistant, after 30 days (section 2). Everything else is kept until you delete it or delete your account.

You can delete your account in the app: open Settings and choose Delete account. The website has no delete button, so use the app or email us. If you delete your account, we will delete your personal data, wardrobe photos, and trip data from our active systems within 30 days. Deletion starts as soon as you confirm, and it covers:

Some things are outside what deleting your account can reach:

To ask us to remove any of these where we can, email info@jetkit.ai with the subject line "Data Deletion Request."

Deleted data can persist in our encrypted backups for a while after that: up to 14 weeks in the backups of our database, and up to 90 days in the backup copy of our photo storage, after which it is gone. A daily export of account records, including hashed credentials, is kept for 30 days as part of our backups; a deleted account drops out of it at the next export. We do not use backups to restore a deleted account.

7. Your Rights

Depending on where you live, you may have the following rights regarding your personal data:

Some of these you can do yourself in the app today. You can correct your name, profile photo, home city, closet items, and trips. You can delete single items, outfits, and trips, or your whole account (Settings, then Delete account). You can turn tips and updates emails off in Settings or with the unsubscribe link in any of those emails. You can switch the AI clothing scan and the AI outfit photo import off, or back on, in Settings; off means nothing more goes to OpenAI. You can disconnect an AI assistant in that assistant's settings, which ends the sharing you agreed to when you connected it. Location, camera, and photo access are controlled in your phone's settings. For everything else, email us. That includes a copy or an export of your data and a change to your account email address. You can turn the de-identified packing events off in Settings with the switch "Contribute anonymized packing insights"; off stops new events but does not delete the ones already recorded (see "Aggregated, de-identified packing insights"). One thing cannot be done today: the usage records in section 2 that are saved with your account ID cannot be switched off. The app has no setting for them, and they are saved whenever you use the app while signed in. Deleting your account removes them (see section 6).

To exercise any of these rights, email us at info@jetkit.ai with the subject line "Privacy Request." We will respond within 30 days.

8. US State Privacy Rights (California and Other States)

If you are a resident of California, Virginia, Colorado, Connecticut, Utah, Oregon, Texas, or another US state with a comprehensive privacy law, you may have rights under that law, including the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA). These rights include the right to know what personal information we collect, the right to delete it, the right to correct it, and the right to opt out of its sale or sharing.

We do not sell personal information, and we have not sold or shared (for cross-context behavioral advertising) any personal information in the preceding 12 months. Our website detects the Global Privacy Control (GPC) signal. When your browser sends it, Google Analytics does not load on the website, whatever you chose on the cookie notice. The signal stops Google Analytics only: it does not switch off Vercel Web Analytics, which uses no cookies (see section 4). You can also opt out of Google Analytics by choosing Decline on the cookie notice, or with Google's browser add-on linked in section 4.

We will not discriminate against you for exercising any of these rights. To submit a request, contact us at info@jetkit.ai.

9. Children's Privacy

JetKit is not directed to children under the age of 13. We do not knowingly collect personal information from anyone under 13. If you believe a child under 13 has provided us with personal information, please contact us at info@jetkit.ai and we will delete it promptly. For users in the European Economic Area and United Kingdom, the applicable age threshold under GDPR may be as high as 16 depending on your country of residence; if you believe a user under that age has provided us with personal information, contact us at info@jetkit.ai and we will delete it promptly.

10. Data Security

We implement industry-standard security measures to protect your data, including:

No method of transmission over the internet is 100% secure. While we take reasonable steps to protect your information, we cannot guarantee absolute security.

11. International Data Transfers

JetKit is operated from the United States. Your data is stored and processed in the United States via Google Firebase, Google BigQuery (de-identified packing events only), OpenAI, and our Railway-hosted backend servers. WorkOS (the sign-in records for AI assistant connections) and Sentry (crash reports, in Sentry's United States region) are United States companies. Open-Meteo (the coordinates of your trip's destination, when it stands in for OpenWeather, section 4) is a Swiss company, OpenMeteo GmbH. Where we transfer personal data from the EEA, UK, or Switzerland to the United States, we rely on recognized transfer mechanisms, including the EU-US Data Privacy Framework (DPF) for vendors certified under that framework (e.g., Google/Firebase and OpenAI, subject to their current certification status) and Standard Contractual Clauses (SCCs) where DPF certification does not apply. You can verify current DPF certifications at dataprivacyframework.gov.

12. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will update the "Last Updated" date at the top of this page. For material changes, we will notify you via email or an in-app notification. Continued use of JetKit after changes take effect constitutes your acceptance of the updated policy.

13. Contact Us

JetKit

333 NE 24th Street

Miami, FL 33137

Privacy inquiries: info@jetkit.ai

Website: jetkit.ai

For data deletion requests, use subject line: "Data Deletion Request"