Visiting the site and Cloudflare hosting
Visiting LayerBench3D requires requests to Cloudflare Pages to obtain pages, images, styles, scripts and search resources. These exchanges communicate your IP address and technical information about the request and browser.
Cloudflare documents processing technical data to provide and protect its services, including logs that may concern visitors. A static site therefore does not mean that no personal data is processed.
The scope of logs actually retained for this project, who can access them and their retention periods are not confirmed. No numerical retention period is stated without verification. Cloudflare operates internationally; processing locations and applicable safeguards must be checked against its documentation and the account’s terms.
Cookies, storage and third-party services
The current LayerBench3D code adds no advertising cookie or audience analytics and does not store tool inputs in localStorage, sessionStorage or IndexedDB. Only an explicitly selected currency code may be saved in localStorage (key site.currency) to retain that preference between pages. No amount, file, history or banking information is saved there. The preference can be reset; if storage is unavailable, it applies to the current page only. The project has no visitor account, advertising, affiliation or contact form.
The publisher reports that Cloudflare Web Analytics, Zaraz and Turnstile have not been enabled. The pages and journeys checked do not load third-party audience analytics. Application resources are served by this site; external source links open the relevant websites if you choose to follow them.
The browser may retain site resources in its normal cache. Depending on the configured protections, Cloudflare may use technical mechanisms, including certain security cookies. Their presence must be reassessed if configuration changes. No tracker requiring consent has been identified in the checked journeys, and no consent banner has been added.
Pagefind search
Search uses an index built from published site pages. Pagefind loads its code and required index fragments from the hosting service, then processes searches in your browser.
LayerBench3D does not send entered search text to a search API or AI API. Downloading Pagefind resources nevertheless involves network exchanges with Cloudflare. Files selected in the analyzer and their results are not added to the public index.
Calculators
The three calculators—printing cost, filament mass/length and model scaling—run their formulas in the browser. These tools send neither entered values nor results to a server and save no account record or application history.
The page and scripts are downloaded from the hosting service first. That loading is separate from local calculation. Closing or reloading the page may discard entered values. Currency reference data is supplied with the static site; no external rate service is called during a conversion.
STL and G-code files
After explicit selection or dropping a file, a Web Worker reads it in memory on your device. The current code sends neither its contents nor its filename to the server for analysis. No upload, history or application storage of the file is provided.
Network checks of selection, dropping, analysis, cost calculation and reset journeys show no request triggered during those operations. This observation applies to the tested version and journeys; it is not an absolute guarantee against a browser extension, compromised device or future site change.
Removing the file discards the tool’s references and resets the display. This does not guarantee secure erasure from device memory. The analyzer is read-only: it does not execute G-code or send it to a printer.
Roles of the publisher and Cloudflare
Roles must be distinguished for each processing activity. A controller determines purposes and means; a processor acts on the controller’s behalf and instructions.
Cloudflare states that it acts as controller for some activities and processor for others, including certain customer logs. Its general policy alone does not assign every LayerBench3D processing activity to one role.
The allocation applicable to the account and services, recipients, legal bases for publisher-controlled processing and safeguards for international transfers are not confirmed here. No account-specific retention period or contractual safeguard is asserted without verification.
Messages sent to LayerBench3D
The public contact address [email protected] uses Gmail. If you choose to write, your sender address, message and any attachments are processed by the email services involved, including Google, and received by the publisher to handle your request and reply.
The contact link opens your email software or service. It does not automatically transmit calculator data or files selected in the analyzer. Avoid attaching sensitive information or information unnecessary for your request.
The legal bases, retention periods or criteria, people authorised to access the mailbox and terms applicable to any international transfers remain to be specified for this processing. The Gmail account settings have not been inspected; no contractual safeguard or retention period is assumed.
Rights and contact
Depending on the processing and GDPR conditions, your rights may include access, rectification, erasure, restriction and objection. You may lodge a complaint with the French data protection authority, the CNIL.
For questions about your data or to exercise rights towards the publisher, write to [email protected]. This dedicated address does not replace other legally required identification and contact information and does not by itself establish a right to anonymity.
The identity and contact details of the controller for publisher-controlled processing, its legal bases, recipients and retention periods or criteria are not yet fully specified. In its present state, this policy therefore does not constitute finalised GDPR information.
For processing under Cloudflare’s responsibility, its policy specifies roles and dedicated channels. [email protected] is Cloudflare’s contact, not the contact address for LayerBench3D.