Chara Privacy Notice

Updated November 10, 2026 · Provider: LOLITA LTD

Your local wardrobe

You can use the wardrobe without an account. Clothes, notes, prices, outfits, wishes, wear records, and the photos you add to them are stored in the app on your device. They are not automatically uploaded or synced when you sign in. A local backup is created only when you request one. Files you export or save elsewhere are handled by the destination you choose.

Feed drafts and the media copied into them are stored separately on your device. Saving a draft does not upload it or move wardrobe data to your account. Feed drafts, copied media and saved-post IDs are not included in the wardrobe backup. When you open a saved post, the app checks whether it is still available from Feed.

Optional garment details, color tags and storage-place notes belong to your wardrobe. Wardrobe style and color summaries and wardrobe-based achievement progress are calculated from records on the device; they are not a separate upload of your wardrobe. Published-post progress uses the service's count of your own published posts.

Document text recognition

Android document text recognition is optional. When an eligible adult manually selects a document, Chara processes the image and recognized text on the device; Chara's recognition flow does not send either to Google. The Android ML Kit SDK may send its own performance, usage and diagnostic metrics to Google and may connect for SDK maintenance or model compatibility. These SDK metrics are separate from the image and recognized text processed by Chara. On iPhone and iPad, Chara uses Apple's on-device Vision framework.

Accounts and age eligibility

Chara processes your email address and account identifiers to provide sign-in, recovery, and account features. Account and Feed eligibility use the age range and country or region you declare in the app. Chara asks for an age range, not a full date of birth, for this check. Your declaration is not identity verification, verified age, or parental consent.

Feed age requirements vary by country or region. The app's eligibility logic starts at age 13 in some supported regions and uses higher minimum ages elsewhere. Some regions also require a compatible platform age signal or another approval step. If a region is not supported or a required check is unavailable, Feed access remains blocked. Use the eligibility and consent information shown in the app for your account and location.

Public profile

Your service-assigned UID, username, and display name, plus any avatar, short bio, or Instagram or TikTok link you choose to add, can be visible to people who view your public profile. Your email address, declared age range, residence region, and wardrobe are not shown on your public profile. Your wardrobe is not published when you sign in.

Feed drafts and submissions

You can browse public Feed posts without signing in. An account is required to submit a post, edit a public profile, or use account actions. A saved Feed draft stays on your device. When you submit a post, Chara sends the text and details you entered and the photos or video you selected. A selected avatar is uploaded when you save it for your public profile. Submissions go through media inspection and human editorial review; only approved posts may be published. Publication is not guaranteed. Product recommendations and magazine articles are reserved for authorized editorial accounts.

Searching Feed sends your search terms to the Feed service.

Selected photos or videos can include information embedded in the file, including GPS location. Chara can receive that information with a selected original even though the app does not request device location permission. A selected video may also contain an audio track; Chara does not separately record audio for Feed. Processing a display copy does not mean the submitted original never contained embedded information.

Service providers and media storage

Supabase provides authentication and stores account and relational Feed records. The Supabase project is configured in North Virginia, United States. Resend sends account verification and recovery email. Cloudflare Workers handle account-service requests and authorized Feed media transfer. Feed media is stored in private Cloudflare R2. Older app versions and historical media may continue to use private Supabase Storage.

Source originals, verified display outputs, and card images are separate files. A private storage bucket is not publicly browsable. For a post that remains published, Feed serves only its verified display output or card image; it does not serve the source original. Cloudflare processing, delivery caches, provider logs, and backups may be handled outside the Supabase database region. The North Virginia location does not promise that every log, email, cached copy, or backup stays there. Providers may process connection and request information such as IP address, timestamps, and authentication events.

Reports, blocks, and review records

A report can include your account identifier, the post or public profile you reported, your reason, details or supporting material you provide, and timestamps. A profile report may retain a limited snapshot of the public profile fields and avatar reference as they appeared when reported. Reporting does not automatically remove a post or profile. Blocking an author hides that author's posts from your Feed results. Restricted review and moderation records may remain while they are needed to handle a case or verify cleanup.

Removing posts and media

When you retract a post, Chara removes it from Feed and begins cleanup of its stored media. A cleanup may remain pending while Chara verifies the exact stored files and any delivery-cache purge. A request receipt does not prove that every step has finished. Unsubmitted uploads and media attached to rejected posts become eligible for a separate cleanup process after seven days. Seven days marks eligibility for cleanup; it is not a promise that deletion occurs at that exact time. This rule does not delete local drafts, published posts, reports, moderation records, provider logs, or backups.

Feed images may be held briefly in delivery caches or in a link already issued. Removing a post stops new delivery through Feed after the service's checks and cleanup, but temporary copies may take time to expire. Copies saved by other people or services are outside Chara's control.

Deleting your account

After an account-deletion request is accepted, the account becomes unavailable for further activity and new public Feed reads while deletion is processed. Chara removes the account's hosted posts, profile, related account records, and associated Feed media; the authentication identity is removed after the hosted cleanup is verified. If processing is interrupted or a removal cannot be confirmed, the request remains pending. Chara does not promise an exact completion time or immediate physical removal of every provider backup, operational log, cache, or external copy.

The requesting device also removes app-managed data belonging to that account when the app can verify and process the deletion. Guest data and another account's data are not removed. Original photos in the system photo library and files already exported elsewhere are not deleted. An offline device can complete local cleanup only after the app runs and checks the account's deletion state.

When the public account-deletion page is available, it supports existing email-and-password accounts; accounts that can sign in only with Apple cannot use that page. The page needs to save a status code in your browser before sending a request. Keep that code and check the status; a request receipt does not mean deletion is complete.

Contact

For privacy questions or requests, contact community@lolitafetch.com. Start with a short description. Do not send passwords, sign-in codes, private photos, or a complete wardrobe backup unless support explains why a file is needed and you choose to provide it.

Help and support · Feed terms