Claspel Privacy Policy

Last updated: October 26, 2026

Overview and contact

Claspel lets shoppers upload a photo to preview jewelry using AI. Photos can identify a person and are personal data. This policy describes the app's handling of shopper and merchant information. The store's own privacy policy also applies. Contact the app operator at iftach@claspel.com for support, access or deletion requests.

Data collection and purposes

• Photos and generated results: uploaded selfies, jewelry product images and generated try-on images are processed to provide and revisit previews. Stored image keys include the shop domain and random identifiers, rather than a customer-to-photo directory.
• Account-linked usage: when available, a Shopify customer ID is stored with the shop, product ID and generation time to account for usage. Aggregate usage counts are retained for billing and service administration.
• Temporary prediction records: provider prediction ID, shop/product ID, customer identifier (a logged-in customer ID or an identifier derived from the request IP), expiry and sometimes a completed image object key support polling, rate limits and generation completion. These temporary mappings can link some results to an account; they are not a complete photo index.
• Analytics: event types, shop/product IDs, random browser session IDs, timestamps and limited event metadata support merchant usage and conversion reports. Reports in the merchant dashboard show counts and averages. Random session IDs do not make all app data anonymous.
• Merchant access: Shopify sessions can contain shop domain, authorization tokens, scopes, expiry, and merchant user ID, name, email, locale and account-role fields supplied by Shopify. These support authentication and operating the app.
• Subscriptions: shop, plan/status, Shopify charge ID and billing-period/trial dates support subscription management. The app does not collect payment card details; Shopify handles payment.
• Failed-result cleanup: if an in-flight generation finishes after deletion and its result cannot be erased immediately, we retain the exact object key, shop and creation time for cleanup retries. These records contain no customer account ID or access report.
• Privacy requests: customer ID, shop, request time, relevant stored usage/prediction data and completion status are kept in merchant access reports. Full incoming privacy webhook payloads and customer email addresses are not stored in these reports.
• Operational logs and rate limits: requests and failures may be logged by the app and infrastructure providers. Verbose request logging can include URLs and customer identifiers. Logs have separate provider retention settings; the scheduled database cleanup described below does not purge infrastructure logs.

Photos, providers and international processing

Photos and generated images are stored in Cloudflare R2; app records are stored in Cloudflare D1. Photos and product images are sent to Replicate to generate a preview. Cloudflare and Replicate processing may occur outside your country. Do not assume local-only processing or a particular residency guarantee.

The app operator does not use photos for advertising or train models with them. Provider handling is governed by their own terms and settings, rather than a blanket guarantee from this app. Replicate documents removal of API prediction inputs, outputs and logs after one hour by default; this is separate from the app's stored R2 copies. See Replicate data retention, Replicate privacy policy, Replicate terms and Cloudflare privacy policy.

Retention and deletion timing

• Stored selfies and generated images become eligible for deletion at 7 days after upload. An hourly cleanup job deletes eligible images. Normal scheduling adds up to about one hour; outages or failed cleanup can delay removal until a successful run. Expiring viewing links and cache metadata do not delete stored objects.
• Analytics events and privacy-request reports older than 90 days are deleted by the same hourly job, with the same scheduling and failure caveat. Marking an access request handled does not immediately delete its report.
• Customer IDs on usage records older than 90 days are cleared by the job. Usage records, shop/product references, timestamps and aggregate counts remain for billing and service administration.
• Failed-result cleanup records are retried by the hourly cleanup job and removed only after storage confirms deletion. Storage outages can delay erasure; these queued results are not served by the app.
• Pending prediction mappings expire after a 10-minute polling window and are removed on cleanup. If a deletion attempt fails, the revoked mapping needed to retry erasure is retained until that deletion succeeds; it cannot be used to retrieve a result. Expiry of a mapping does not itself delete the corresponding image.
• Merchant sessions and subscription records are retained while needed to operate the installed app. Uninstall removes sessions; Shopify's subsequent shop-redaction request removes the shop's stored images and app database records, including subscriptions and usage. Uninstall and Shopify's delayed redaction request are distinct events.
• The browser can remember a result reference and random analytics session token. Clear site storage to remove locally saved references; this does not delete server images.

Access, correction and early photo deletion

Contact your store or iftach@claspel.com. Depending on your location, applicable privacy law (including GDPR or CCPA) may provide access, correction, deletion, objection or other rights. We may need information to verify your request and locate the relevant records. Merchants can retrieve account-linked access reports and mark them handled in the app's Privacy requests page; delivery to the customer is handled by the merchant.

For early photo deletion, provide the store domain and the exact image object key or result reference, if available. Do not send another copy of your selfie. Support must verify that the reference belongs to the relevant store before deleting it. An account ID alone cannot locate all photos: most objects are not indexed by customer. Customer-redaction requests clear linked identifiers, access reports and known linked results, but cannot identify every anonymous upload or result. Unlinked images remain subject to scheduled retention. We will explain what can be found and removed.

Merchant responsibilities and policy changes

Merchants should disclose this feature in their store privacy notice, keep the notice visible before photo selection, handle privacy reports securely, and assess the legal basis, applicable consent requirements and international-transfer safeguards for their shoppers. This policy is not a certification of legal compliance. Contact the operator about questions or corrections. Updates will appear here with a revised date.