VESQORA Privacy Policy

1. Introduction

This Privacy Policy explains how VESQORA (“we,” “us,” or “our”) collects, uses, stores, and shares information when you use the VESQORA mobile application and related services (the “Service”).

By using VESQORA, you agree to this Privacy Policy. If you do not agree, please do not use the Service.

This page is publicly available and does not require signing in to the VESQORA app.

2. Information We Collect

We collect the following categories of information in connection with VESQORA:

2.1 Account information

• Email address (via email sign-up or authentication providers)
• User ID assigned by our authentication system
• Profile information such as display name (and, if you provide them, fields such as avatar URL, country, or currency)
• Authentication-related information when you sign in with supported providers (for example, email/password, Google, or Apple Sign In where available)
• Photo-processing consent timestamp recorded when you agree to photo processing in the app

2.2 Photos and user content

• Person photos you select or capture for virtual try-on
• Garment / clothing images you upload or add to your wardrobe
• Generated try-on result images created through the Service
• Optional wardrobe metadata you provide (for example, category, name, color, description, and related tags)

The app may request access to your camera and/or photo library so you can select, capture, or save images. Permission prompts are handled by your device operating system.

2.3 Wardrobe information

If you use My Wardrobe, we store clothing item records associated with your account, including image storage paths, category, optional display name, and metadata such as favorite status where you use that feature.

2.4 Try-on jobs, results, and saved looks

• Try-on job records (for example, status, related photo/clothing references, provider identifiers needed to run the job, and error information if a job fails)
• Try-on result records and result image paths
• Saved looks you explicitly save (title/notes if provided, linked to a try-on result)

2.5 Credits and billing-related records

• Credit ledger transactions stored on our servers (for example, signup grants, reservations, consumption, and refunds related to try-on jobs)
• Subscription-state fields maintained for future billing/entitlement handling (for example, whether a Pro entitlement is marked active)

Important: As of the effective date of this Policy, in-app purchases and live RevenueCat billing are not active in the VESQORA app. VESQORA currently uses a billing stub for development/preview. We do not claim that VESQORA is presently processing paid store purchases.

2.6 Usage and analytics information

VESQORA includes an analytics abstraction that can record product events (for example, app opened, try-on started/completed/failed, wardrobe actions, result saved/shared, and paywall viewed). Event properties are designed to avoid sending photos, image URLs, or storage paths.

A third-party analytics SDK (PostHog) is prepared for future use when a project key is configured. Until that provider is fully wired and enabled, analytics may be limited to development console logging or no network transmission, depending on environment configuration.

2.7 Technical and support information

• Information needed to operate authentication sessions and secure access to your account
• Limited operational logs generated by our backend (for example, Edge Function errors), which are used for reliability and security
• Information you send us if you contact support (such as your email and message content)

3. How We Use Information

We use information to:

• Create and manage your VESQORA account
• Provide virtual try-on features
• Store and display wardrobe items and saved looks
• Process credit reservations, consumption, and refunds for try-on jobs
• Authenticate you and protect the Service
• Respond to support requests
• Improve reliability and diagnose failures
• Comply with legal obligations and enforce our Terms

We do not sell your photos. VESQORA does not use your photos to train our own AI models. When a third-party AI provider processes images for try-on, that processing is governed by that provider’s applicable terms and privacy practices (see Section 4).

4. AI Image Processing (FASHN)

VESQORA’s virtual try-on feature may use a third-party AI provider, FASHN (fashn.ai), when the Service is configured for live AI processing.

When a try-on is started:

• A person image and a garment image are prepared on our servers (typically as short-lived signed URLs or equivalent image references)
• Those images are sent to FASHN’s API so FASHN can generate a virtual try-on preview
• The resulting image may be retrieved by our servers and stored in your private VESQORA result storage so you can view, save, download, or share it in the app

VESQORA’s mobile app does not call FASHN directly. Try-on requests are handled by our server-side Edge Functions.

In development environments, VESQORA may use a mock try-on provider that does not call FASHN. Mock results are labeled as development/mock results in the app.

5. Data Storage

VESQORA uses Supabase for core backend services, including:

• Authentication
• Database (Postgres) with row-level security policies
• Private object storage
• Edge Functions for try-on orchestration and account deletion

Private storage buckets used by VESQORA include:

• user-photos — person photos
• clothing-images — garment / wardrobe images
• try-on-results — generated try-on images
• avatars — avatar objects if used

Storage paths are organized under your user ID. Access controls are designed so that other users cannot read your private objects through normal app policies. Result images and certain media may be accessed via temporary signed URLs.

6. Sharing of Information

We share information only as needed to operate VESQORA, including with:

• Supabase — hosting authentication, database, storage, and Edge Functions
• FASHN — processing person and garment images for virtual try-on when live AI is enabled
• Authentication providers you choose (for example, Google or Apple), to the extent required for sign-in
• Analytics providers if/when a configured analytics service is enabled
• Billing providers if/when paid purchases are enabled in the future (see Section 7)
• Service providers who assist with infrastructure or support, under appropriate confidentiality and security expectations
• Authorities or other parties when required by law, or to protect rights, safety, and the integrity of the Service

We do not sell your personal information.

7. Payments and Billing

As of the effective date, VESQORA’s RevenueCat / store purchase integration is a stub used for development and UI preview. VESQORA does not currently process live Google Play (or other store) purchases through RevenueCat in the shipping app configuration described by this Policy.

If paid credit packs or subscriptions are enabled later, purchases would typically be processed by the applicable app store and/or a billing provider such as RevenueCat, and those parties’ terms and privacy policies would apply to payment processing. Any such change will be reflected in an updated Privacy Policy and in the purchase screens presented at the time of purchase.

8. Credits

VESQORA uses a server-side credit ledger. Credits are used for AI try-on jobs. In the current product design, starting a try-on typically reserves one credit; if the try-on fails according to the Service’s credit rules, the reserved credit may be returned (refunded) to your balance.

New accounts may receive a signup credit grant configured by the Service. We do not state a credit expiration period in this Policy because automatic credit expiry is not implemented as an active product rule as of the effective date.

9. Data Retention

We retain information for as long as reasonably necessary to provide the Service, maintain the Service, comply with legal obligations, resolve disputes, and enforce our agreements, unless a different period is required by law.

When you delete your account using the in-app deletion flow, we take steps to remove associated account data as described in Section 10. Limited non-identifying audit records may remain (for example, a count of storage objects removed) without storing your email or user ID in that audit table.

Soft-deleted wardrobe items or results may remain in systems until purged according to Service operations; account deletion is designed to remove your auth user and cascade related database records, and to purge storage objects under your user prefix.

10. Account Deletion

You can delete your VESQORA account from the Profile section of the app. The flow requires you to confirm by typing your account email.

When deletion succeeds, VESQORA’s server process is designed to:

• Remove private storage objects under your user ID from VESQORA’s private buckets (user-photos, clothing-images, try-on-results, and avatars)
• Delete your authentication user, which cascades deletion of related application database records associated with your user ID
• Write a minimal account-deletion audit entry that does not store personal identifiers such as your email

Local app caches related to try-on resume may also be cleared on the device as part of the deletion client flow.

Deletion of data held solely by third parties (for example, images already processed by an AI provider) is governed by those third parties’ policies and may not be controlled by VESQORA.

To request help with account deletion, contact bsaipna1@gmail.com.

11. Security

We use safeguards appropriate to VESQORA’s architecture, including:

• Authenticated access to account features
• Row-level security policies in the database
• Private storage buckets with user-scoped path policies
• Temporary signed URLs for certain media access
• Server-side secrets for AI provider API keys (not embedded as public mobile client secrets)
• Server-side orchestration of try-on jobs so the mobile app does not directly authorize credit settlement or AI provider calls

No method of transmission or storage is completely secure. We cannot guarantee absolute security.

12. Children’s Privacy

VESQORA is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact us at bsaipna1@gmail.com and we will take appropriate steps.

This section is a product privacy statement and is not a claim of certification under any specific children’s privacy law.

13. Your Privacy Rights

Depending on where you live, you may have rights to:

• Request access to personal information we hold about you
• Request correction of inaccurate information
• Request deletion of your account and associated data
• Ask questions about how your information is processed

You can exercise many controls directly in the app (for example, deleting wardrobe items, removing saved looks, or deleting your account). For other requests, email bsaipna1@gmail.com.

We may need to verify your request before responding. Applicable law may limit or shape these rights.

14. Third-Party Services

15. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. When we do, we will revise the effective date above and post the updated Policy at this URL. Continued use of VESQORA after an update means you acknowledge the revised Policy.

16. Contact

Questions about this Privacy Policy or your data:
PANDADeveloper (independent developer, India)
Email: bsaipna1@gmail.com