NeedToWatch
쿠키 정책
최종 업데이트: 2026-06-13
This Cookie Policy explains how NeedToWatch (“we”, “the Service”) uses cookies and similar storage technologies when you visit needtowatch.net or use the NeedToWatch mobile app. It complements our Privacy Policy.
1. What is a cookie?
A cookie is a small text file a website stores on your device. We also use localStorage, sessionStorage and HTTP-only auth cookies set by the server — they all serve the same purpose: holding on to a piece of state between page loads.
2. Categories we use
| Category | Purpose | Lifetime |
|---|---|---|
| Strictly necessary | Sign-in session (HTTP-only access/refresh cookies), CSRF guards, locale routing | Session → 30 days |
| Preference | Theme (light/dark), language, story-strip seen markers | 12 months |
| Analytics (aggregate) | Anonymous usage counts on internal admin dashboards. We don't set 3rd-party analytics cookies. | — |
| Advertising | Google AdSense may set cookies to serve ads relevant to you. See §4. | Up to 13 months |
3. Why we use strictly-necessary cookies
Without them you can't stay signed in, the language toggle resets on every page load, and any “remember my watchlist” action breaks. You can't disable these without breaking the Service — if you do, your browser will simply log you out every navigation.
4. Advertising — Google AdSense
NeedToWatch is ad-supported. We render Google AdSense ad-units in designated slots (between home rails, in feed, etc.). Google may set cookies on your device to:
- Limit how many times you see the same ad (“frequency capping”).
- Measure ad effectiveness in aggregate.
- Serve personalized ads based on your prior browsing across sites that use Google's ad network.
You can opt out of personalized ads at adssettings.google.com. For the EU, additional consent is presented via the standard Google CMP. See policies.google.com/technologies/ads for the full description of cookies Google may set.
5. Third-party services we use
- Google AdSense — ads. Sets its own cookies (see §4).
- TMDB — catalog data only, fetched server-side. No client-visible cookies.
- OAuth providers (Apple, Google) — only when you sign in with them. They set their own session cookies on their domain; we never see them.
6. Managing cookies
Most browsers let you block or delete cookies via Settings → Privacy. Blocking strictly-necessary cookies will sign you out and reset language preferences on every visit. Blocking advertising cookies still lets you use the Service — you'll just see non-personalized ads.
7. Mobile app
The mobile app doesn't use HTTP cookies. It stores the same kinds of state (auth tokens, language preference) in the device's secure keystore and AsyncStorage. Clearing the app's data signs you out and resets preferences.
8. Changes
We may update this policy as our cookie use evolves (e.g. when a new ad partner is onboarded). Material changes will be announced in-app or by email.
9. Contact
Questions about cookies: [email protected].