SnapLabSnapLab currently uses cookies and device storage to keep sign-in and draft recovery working. We do not set advertising or analytics cookies on the website. There is no optional tracking to accept or reject today, so we do not show a tracking-consent banner.
Website cookies
| Name | Purpose | Duration |
|---|---|---|
| __Host-snaplab_session | Keeps you signed in; HttpOnly and secure on HTTPS. | Up to 30 days |
| __Host-snaplab_embedded | Partitioned sign-in session for supported embedded app contexts. | Up to 30 days |
| __Host-snaplab_oauth | Checks a Google or Apple sign-in request when you choose it. | Up to 10 minutes |
| play_designer_session | Older sign-in cookie accepted temporarily for existing sessions; new sign-ins use the cookies above. | Until its existing expiry or sign-out |
Other storage
The designer stores an unsaved draft in sessionStorage so you can recover it after a refresh. The service worker caches the app icons and manifest. The mobile app stores your session in secure device storage and may keep unsynced drafts locally. These are not advertising trackers.
Your controls
Sign out to end your active sign-in session; unsynced local drafts remain on the device for recovery. Deleting your account clears its drafts in the current browser tab or mobile app. You can clear site data in other browser tabs or remove local app data on other devices; doing so may remove drafts that have not synced. You may leave the service without accepting optional cookies because none are currently used. Choosing Google or Apple sign-in opens that provider’s own service, which has its own cookies and policy.
If we add ads, measurement, or other optional tracking, we will update this notice and provide any required controls before loading it.
Questions or requests: Snaplabsupport@gmail.com. Include the email address associated with your account so we can verify your request. Do not send your password, password-reset link, or any legacy recovery code.