Cookie Policy
What cookies and local storage we use. Spoiler: only what we need to log you in. No analytics. No tracking.
Cookie Policy
Effective date: 2026-05-10
Version: 2026-05-10
Plain English: We use only the cookies needed to keep you logged in safely. No analytics. No advertising. No third-party tracking.
1. What This Policy Covers
This Cookie Policy describes the cookies, local storage, and similar tracking technologies used by Market Sniper. It supplements the Privacy Policy.
2. What Is a Cookie?
A cookie is a small text file placed on your device by a website. Cookies allow the website to remember information about your visit, like your sign-in state. Local storage is a similar mechanism with larger capacity and no automatic transmission to the server.
3. Cookies We Set
3.1 Strictly Necessary Cookies
These cookies are required for the Service to function. You cannot opt out of strictly necessary cookies and continue to use the Service.
| Cookie name | Purpose | Lifetime | Scope |
|---|---|---|---|
Session cookie (SESSION_COOKIE_NAME per backend config) | Authenticates your active session. HttpOnly, Secure (in production), SameSite=Lax | Per SESSION_TTL_SECONDS configuration; deleted on logout | First-party |
Anonymous CSRF cookie (ANON_CSRF_COOKIE_NAME per backend config) | Cross-site request forgery protection for unauthenticated requests (signup, login). SameSite=Lax | Set during pre-auth flow; removed after authenticated session established | First-party |
3.2 First-Party Local Storage (Functional)
We use browser local storage for first-party UI preferences. These are not cookies; they do not transmit to our server.
| Storage key | Purpose | Lifetime |
|---|---|---|
shell-search | Remembers your recent in-app search history for the search component | Until you clear browser storage |
use-sidebar-collapsed | Remembers whether you have the operator sidebar collapsed | Until you clear browser storage |
3.3 Cookies / Storage We Do NOT Use
We affirmatively do not use:
- Analytics cookies — no Google Analytics, no Mixpanel, no Segment, no Amplitude, no PostHog, no Plausible, no Fathom, no other analytics SDK.
- Advertising cookies — no Google Ads, no Meta Pixel, no LinkedIn Insight Tag, no Twitter Pixel, no other advertising-network beacon.
- Social-media tracking — no Facebook Connect, no Twitter widget, no LinkedIn share, no Instagram embed.
- Cross-origin tracking — no third-party scripts loaded from external domains (other than as required for transactional email links if/when activated).
- Behavioral profiling — we do not build profiles of your behavior across sessions or sites.
If we ever add a non-strictly-necessary cookie or third-party tracker, we will:
- update this Cookie Policy and treat the change as material under the Privacy Policy version-update gate;
- deploy a cookie-consent banner that captures your opt-in or opt-out (where required by law) before any non-strictly-necessary cookie is set;
- notify you by in-app notice and email.
4. Third-Party Cookies
We do not currently set any third-party cookies. If we activate the Stripe payment processor in the future, Stripe will set its own cookies on its hosted checkout pages — those cookies are governed by Stripe's privacy policy, not ours.
5. Browser Controls
You can control cookies through your browser settings:
- Block all cookies — will break the Service (you cannot stay logged in without our session cookie).
- Block third-party cookies — has no effect on the Service today (we do not set third-party cookies).
- Clear cookies on close — will log you out at the end of each browser session.
Most browsers also support "Do Not Track" signals. Because we do not engage in cross-site tracking, DNT signals are effectively no-ops for us — we behave the same whether DNT is on or off.
6. Mobile and Other Devices
The Service is a web application. We do not currently distribute a mobile application. Browser cookies on mobile devices behave the same way as on desktop devices.
7. Changes
We may update this Cookie Policy from time to time. Material changes (such as the addition of any non-strictly-necessary cookie) will be communicated by in-app notice plus email and will trigger a cookie-consent flow before the new cookie is set.
8. Contact
Questions about this Cookie Policy: privacy@[domain]
Last updated: 2026-05-10