RelightSnap
EN
ENEnglishJA日本語PTPortuguês (Brasil)KO한국어FRFrançaisESEspañolITItalianoDEDeutsch
COOKIE POLICY · UPDATED 28 OCTOBER 2026

Small files.
Clear purposes.

RelightSnap uses cookies and browser storage to remember who can access a photo and keep the editing flow working.

What lives in your browser

StoragePurposeLifetime
app_sessionEssential. Keeps sign-in, form protection and temporary authentication state.Up to 30 days
guest_keyEssential. Links a guest to their private preview and helps enforce the free allowance alongside the IP address.Up to 365 days
Session storageRemembers the current job and return/download state during the editing flow. It does not store a photo file.Browser tab session
GTM & analyticsWhen configured, Google Tag Manager loads tags for usage measurement. Tags may receive page URLs, device data and events such as a started relight. Cookie names and retention depend on the tags enabled.Set by the configured tags

Essential storage

Session and guest cookies are first-party, HttpOnly and SameSite=Lax, with Secure on HTTPS. They support sign-in, security and private photo access. Blocking them can prevent sign-in or make a guest preview inaccessible. Clearing them does not reset the IP-based free limit.

Analytics on this site

Google Tag Manager is not currently configured, so this site is not loading GTM analytics tags. Editing events can still be recorded in the browser’s data layer and in our service logs; that is separate from third-party tracking cookies.

We do not send uploaded image files in analytics events. We must obtain consent for optional tracking where required before enabling those tags.

Your browser, your controls.

You can inspect, block or delete cookies and session storage in your browser’s site settings. This does not delete server-side photos or your account. Use account Settings or contact support for data deletion. Google sign-in and Polar checkout run on external services with their own cookie policies.