Cookie and Local Storage Policy
1. Essential cookies
GEMC2 uses essential cookies for authentication and request security. The intended production configuration uses a lifetime of up to 30 days for the authentication and CSRF cookies. The effective lifetime is controlled by the server's SESSION_TTL configuration, and a session may end earlier if you log out, the session is revoked, a security action is taken, or your browser removes cookies. Continued activity does not guarantee that the browser cookie's own expiry will be extended.
| Cookie | Purpose | Lifetime | Attributes |
|---|---|---|---|
gemc2_session | Maintains your authenticated session. | Up to 30 days under the intended production configuration; actual lifetime depends on server configuration. | Secure, HttpOnly, SameSite=Lax. |
gemc2_csrf | Helps protect account actions against cross-site request forgery (CSRF). | Uses the same configured lifetime as the session. | Secure, SameSite=Lax; readable by the browser application to send a CSRF header, so not HttpOnly. |
2. Local storage and service-worker cache
The application stores gemc2_version in localStorage to detect application-version changes. GEMC2 also uses a service worker to cache the application shell and static same-origin resources so the app can load and update more reliably. In the source reviewed, API responses are fetched directly rather than stored in the service-worker cache.
Clearing site storage may reset the version marker or remove cached application files. Clearing cookies may sign you out. Local storage and cached application resources are stored by your browser on your device; they are separate from account and content data stored on GEMC2's server.
3. Analytics and advertising
No advertising, behavioral-advertising, or analytics SDK was found in the application files reviewed. GEMC2 does not intentionally use Google Analytics, Meta Pixel, TikTok Pixel, or similar advertising trackers. Hosting, DNS, security, browser, and push-delivery providers may process technical request or delivery metadata according to the services configured to operate the site. This is not a promise that a browser or external provider never uses its own technical storage.
4. Push notifications
Push notifications are optional and require permission from your browser/device. If you enable them, the browser creates a push subscription and GEMC2 stores the endpoint and subscription keys needed for delivery, together with user-agent information. Current social-activity notifications may display an actor's name and activity type. Your device or browser may display notifications on a lock screen depending on your settings. You can turn notifications off in GEMC2 settings or your browser/device settings.
5. Managing cookies and storage
You can block or clear cookies and site storage in your browser settings. Blocking essential cookies may prevent sign-in or authenticated actions. Browser-specific menu names may change; consult your browser's current help instructions. Removing local data does not necessarily delete information already stored on GEMC2's server, public content copied by other people, or data held on another user's device.
6. Changes
If GEMC2 adds materially different cookies, tracking technologies, or local-storage functions, this page will be updated and notice will be provided where required by law.
7. Contact
Questions: [email protected].