Privacy & cookies
Effective date: 2 September 2026. This notice explains how SnapGem handles personal data and device storage. It is designed for GDPR/ePrivacy transparency and should be read together with our Terms.
Who is responsible
SnapGem is the data controller for account, platform and website data described here. Privacy requests can be sent to shiridiamonds@walla.com.
Camera and virtual try-on
The live camera feed is processed in your browser to position jewelry. SnapGem does not upload the live camera stream. When you freeze and edit a try-on image, the image remains on your device. “Save” creates a local download and “Share” uses your device’s native share interface. The current version does not upload the finished try-on image to SnapGem.
The try-on engine downloads technical browser libraries/model files needed to provide the requested camera feature. Those providers may receive ordinary network metadata such as IP address as part of delivering those files, but the camera image itself is not sent to them by SnapGem.
Data we process
- Merchant account data: email address, business name, profile details and account status.
- Merchant content: jewelry images, product names, categories and destination URLs you choose to publish.
- Essential security/session data: session identifiers, CSRF protection data and ordinary server/security logs.
- Aggregate SnapGem product events: counts such as try-on views, captures and shop clicks. These events are stored without IP address or a reusable browser/session identifier.
- Support/contact data: name, email, support subject and the messages you choose to send through our private support conversation.
- Optional message translation: when you explicitly press Translate, the selected support message is sent to Google Translate to produce a translation; SnapGem caches the translated text to avoid repeated requests.
- Optional analytics: Google Analytics and Microsoft Clarity only after you explicitly accept analytics.
Why we process data
We process account and merchant data to provide the service and manage accounts; essential technical/security data to operate and protect SnapGem; aggregate non-linkable product events to understand service performance; and optional third-party analytics only on the basis of your consent. You can withdraw analytics consent at any time using .
Cookies and device storage
Necessary storage is used regardless of analytics choice when required to provide requested functionality. Optional analytics remains off until you accept it. Accept and Reject are remembered for the same period (180 days), after which SnapGem asks again.
| Name / category | Purpose | Duration | Provider |
|---|---|---|---|
snapgem — Necessary | Secure login/session and account state. | Browser session | SnapGem |
sg_consent_v1 — Necessary local storage | Remembers Accept/Reject so the consent prompt does not reappear on every page. | 180 days | SnapGem |
_ga, _ga_* — Analytics | Distinguish browsers and maintain GA4 session state. | Configured by SnapGem up to 13 months | Google Analytics |
_clck — Analytics | Clarity user ID/preferences for the site. | About 1 year | Microsoft Clarity |
_clsk — Analytics | Links page views into a Clarity session. | About 1 day | Microsoft Clarity |
Clarity/Microsoft third-party cookies such as CLID, ANONCHK, MR, MUID, SM | Clarity analytics/session operation. Exact use and duration are controlled by Microsoft and may change. | Session to about 1 year depending on cookie | Microsoft |
Google Analytics and Microsoft Clarity scripts are not loaded by SnapGem before analytics consent. If you reject, the service remains fully usable. If you withdraw after previously accepting, SnapGem sends a denial signal, removes first-party analytics cookies it can control and reloads without optional analytics scripts.
Analytics services
Google Analytics 4 helps us understand aggregate site use. Advertising storage and ad personalization signals are kept denied in our implementation. Google privacy information.
Microsoft Clarity can provide heatmaps and session interaction analytics after consent. Input fields are masked by Clarity, and we use Clarity Consent Mode signals. Microsoft privacy information.
Support conversations and translation
Contact requests create a private conversation identified by a long, unguessable link token. Anyone who has that link can access that conversation, so keep it private. SnapGem uses support messages to answer your request and maintain the conversation history. Translation is optional and on-demand; a message is sent to Google Translate only when Translate is selected by you or an authorized SnapGem administrator.
Retention
Account and merchant content is kept while the account/service relationship is active and as reasonably required for legal, security and backup purposes. Aggregate SnapGem event counts may be retained for product reporting because they are designed not to identify or link visitors. Third-party analytics retention follows the relevant provider settings/policies and only applies after consent.
Your rights
Where GDPR applies, you may have rights to access, correct, erase or restrict personal data, object to certain processing, receive portable data where applicable, and withdraw consent at any time. You may also lodge a complaint with the competent data-protection authority, including the Office of the Commissioner for Personal Data Protection in Cyprus where applicable.
Security and international providers
We use access controls, HTTPS, secure session settings and restricted private storage. Some technical/analytics providers may process data outside Cyprus/EEA under their applicable transfer mechanisms and privacy terms.
Changes
We may update this notice when functionality, law or service providers change. The effective date above identifies the current version.