Policies and best practices

The supported clothing workflow uses merchant catalog import, a storefront script, and generated photo-based previews. It has no live store sync or merchant outbound webhook service. AI size recommendation is planned and is not currently available.

A preview does not guarantee physical fit, purchase outcomes, or a reduction in returns. Keep garment measurements, size charts, purchase controls, and return policies available to the shopper.

Starter, Growth, and Scale have published monthly allowances and billing amounts. Enterprise volume, support, and any SLA are defined by agreement. Read pricing, terms, and your checkout or contract for the applicable offer.

Any uptime, service-credit, maintenance, backup recovery, or support commitment must be specified in a current written agreement before you rely on it.

Explain the photo-processing experience before upload and use photos only with the necessary permission. The current widget accepts one JPEG, PNG, or WebP photo up to 10 MB; a separate shopper-profile workflow should not be treated as the widget's upload requirement.

The widget submits the selected photo as a base64 data URL; it does not accept a remote shopper-photo URL. The service uploads the photo into protected storage and gives processing a temporary signed access link. To generate the preview, the photo is sent to Closku's AI inference provider, which processes it and returns the generated image. This processing flow is separate from public product photographs imported through the merchant catalog.

You are responsible for the notices and consent your storefront presents to shoppers, and for responding to shopper requests about their photos, including deletion requests. Closku assists with shopper requests that concern data it processes on your behalf. Do not enable the widget in a way that encourages shoppers to upload photos of children or of other people without their permission.

Review the privacy policy and the Terms of Service for processing, storage, retention, and rights requests. Do not promise that photos are deleted immediately or never stored unless that is established for the actual service. Keep shopper images, result URLs, and account credentials out of public logs.

• Maintain a catalog owner and storefront-to-Closku product mapping.
• Review product imagery, variant labels, and category configuration before launch.
• Test desktop and mobile after changes to scripts, themes, or product data.
• Monitor submitted and completed previews separately from failures and purchases.
• Use a defined evaluation period and controlled comparison where possible, without treating every sales or return change as a result of try-on.

You are responsible for the notice your storefront shows shoppers before upload. This short template covers the points the widget flow depends on. Place it near the try-on button or upload area, keep it visible without a click-through, and adjust it to your store.

"When you upload a photo here, it is sent securely to our virtual try-on provider (Closku) to create your preview. The photo is used only to create your preview, is not used to identify you, and is automatically deleted within 14 to 30 days depending on the store's plan. To request a copy or deletion of your photo, contact us and we will forward your request to the provider. See [link to your privacy policy] for details."

Photos are deleted within 14 days on the Starter plan and within 30 days on other plans, matching the retention periods in the Closku privacy policy. Replace [link to your privacy policy] with your store's privacy page before publishing.

Use the owner account's billing portal or contact Closku for available changes. Effective dates, renewals, cancellation, and any adjustments follow the actual checkout or agreement. Do not assume that an upgrade resets recorded usage or that a downgrade has a penalty described by an outdated guide.

You may request an export of your catalog and account data by contacting Closku before or shortly after closing your account, as described in the Terms of Service.