Cookie & Tracking Notice

Version: 2026-09-08Effective: September 8, 2026Applies to: Web apps, embeds, mobile-equivalent storage

Cookies, local storage, SDK identifiers, pixels, and similar technologies (“technologies”) help Zeeker sign you in, remember choices, protect the Services, and—only when permitted—measure use.

Terms acceptance is not cookie consent. Strictly necessary technologies operate to provide the Service. Optional analytics remain off until you choose them where prior consent is required. Where law permits an opt-out model, analytics may be enabled by default and you can turn them off at any time. Zeeker keeps optional analytics off when your browser sends Global Privacy Control.

Manage your choice

Strictly necessaryAuthentication, security, load balancing, and your saved legal choices.

Always on

AnalyticsHelps Zeeker understand aggregate app usage and reliability. Starts only after you opt in.

Off

You can reopen these controls from this page or the Legal & cookies control in a Zeeker app. Browser deletion may reset the choice. If your browser sends Global Privacy Control (GPC), Zeeker keeps optional analytics off and treats the signal as an opt-out of covered sale, sharing, and targeted advertising where applicable.

Technologies Zeeker uses

Category	Examples	Purpose	Typical duration
Authentication	HttpOnly refresh/session cookies, session family and anti-forgery state	Sign in, refresh sessions, prevent replay and cross-site attacks	Session to about 30 days, or earlier logout/revocation
Security and routing	Rate-limit, abuse, load-balancer, device/session signals	Protect users, APIs, and availability	Session to 24 months depending on risk
Preferences	Theme, community/admin mode, role, Explore preferences, language	Remember choices across pages or apps	Session to 12 months
Legal choices	zeeker_cookie_preferences, versioned terms acceptance status	Remember cookie preference locally; acceptance evidence is also account-backed	Cookie choice up to 12 months; acceptance retained as described in Privacy Policy
Analytics (optional)	Google Analytics identifiers such as _ga and _ga_*	Aggregate usage, page flow, performance, and reliability	Commonly up to 13 months, subject to configured provider controls
Third-party video	YouTube-hosted thumbnails and the privacy-enhanced YouTube player	Show a public video preview and, when loaded, deliver playback	Request/session data and provider-controlled storage as described by Google/YouTube

Names may change as security and browser technology evolves. HttpOnly values cannot be read by page scripts. Zeeker does not place full passwords in cookies or local storage.

Third-party content

A YouTube card may load a YouTube-hosted thumbnail before the player is active. That request can disclose ordinary network and request information, including IP address, browser/device details, referring page, and request time, to Google or YouTube. Zeeker does not preconnect to YouTube or Google video hosts merely because a page might later contain a video.

Zeeker uses the privacy-enhanced YouTube player. Depending on the surface, the player loads when an eligible video becomes mostly visible for muted autoplay or when you select play or unmute. Player loading and playback can involve Google/YouTube cookies or similar technologies and processing under the Google Privacy Policy. By using Zeeker, you agree to the YouTube Terms of Service. You can avoid player loading by not activating a player and, on autoplay surfaces, by scrolling past before the video is mostly visible.

A connected OAuth provider may receive device, page, or account information when you activate the connection. A publisher site hosting a Zeeker widget may use its own technologies; consult that site’s notice as well.

Mobile apps

Mobile apps use platform permissions, secure token storage, push tokens, and SDK identifiers that perform functions similar to cookies. Change OS permissions and advertising/privacy settings on your device. Optional analytics SDKs follow the same regional consent or opt-out rule.

Regional consent and opt-out standards

Where consent is required, Zeeker:

• does not load optional analytics before an affirmative choice;
• provides equally prominent accept and reject actions;
• avoids prechecked optional categories;
• records the preference version and time;
• lets you withdraw as easily as you gave consent; and
• asks again when purposes or vendors materially change or the preference expires.

Where law permits an opt-out model, Zeeker may enable optional analytics by default. Zeeker provides clear notice and an in-app control to turn analytics off at any time, preserves a saved choice across supported Zeeker apps, and does not make access to core features depend on leaving analytics enabled.

In every region, Zeeker honors your saved choice, keeps optional analytics off when GPC is active, and does not treat acceptance of the Terms as a cookie preference.

Necessary technologies do not require consent where law exempts them, but remain subject to transparency, minimization, and security duties.

Browser controls

You may block or delete technologies in browser settings. Blocking strictly necessary storage can prevent sign-in, security, chat, publishing, preference, or embed functions. “Do Not Track” is not a consistent legal signal; Zeeker responds to GPC and other recognized universal opt-out mechanisms as law requires.

For questions or a tracking-rights request, use Your Privacy Choices or the Request Center.