Your wardrobe is personal.
Your data should be understood.

Your private cloud wardrobe

A free account is required for a personal wardrobe. Aara synchronizes clothing details, imported clothing photos, saved outfits, lookbooks, calendar plans, wear logs, and preferences with your private Supabase account storage. These records let you open the same wardrobe across devices, build outfits, and calculate wardrobe insights. Clothing photos use private storage with account ownership checks. Saving clothing to your wardrobe does not authorize AI processing.

Aara keeps an offline copy on each device to support viewing and editing when a connection is interrupted. A change is saved in the cloud only after synchronization succeeds; the app shows pending changes, errors, and confirmed cloud status. Earlier wardrobes created without an account remain separate until you explicitly import them into the displayed destination account. Imports preserve existing account pieces and offer choices for conflicting data. Sample previews stay separate and are never uploaded as your personal wardrobe.

Aara retains a separate device cache for each account, including changes waiting for a connection. These device records are not encrypted by Aara. Signing out switches away from that account; it does not erase its device cache. Only sign in on devices you trust. Clearing site data, using private browsing, or changing browsers can remove unsent changes. Use Account’s export and recovery actions to keep a copy. When two devices change the same record, Aara asks which version to keep.

In the native app, new garment photos are stored as files in the app’s document storage. A JSON record export is not a portable backup of those separate photo files.

Photos are a choice

You can organize garments, plan outfits, and record wears without adding a photo of yourself. The default clothing-photo preparation runs on your device. Saving a photo in a signed-in wardrobe synchronizes it privately, but does not automatically send it to an AI provider.

Optional garment enhancement requires a separate choice for each photo. It sends the selected clothing image through private Supabase storage to Google Gemini for suggested tags and an approximate cleanup. Use clothing-only photos; images containing people are rejected by the processing check. Aara preserves the original and offers it when enhancement is unavailable or fails quality checks. AI can misidentify a fabric, color or detail, so review the result before saving.

Personal-photo Studio features require separate consent, identity and age verification, and applicable eligibility checks. Current cloud AI processing is available only to adults aged 18 or older. Personal-photo features remain unavailable until their required verification services are connected. People aged 13–17 can use the free wardrobe and local photo tools. Aara is available from age 13.

AI output is not an identity guarantee. Provider handling depends on the Google project’s service tier and settings; Aara does not promise that an external provider keeps no data. See Gemini API terms before choosing cloud processing.

Optional text assistance

The AI assistant requires a separate agreement before sending a question to Google Gemini. It sends your question, a limited recent conversation history, and selected clothing details such as names, categories, colors, and fabrics. It does not send your clothing images or personal photos through this text feature. Avoid including sensitive information in your messages.

Text assistance is available only when your saved account preferences declare you are 18 or older. This is an age declaration, not independent identity or age verification. Your private account conversation is retained until account deletion. Gemini may make mistakes; review its styling suggestions before using them. Provider handling remains subject to the Gemini terms linked above.

Connected accounts and payments

Aara uses an email magic link to create or sign in to your free account. Account services process the email address you provide. The browser keeps the active account session in tab-scoped session storage, so a refresh or checkout return in that tab can stay signed in. Closing the tab ends that browser session. Native builds store session credentials using the device’s secure storage.

AI services, verification, and paid membership depend on the integrations enabled for the release. Aara displays an unavailable state when a required connection is missing. The free cloud wardrobe requires an account but does not require payment or a paid membership.

If web checkout is available, the payment provider displays the actual plan, price, billing terms, and payment form before you choose to pay. Payment details are entered through that provider’s checkout. Opening the membership screen or viewing a sample wardrobe is not a purchase.

Private help and support

Signed-in members can send requests through Help & support. Request titles, messages, replies and status are stored with your account and visible to authorized Aara support staff. Replies appear in your private inbox; check there for updates. Do not include passwords, payment details or personal photos. Account deletion removes these conversations. Minimal staff-action audit records may remain as described below.

Other connections on this site

This marketing site serves its typeface files from the same host as its pages. Fly.io receives the network information needed to deliver pages and images.

When an Aara Google Analytics property is connected, optional usage analytics loads only after you choose “Allow analytics.” It records a limited set of page and screen names, without your photos, email address, prompts, wardrobe details, or sign-in URL parameters. Advertising features are disabled. Your browser’s Global Privacy Control keeps analytics off. Use “Privacy choices” in the site footer or Account to change your choice; refusing analytics does not affect your wardrobe.

The app’s planner can request weather for a selected supported city. It sends the city’s forecast coordinates to the weather service; it does not need your clothing images for that request.

The editorial portrait and sample garment imagery shown here are AI-created examples. Sample clothing, profiles, plans, and wear history are demonstrations, not information about you.

What you can control

• Edit or remove wardrobe items, looks, and plans inside the app.
• Export your records and recover changes that have not synchronized from Account.
• Start a fresh wardrobe after confirmation. This replaces the current wardrobe records; it is not an account-deletion request.
• Sign out, keeping your private cloud account and its offline cache separate from other accounts and the sample preview.
• Request deletion of model photos, color analysis, and generated previews. This revokes photo consent without deleting your garment wardrobe or account.
• Delete your account through Account. Aara removes private storage and account records, cancels connected Stripe subscriptions when applicable, and confirms completion only after the service finishes. Interrupted requests can resume.

Apple or Google subscriptions must be managed with the relevant store before account deletion; Aara displays the applicable instructions. Deletion from Aara does not remove payment records a processor must keep, provider-side records governed by its terms, or copies you exported or shared. Some administration audit records remain to document privileged actions, with a deleted actor’s account reference removed.

Removing wardrobe records does not guarantee removal of every orphaned native image file, download, export, or backup copy. Copies you save or share outside Aara remain in the locations you chose.