Privacy Policy

The short version

• Your garment photos and your whole wardrobe live in a private database on your phone.
• Garment recognition runs on the device. Photos are never uploaded for tagging.
• An account is optional. If you create one, the only personal data stored is your email address and a generated user ID.
• Without an account, nothing is uploaded at all. Signing in turns on closet backup — that is what the account is for.
• AI trip packing is the one feature that uses a server. It sends garment attributes as text — no photos, no names, no email address.
• There is no analytics, no tracking, no advertising, and no crash-reporting SDK in the app. Nothing is sold or shared with data brokers.

Who is responsible

Fullwear is made and operated by Josua Kohler, an individual developer based in Switzerland. Fullwear is not a company. For anything in this policy, including data-protection requests, write to support@fullwear.app.

What stays on your device

The following is stored in Fullwear's private app sandbox, in a local SQLite database. If you are not signed in, none of it is uploaded anywhere:

• Your garment photos.
• The attributes derived from them: category, colour, pattern, material, season, formality, and fit.
• Your wear history and outfit feedback.
• Saved trips, style rules, and inspiration lists.

Deleting the app removes all of it from the phone.

On-device AI

Garment recognition uses two AI models: a vision-language model (Qwen3-VL-2B) and an image-embedding model (CLIP ViT-B/32). They are downloaded once — around 1.5 GB in total — and after that they run entirely on your phone.

Your photos are never sent anywhere for tagging.

Optional account

You can use Fullwear without an account. An account is needed only to unlock Pro features and to sync a backup between your devices.

Sign-in options are Sign in with Apple, Google, or a one-time code sent to your email address. The account is hosted on Supabase in the EU, in the eu-west-1 (Ireland) region.

What the account stores

• Your email address.
• A generated user ID.

Fullwear never stores a password of yours.

Optional closet backup

Backup is what an account is for, so it is active whenever you are signed in. A snapshot of your closet data and your garment photos is uploaded to the developer's Supabase project — a Postgres database and a storage bucket — and kept in step as your closet changes. There is no separate switch to turn it on.

Access is restricted per user at the database level: each account can read and write only its own rows and its own photo folder.

If you do not create an account, none of your photos or closet data is uploaded. Signing out stops the backup, and deleting your account removes what was uploaded.

AI trip packing

AI trip packing is a Pro feature and the one part of Fullwear that needs a server.

When you generate a packing plan, the app sends a compact text list of your wardrobe attributes — plus your trip parameters, such as where you are going, for how long, and what you will be doing there — to a Supabase Edge Function operated by the developer. That function calls the Anthropic Claude API to produce the plan.

• No garment images are sent.
• No personal identifiers are sent — no names, no email address.
• Anthropic does not use API inputs to train its models.

Location and weather

Outfit recommendations use the real forecast, so Fullwear asks for your location. With your permission it reads the device's approximate location — low accuracy — and sends those coordinates to Open-Meteo (open-meteo.com) to fetch the local forecast.

Open-Meteo requires no API key and receives no identifier of any kind. It receives coordinates and nothing else.

Your location is also used to pick the app's default language.

Declining location permission is fine. The app then falls back to a default temperature.

Subscriptions and payments

Purchases are processed by Apple. The developer never sees your card or payment details.

RevenueCat manages subscription state on the developer's behalf. It receives your Supabase user ID and your purchase and subscription record. No email address and no name is sent to RevenueCat.

Notifications

The morning reminder is scheduled locally on your device. There is no push server behind it, and no device token is transmitted anywhere.

Analytics and advertising

There is none. Fullwear contains no analytics, tracking, advertising, or crash-reporting SDK. No data is collected for advertising purposes, and no data is sold or shared with data brokers.

Third parties

These are all of the outside services involved, and exactly what each one receives.

Google also appears here if you choose to sign in with Google: the sign-in is handled by Google, and the resulting account stores the same email address and user ID as any other sign-in method.

Legal basis for processing

• Contract performance — running your account, backing up your closet to it, and running your subscription.
• Consent — location access. You can withdraw it at any time in iOS Settings. Creating an account is itself the consent for the backup; signing out or deleting the account withdraws it.
• Legitimate interest — keeping the service working.

Retention and deletion

• On the phone: deleting the app removes all on-device data.
• Your account: deleting the account removes the account and the uploaded backup, photos included.

Account deletion is available inside the app, in the Profile tab. That is the primary route. If you cannot reach it, email support@fullwear.app from the address on the account instead. Full instructions are on the delete your account page.

Children

Fullwear is not directed at children under 13 and does not knowingly collect their data.

Your rights

If you are in the EU or EEA, the GDPR applies to you. If you are in Switzerland, the revised Federal Act on Data Protection (nFADP) applies. Either way you have the right to:

• access the data held about you,
• have it corrected,
• have it deleted,
• receive an export of it,
• and object to processing.

Send requests to support@fullwear.app. They are answered within 30 days.

Changes to this policy

If this policy changes, the updated version is published on this page with a new "last updated" date.