1. NO ACCOUNTS. We do not collect emails, names, or profiles. Your IDENTITY_KEY stays on your device and is used only to derive a consistent anonymous handle.
2. NO TRACKERS / NO ADS. ICESS does not run analytics trackers, ad pixels, fingerprinting scripts, or third-party marketing beacons. We do not sell data. We do not share data for advertising.
3. COOKIES. Public pages do not require cookies to function. If your browser receives any cookies, they are limited to essential platform/session behavior (for example, when an administrator is logged in). No tracking cookies are used for visitors.
4. IP HANDLING (ABUSE PREVENTION ONLY). To defend the service, we compute short-lived hashes of network signals (e.g., IP hash + user-agent hash) to enforce rate limits and verify the anti-abuse challenge. These hashes are not stored with your public entries and expire automatically (seconds to ~1 hour depending on the limit window; challenge data expires in minutes).
5. PUBLIC RECORD WARNING + GDPR NOTES. Content you submit (event summaries, discussion text, source URLs, and uploaded artifacts) becomes part of a public archive. Do not post sensitive personal data. For EU/UK-style privacy regimes, our legal basis is legitimate interest (operating a public archive and preventing abuse). You can request removal of personal data you control by contacting us, but remember: copies may exist in third-party caches, mirrors, and screenshots.
Comments
2 responses to “EVENT-2026-F37B”
jdxkxkkx