Skip to main content
DELETE
Delete My Data
Erase the calling shopper’s Genlook data. Use it to power a “Delete my data” control in a custom try-on UI; the built-in widget already offers one.
On JavaScript, the @genlook/storefront SDK is the recommended integration. deleteMyData() calls this endpoint, then wipes the local history and pending upload, and emits tryon:data_erased once the server confirms. It never rejects, so your UI can await it and navigate away unconditionally:
SDK

What gets erased

Everything tied to the shopper: uploaded photos, generated try-on images, share links (existing links stop working), the shopper’s try-on records, and their identity records. Copies in analytics are queued for erasure as well. The merchant’s order history and aggregate statistics are detached from the shopper rather than deleted.

Scope

Erasure is scoped by how the shopper is identified:
  • From the storefront widget or a plugin proxy, where the customer identity is verified by the shop’s server, the erasure covers the shopper’s full identity: every device linked to their customer account or email.
  • With a publishable key, the identity headers are declared by the caller and cannot be verified, so the erasure is deliberately scoped to the calling device’s anonymous id. One shopper can never erase another shopper’s data.

Request

No body. The shopper is identified by the standard identity headers (see identifying the shopper). This endpoint is rate-limited to 5 requests per minute per caller.

Example

Response

boolean
true once the erasure completed.
Response
Erasure is synchronous and irreversible: a 200 means the data is gone. Clear any history you cached on your side too. The shopper’s anonymous id stays usable and now refers to an empty shopper, so you can keep it or mint a new one.

Errors