Privacy, without assumptions.
This draft explains the intended form behavior, but the controller identity, legal basis, retention period and rights contact must still be supplied and professionally reviewed.
Contact forms may collect identity, contact details, project information, budget, timing and links voluntarily provided by the visitor.
The form reports success only after the configured email provider accepts the message. When delivery credentials are absent or delivery fails, the interface states that the inquiry was not sent. Inquiry content is not stored in the site database.
Server-side validation, a honeypot and rate limiting are designed to reduce abuse. Rate limiting stores only a rotating secret-keyed fingerprint and counters, never names, messages, email addresses or raw IP addresses.
Direct 3D file upload is disabled until private storage, access controls and a deletion policy are configured. Do not submit confidential files through an unapproved public link.
Cookie information