Privacy Policy

Your privacy is of foundational importance to Howilook. This Privacy Policy describes how we collect, process, protect, and delete your personal data when using our application.

1. Information We Collect

• Account Data: Email address, display name, and avatar URL provided via Google Sign-In or manual account creation.
• Photos & Visual Data: Selfies and outfit photos captured through your device camera or uploaded from your photo library.
• Aesthetic & Style Preferences: Style goals, aesthetic choices, and physical dimensions (height, weight, body type) that you voluntarily supply to personalize styling accuracy.
• Transaction Records: Payment IDs and plan tiers processed via secure payment providers (we do not store raw credit card numbers or banking passwords).

2. How We Process Photos

Face and outfit scans are separate requests. When you request a scan:

• Your selected photo is uploaded to Supabase storage and sent through our backend to Google Cloud Vertex AI for processing over HTTPS. Processing may occur outside your country; the current Vertex configuration uses us-central1.
• The model generates cosmetic style and grooming suggestions from the image and optional context. Scores are subjective AI estimates, may be inaccurate or biased, and are not medical assessments, measured golden-ratio results, identity verification, or an objective measure of attractiveness or personal worth.
• Application code does not create facial identification templates or compare photos with an identity database.
• Photos and results are stored in account-scoped, access-controlled storage and database records. Photos are shared with processing providers to deliver the requested analysis, not kept only on your device.
• The code also supports Google Gemini Developer API as a separately controlled fallback. It must remain disabled unless its processing terms, retention, regional handling and user disclosures have been reviewed and approved. Provider approval is a release prerequisite, not established by this draft.

3. Data Retention & Deletion

• Scan Deletion: Request deletion from history. Hiding a scan or accepting the request is not proof that its photo and record have been removed; cleanup can remain pending and require retry.
• Account Deletion: Request deletion inside Settings → Delete Account. Cleanup covers application profile, scan and image data before account removal. Pending work, network failures and storage cleanup may delay completion. See deletion instructions.
• Limits: Provider-held payment records, provider retention and backup schedules are separate from application deletion. Their applicable retention periods and any legally required records must be confirmed before publication; this draft does not promise instant or complete provider erasure.
• Operational records support payment reconciliation, analysis failures and cleanup without intentionally including photo content, tokens or raw payment credentials. Final retention periods and automated cleanup activation remain release prerequisites.

4. Third-Party Service Providers

• Supabase: Account authentication, application database and photo storage.
• Google: Google Sign-In and Vertex AI image analysis. Gemini Developer API requires separate approval before fallback activation.
• Razorpay: Checkout and payment processing. Provider payment records are subject to the provider's own retention obligations.

No external crash-reporting SDK is included. This is not a claim of regulatory certification or a complete deployed-provider audit.

5. Audience & Consent — Pending Owner Approval

The target audience, minimum age, minor-photo policy and any required parental consent or age-assurance controls have not been approved for release. This draft makes no claim that age verification is implemented. These decisions and matching Google Play declarations must be finalized before publication or launch.

6. Contact Us

Draft privacy contact: lakhtech20@gmail.com. Mailbox ownership, monitoring and request handling must be verified before publication.