Privacy Policy

Fitly provides a virtual try-on widget that e-commerce merchants embed on their stores. Shoppers use the widget to upload a photo and see themselves wearing a garment using AI-generated imagery. This policy explains what data we collect from both merchants and shoppers, how we use it, and how we protect it.

Who Uses Fitly

Merchants sign up for a Fitly account to configure and embed the try-on widget on their online store. They manage settings, view usage, and handle billing through the Fitly dashboard.

Shoppers interact with the widget on a merchant's store. No account, login, or personal information is required to use the widget.

Data Collected from Merchants

• Email address, name, store name, and store URL (provided at signup)
• Password (hashed and stored via Convex Auth — we never store plaintext passwords)
• Stripe customer and subscription IDs for billing purposes. We do not store credit card numbers — all payment details are handled entirely by Stripe.
• API key, whitelisted domains, and subscription plan tier

Data Collected from Shoppers

• The photo uploaded for the virtual try-on. This image is stored temporarily and automatically deleted within 24 hours.
• The origin domain (which merchant store the widget was used on), recorded for usage tracking.

We do not collect shopper names, email addresses, or any other personal identifiers. No account is needed to use the widget.

Third-Party Services

The following services receive data as part of operating Fitly:

• Google Gemini API, xAI (Grok) API, Replicate API — receive the shopper's uploaded photo and the garment image to generate the virtual try-on result. The AI provider used depends on the merchant's configuration.
• Stripe — processes merchant payments. Fitly never handles or stores credit card numbers directly.
• Convex — backend database and file storage for all application data.
• Vercel — hosts the Fitly dashboard and website.
• AWS CloudFront — serves the widget JavaScript file via CDN.

Data Retention

• Shopper photos: automatically deleted after 24 hours. A cron job runs hourly to purge expired uploads.
• Generated try-on images: retained until the merchant deletes them.
• Session records: retained for usage tracking and billing purposes.
• Merchant accounts: retained until the merchant requests deletion.

Security

• Domain whitelisting ensures the widget API only responds to requests from approved merchant domains.
• All image URLs are served over HTTPS only.
• SSRF protection blocks requests to private IP ranges, preventing internal network access.
• File uploads are limited to 5MB.
• All API endpoints require authentication via API key.

Cookies and Tracking

Fitly does not use any analytics or advertising trackers. There is no Google Analytics, no pixel tracking, and no third-party analytics of any kind.

The Fitly merchant dashboard uses session cookies for authentication. These cookies are only set when a merchant logs in to manage their account.

The widget does not set any cookies on shopper browsers. Shoppers are not tracked across sites or sessions.

GDPR and Biometric Data

Shopper photos may be considered biometric-adjacent data under certain jurisdictions. Fitly processes these photos solely for the purpose of generating a virtual try-on image. Photos are not used for facial recognition, identification, or any purpose beyond try-on generation.

All shopper photos are automatically deleted within 24 hours of upload. Shoppers who wish to have their photo deleted sooner may contact us at contact us.

Children

Fitly is not intended for use by children under 13. We do not knowingly collect data from children under 13. If you believe a child has submitted data through our service, please contact us and we will delete it promptly.

Changes to This Policy

We may update this policy to reflect changes in our practices or for legal reasons. When we do, we will update the “Last updated” date at the top of this page.

Contact

For questions about this privacy policy or to request data deletion, contact Fitly at contact us.