Privacy Policy

1. Scope and responsibility

This policy applies to the AhaDrobe website, partner workspace, support forms, and the AhaDrobe virtual try-on widget. AhaDrobe determines how information is processed for operating these services.

When a store embeds the widget, that store also decides why it offers virtual try-on to its visitors. The store should provide its own privacy information and explain its use of AhaDrobe.

2. Website and partner information

Accounts and store configuration

When a partner signs in, we process an account identifier and the primary email address. We also store the store name, public store identifier, approved storefront addresses, widget colour and language settings, account status, credit balance, and per-device credit limit.

Payments

Our payment provider processes checkout and payment details. AhaDrobe stores a payment reference, purchased credits, amount, currency, payment status, and the related account and store records. AhaDrobe does not store full payment-card details.

Contact and support

Support requests can include the signed-in email address, account identifier, name, subject, message, attachments, relevant page address, browser details, service environment, and request status. These details are used to respond, investigate issues, and maintain support records.

3. Virtual try-on widget

Photos and generation inputs

The widget processes the model photo selected by the visitor, the selected clothing image or image URL, and the selected position and quality settings to generate a virtual try-on result. The uploaded model photo is stored locally in the visitor's browser so the current selection can be restored. It is sent to the generation service only when the visitor requests a result.

AhaDrobe does not write the uploaded model image itself to the AhaDrobe database. Generation status, quality, credits, technical identifiers, result URL, and error code may be recorded to operate credits, show results, prevent abuse, and investigate failures.

Device and usage information

To allocate credits and prevent repeated or abusive use, we process a pseudonymous device identifier, protected device and network signals, browser and device characteristics, credit allocation and usage, and activity times. These protections reduce direct exposure but do not make the information anonymous in every context.

Browser storage

The widget uses browser storage and a strictly necessary device cookie to remember configuration, selections, the uploaded model image on that device, open state, and credit-session information. See the Cookie Policy for details and removal options.

4. Why we process information

• Provide authentication, partner accounts, store settings, credits, payments, support, and virtual try-on generation.
• Secure the service, enforce allowed storefront origins, prevent fraud and abuse, and diagnose failures.
• Maintain transaction and operational records and comply with legal obligations.
• Respond to requests and exercise or defend legal rights.

Depending on the context, processing is necessary to provide the requested service or perform a contract, comply with legal obligations, or pursue legitimate interests in operating and protecting AhaDrobe. Where consent is legally required, processing is based on consent and can be withdrawn.

5. Service providers and transfers

• Cloudflare hosts and protects the website and online services.
• Clerk provides account sign-in and identity services.
• Stripe processes checkout and payments.
• FASHN AI processes model and clothing images and produces virtual try-on results.
• Email providers deliver support notifications to the AhaDrobe support mailbox.

These providers may process information in countries outside your own. We use appropriate contractual and legal transfer safeguards where required. Image inputs and generated results are kept only for the periods needed to provide the service, subject to the generation provider's processing and retention terms.

6. Retention

We keep account and store records while the account is active and for a limited period afterwards when needed for security, support, disputes, or legal compliance. Payment and transaction records may be retained for legally required accounting periods. Contact requests and attachments are kept only while reasonably needed to resolve and document the request.

Device-credit records are kept for their operational validity and for a limited period needed for abuse prevention and support. Browser-stored widget data remains on the device until it is cleared by the widget, the browser, or the visitor. Generated output availability is also limited by the generation provider's retention period.

You can request deletion using the contact details below. Some records may need to be retained where required by law or necessary to establish, exercise, or defend legal claims.

7. Your privacy rights

Depending on applicable law, you may request access, correction, deletion, restriction, portability, or object to processing. You may withdraw consent where processing relies on consent and may complain to your local data protection authority.

To protect accounts and other people, we may need to verify identity before completing a request.

8. Security and changes

We use account controls, approved storefront checks, encrypted connections, protected credentials, and request validation. No service can guarantee absolute security. See the Security page for an overview.

We may update this policy as the service changes. The updated date at the top identifies the current version.