Scope
Service operator: Byunghak Ko. Effective date: 2026-11-07.
This notice describes data handling in the pre-release Lookfold app. The sample wardrobe is fictional. Saving a record to an account and requesting AI processing are separate actions; signing in does not send a photo to AI.
App analytics in version 1.0.1, build 10
Updated November 9, 2026. This section applies to Lookfold 1.0.1 (build 10) and later, including TestFlight builds. Firebase Analytics (Google) measures app launches, sessions, engagement, SDK-detected purchases and main-screen visits. It processes an app-instance identifier and app/device information, and may derive approximate geography from network information. Custom events contain fixed screen labels and IDs. Photos, notes, search terms, clothing details, Lookfold account IDs and authentication credentials are excluded from analytics properties. IDFA and IDFV collection, advertising storage, advertising user-data use and ad personalization are disabled.
Production collection is enabled by default. In Account, turn off Share usage analytics to stop collection on this device and reset local analytics data and its identifier. Your choice persists after restarting. This does not erase events already received by Google, which follow the Analytics property retention settings. Contact alarmcrew.support@gmail.com about analytics privacy requests.
Sign-in and account storage
Lookfold uses an Apple sign-in identifier, app account ID and email if supplied by Apple for authentication and account separation. Credentials use the device Keychain. Drafts and cached content are kept locally. Garment and person photos, outfits, wear dates, plans, collections, sizes and notes you choose to save to an account are processed in a private Supabase database and file storage in the Tokyo region.
Selected photos and optional AI
The system photo picker imports photos you choose. Before each AI task you review its purpose and photo scope. Our server sends selected person and garment photos to OpenAI for a fitting, or the selected photo for garment classification. Outfit matching uses an outfit photo and up to 24 selected candidates, with their photos, IDs, names and categories. Private notes and payment details are not inputs to these requests. Requested results are saved to the account, not automatically added to actual wear history. Declining AI leaves manual recording available.
Purchases, support and sharing
When subscriptions are offered, Apple processes payment and RevenueCat handles purchase verification and purchase analytics. Lookfold keeps transaction, entitlement and fitting balance records linked to the account; it does not receive full card numbers. Support messages, related job IDs, errors and status help resolve requests. Support review of a photo requires your permission for that photo. Files you choose to share are handled by the recipient.
Access, retention and deletion
Use Account to export records, manage photos or request account deletion. Reauthentication with the same Apple account allows removal of stored app records and files and revocation of Apple sign-in authorization. Previously issued temporary photo links may work for up to 15 minutes; externally shared copies cannot be recalled. Provider logs, backups and required transaction records can have different retention periods from app content. Deleting the app or account does not cancel an Apple subscription. For access, correction, deletion or consent requests, contact alarmcrew.support@gmail.com.
External privacy dispute-resolution and advice contacts in Korea: the Personal Information Dispute Mediation Committee, 1833-6972, and the Personal Information Infringement Report Center, 118. These are external agencies, separate from Lookfold’s contact.
Support retention and request handling
Byunghak Ko directly handles privacy and rights requests at the contact above. General support messages have an adopted maximum retention of 90 days after closure; valid earlier erasure or the end of the purpose can require earlier removal. Transaction, refund, dispute and rights-request records are assessed separately, with justified holds kept separate. Database automation and actual mailbox handling still require operational verification before release. Support does not require repurchasing, generating another AI result or granting access to a photo.
A restricted request ledger contains a case ID, minimal account reference, original receipt time, verification status and provider follow-up status, with references to evidence instead of copied photos or messages. It can remain after app-account removal to track unfinished actions and retention exceptions. Fully reconciled ordinary cases have a maximum retention of 90 days after closure; unresolved exceptions and justified holds are reviewed separately. A manual provider reconciliation does not cancel an Apple subscription.
Automatic account deletion is attempted after the required identity check. Our internal goal for following up on errors is three calendar days from the original receipt, subject to any applicable earlier duty. Identity checking or retries do not restart that clock. This is not a guarantee that all provider logs, backups or required transaction records are erased within three days. Actual provider completion must be confirmed separately.
Diagnostics and backup preparation
We do not add a separate long-term diagnostic copy. Server diagnostics are limited to fixed error categories and job IDs, without photos, notes, temporary photo URLs, tokens or raw provider responses. Provider security, access and SDK logs may have different retention; a published API/database log period does not establish every provider log period.
The adopted backup target is daily paid-plan database backups retained for seven days plus separate encrypted photo backups retained for seven days. It is not yet operationally verified: the current Free projects have no customer-restorable project backups, and an independent photo destination and recovery-key process are not configured. Database backups do not include photo bytes. We do not currently promise a verified recovery time or recovery point.
This website
Sparkish product pages use Firebase Analytics to measure page visits. This website does not accept Apple sign-ins, wardrobe uploads, AI fitting requests or payments.