Cookie Policy
This Cookie Policy explains how Codemarket OÜ uses cookies and similar storage on seenshot.app. It sits with the Privacy Policy (GDPR, ePrivacy Directive 2002/58/EC as implemented in the EU/EEA, UK PECR, and US state privacy laws).
1. What we use today
The website does not use Google Analytics, advertising pixels, or other optional tracking cookies. We do not show a cookie-consent banner because the only cookie we set is strictly necessary to run a signed-in session (ePrivacy exception for cookies that are necessary to provide a service the user requested).
The Mac app does not set website cookies. Mac analytics (PostHog) run in the app, not in the browser. See the Privacy Policy.
2. Cookie
| Name | Type | Purpose | Duration |
|---|---|---|---|
seenshot_id |
First-party, strictly necessary | Holds the Firebase ID token so signed-in pages (including screenshot <img> requests on My Screenshots) can authenticate. Path /, SameSite=Lax, Secure on HTTPS. |
Session until Sign Out, or until the token is replaced. Sign Out sets max-age=0. |
3. Local storage (similar technologies)
These keys are in your browser’s localStorage for seenshot.app. They are not HTTP cookies. They are strictly necessary for Sign In, token refresh, and completing an email sign-in link.
| Key | Purpose |
|---|---|
seenshot_idToken |
Firebase ID token copy |
seenshot_refreshToken |
Firebase refresh token |
seenshot_uid |
Firebase user id |
seenshot_email |
Account email shown in the nav |
seenshot_expiresAt |
ID token expiry time in milliseconds |
seenshot_pendingEmail |
Email waiting for an email-link sign-in |
Sign Out removes these keys. You can also clear site data in your browser settings.
4. Third-party requests (not our cookies)
- The landing page may fetch GitHub Releases so Download can point at the latest DMG. GitHub may set its own cookies on github.com, not on seenshot.app.
- Sign-in talks to Google Identity Toolkit / Firebase. Google may set cookies on Google domains according to Google’s policies.
- If you pay for Member, Polar checkout runs on Polar’s domains.
We do not control those third-party cookies. Use each provider’s cookie tools if you visit their sites.
5. How to refuse
You can refuse seenshot_id by not signing in, or by signing out and blocking cookies for seenshot.app. Without that cookie and localStorage, My Screenshots and Mac website sign-in will not work. Browser “block all cookies” settings will break the signed-in site.
6. Changes
If we add optional analytics or advertising cookies on seenshot.app, we will update this page and, where the law requires consent, we will ask before setting them. We will not add a consent banner while the only cookie remains strictly necessary.