FluidCell.eu uses self-hosted website analytics to measure visits and understand which resources readers use. Reading an article does not require an account. The website does not set advertising or analytics cookies.
Website analytics
Our analytics service runs on our own infrastructure. When analytics is enabled, your browser loads a small tracking script and sends page-view information to that service. We use these statistics to improve navigation and decide which technical subjects need better coverage.
The information includes the page path and title, referring website, time of the visit, browser, operating system, device type, screen size, language and approximate location derived from the connection. The analytics service processes the connecting IP address to estimate location and generate a hashed session identifier. It does not store the raw IP address in its analytics database. Hosting and proxy logs can contain separate request information.
We exclude our page URL's query string and fragment from analytics. Search terms, contact-form fields and messages are not sent to the analytics service. We do not use session replay, advertising profiles, account identifiers or custom interaction events. Analytics records are stored in our private analytics database until the operator deletes them; there is currently no automatic analytics retention limit. The 30-day retention period below applies to contact messages only.
The tracker respects your browser's Do Not Track setting. You can also use browser tracking protection or a content blocker to restrict analytics requests. Reading the site and using the contact form work with analytics blocked.
Contact messages
The contact form collects the name you choose to provide, your email address, the message category, an optional article reference and your message. These details are used to assess and respond to the enquiry. Do not include confidential research, credentials or sensitive personal information.
Messages are saved to a private server-side inbox. They are not displayed publicly or sent to an external form provider. A confirmation means that the message was saved. It does not mean that it has been read or that a response is guaranteed.
Contact records are retained for 30 days. The inbox applies expiry during submission and administrative access. The server's hourly retention job removes expired records even when no new message is submitted. A technical correction can be retained as an editorial record without the sender's contact information.
Abuse prevention
The form limits repeated submissions. It uses a keyed, one-way token derived from the connecting address for a short-lived rate-limit record, instead of storing the raw address in the contact database. Those records expire after one hour. The operator's web server or hosting provider may keep separate access logs according to its configuration.
Browser storage and external links
The contact form keeps its current input in memory while the page is open. It does not store the message in browser local storage. The site serves its fonts and diagrams locally.
External sources have their own privacy policies. No external source is loaded as an embedded reader. Following a citation navigates to the source's website.
Requests about a message
Use the contact form to request access to or deletion of a submitted message. Include the email address used for the original enquiry and enough context to identify it. Do not provide an identity document through the form. Verification can be arranged where necessary.
A substantive published correction may remain in the article after its associated contact record expires. The correction record should describe the technical change without publishing private contact details.