Privacy at Icelamp
Icelamp publishes icefield concepts and design records for anyone to read. Browsing the archive does not require registration, a character profile or a purchase. The communications form is optional. This operational reference distinguishes its saved correspondence from technical requests generated while viewing a page, and states the retention mechanism actually configured for this site.
The correspondence lifecycle
Communications register
The form receives a name, an email address and the text of the message. The name and text are saved in a private website record, with the reply address attached to that record. Administrators can review it in the management interface. It is not a public archive entry or a comment below a Melt Record. The handler saves the enquiry rather than automatically subscribing the sender to a publication. It also does not transfer the written fields to Histats. Describe the page, diagram or proposed mechanic you mean; identity documents and sensitive personal background are not needed for an initial design question.
Retention mechanism
The website schedules a daily cleanup task for private contact messages older than ninety days. Those records become eligible for removal after that age. Because the task depends on the website scheduler running, this is not a guarantee of deletion at an exact hour on day ninety. The routine concerns the active message database, not every backup or technical log. You may request an earlier correction, access or deletion through Contact. Identify the email originally used and the approximate date, without reproducing more of the conversation than necessary. An administrator may need clarification before acting on an ambiguous request.
Technical appendix: requests and measurement
Request handling
The form uses a short repeat-attempt check based on a hashed connection address. That temporary marker is separate from both the saved message and the ninety-day cleanup process. Cloudflare handles website delivery and security, while the origin server processes the requests needed to serve pages and assets. Infrastructure logs may include technical connection details. We cannot describe deletion of an active message as immediate erasure of every trace held by those separate systems.
Audience measurement
Histats code is installed on public pages. Measurement requests contain the visited URL and browser information, and the remote service receives the network address associated with the connection. Cookies or similar identifiers may be involved. The configured counter aggregates visits across several sites operated through the same management platform; it is not an Icelamp-only total. Browser privacy controls can restrict external scripts or cookies, but cannot remove an existing enquiry here. Provider notices are linked below. Contact the observatory for questions about its own stored correspondence. Configuration reviewed: 15 November 2026.
Provider information: Histats privacy information · Cloudflare privacy policy. Contact the studio about a record held here.