SnapLab 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 |
Signup verification storage
The website uses sessionStorage under snaplab_pending_signup to keep the pending signup email address, an opaque challenge, and code-expiry and resend times in the same browser tab. This lets you refresh the verification screen without entering your signup details again. It contains no password or verification code and grants no account access. It is cleared after successful verification or when you choose Change email or Back to sign in. Otherwise it can remain for the browser’s tab session; stale data is discarded when the login page next checks it. The server independently limits a pending signup to 24 hours from its creation, and each code to 10 minutes. The native app keeps its pending verification screen in app memory rather than this browser storage.
Other storage
The designer stores account-specific unsaved drafts in localStorage for recovery across refreshes and tab closure, falling back to sessionStorage if persistent storage is unavailable. Browser drafts expire for recovery after 30 days without an update and are removed when next accessed; you can discard them sooner from Account. Device preferences remember prior site use and whether the designer welcome has appeared. Signed-in accounts also keep this welcome status on the server so it is not offered again on another device. 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.
Email and consent
Sending verification, welcome, or password-reset emails does not add advertising or analytics cookies to SnapLab. Server-side code and delivery records are described in the Privacy Policy; they are separate from browser cookies. The email templates contain no tracking pixels or per-recipient tracking links. Your email app may request the public logo image, and email providers may keep delivery records. Accepting the Terms or verifying an email does not authorize future advertising or analytics tracking.
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’s site storage or mobile app. Other open tabs, browsers, devices, and device backups may require separate clearing. You can clear site data or remove local app data; 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 or pending signup so we can verify your request. Do not send your password, verification code, password-reset link, playbook access code, or any legacy recovery code.