Information used while exploring Andrea Donini’s technical drawing and cad visualization portfolio, preparing a project outline and deciding whether to start an email conversation.
1. Responsible professional and scope
This portfolio identifies ANDREA DONINI, an independent professional using the public name Andrea Donini, at Ulenpas 74, 5655 JD Eindhoven, Netherlands. Privacy questions can be addressed in an email draft to [email protected]. This notice describes the public portfolio and its enquiry interface. It also explains the boundary between information entered on a page, information handled by the services that deliver the page, and information you separately decide to send by email. It does not describe the internal practices of your own device, network or email provider.
2. Information you choose to provide
The project outline can contain your name, reply email, optional company or project name, selected area and message. For technical drawing and cad visualization, useful context is reference drawings, the intended diagram use, source-file format and required viewpoints. Only enter material you are entitled to share. An initial outline does not need proprietary assemblies, non-public technical specifications and operational security details. There is no attachment control or request for an identity document. If a later project requires original files, first agree the transfer route, the intended purpose and the people who may access them. The form keeps a preview in your current page; it does not create an enquiry record on a website server.
3. What the form actually does
The technical-drawing outline is prepared within your browser. It can combine a selected drawing service, contact details and a description of the required view in a draft preview. No CAD model is uploaded, opened or converted by the page. Joint 01 and Profile 02 are fixed local illustrations rather than an input tool for real geometry. You separately choose whether to open the draft in an email application and send it. That action is outside the website’s local preparation step, and delivery is not confirmed here.
4. Email and communication providers
Opening a mailto link passes the draft to the email application or service configured on your device. That provider may handle addresses, message contents, device details and its own service records under its policies. When you send a message, delivery can involve your provider, network services and the recipient's provider. This portfolio cannot control those systems, confirm that they have accepted a draft, or verify successful delivery. Check the final recipient, contents and any attachments in your email application before sending, especially when more than one email account is configured.
5. Purposes of an enquiry conversation
A first drawing conversation can start with the intended diagram use and a description of the available references. Avoid sharing proprietary assembly files, access credentials or sensitive operational details without an agreed route and permissions. A simplified sample can explain the visual question while keeping unnecessary engineering information out of an initial email. If source geometry is required for a commissioned task, identify its permitted recipients and use before transfer. The public enquiry does not provide a protected CAD repository or establish a technical confidentiality arrangement.
6. Website delivery and technical data
Requesting a web page necessarily sends connection information to the infrastructure serving it. This can include an internet protocol address, the requested resource, approximate request time and browser or protocol information. Hosting, content delivery and security providers may process such information to deliver resources, handle failures or protect their networks. Their operational settings and applicable terms govern their own processing. A public page cannot establish every provider's logging or retention behavior. This notice therefore does not promise anonymous browsing or that the delivery infrastructure keeps no records.
7. Local assets, cookies and browser storage
The illustrated technical views are delivered as local vector images. Their annotations do not read files from a visitor’s device or query a model server. Local type and interaction resources support the static pages, and the authored script does not write a model cache, cookie or browser-storage entry. Form values remain in the current document for review. Device autofill, page restoration and network-service logging can still apply separately. Check the relevant browser and provider controls when handling information that is sensitive in a real engineering setting.
8. Analytics, email protection and links
Cloudflare delivers this portfolio and may add Web Analytics for traffic and performance measurement, email-address protection and network error reporting headers. These features can process request, connection, browser and resource information independently of the local enquiry form. The page itself does not submit form fields to a website database. Its fonts and original example assets load from local paths. There are no social feeds, external media embeds, payment controls or file uploads. Your email provider has its own policies when you decide to open or send a draft. Browser site-data settings let you inspect and manage data held on your device.
9. Access, recipients and locations
An email discussion may be handled using communication and hosting services that operate in different countries. The site does not infer a visitor's residence from its English language or select a jurisdiction for them. Necessary service providers can process information within their roles, while any additional project recipient or collaborator should be addressed as part of the engagement discussion. Do not assume that sharing material through an initial enquiry establishes a confidentiality arrangement. If location, access restrictions or a particular transfer method matter to your project, raise those requirements before transmitting the material.
10. Retention and deletion requests
An outline kept on this page is not the same as a source drawing sent during an engagement. Email providers, sent folders and later project records may retain separate copies for their purposes. There is no universal retention period stated for every technical reference or agreed deliverable. A correction or deletion request should identify the drawing conversation and relevant material, while avoiding unnecessary retransmission of proprietary models. Actual handling may need to distinguish removable correspondence from information retained for an obligation or an unresolved project matter.
11. Security and practical choices
Technical references may reveal proprietary component details or operating information. The first message can identify the diagram’s purpose without disclosing an unrestricted model or internal access credentials. If the work needs source geometry, agree how it is transferred and who may use it before sharing. A local drawing example does not certify the safety of that transfer. The enquiry asks for contact and project context only, with no model upload, password field or payment request. Verify the email recipient when moving beyond the preview.
12. Requests, children and updates
You can use the contact email to ask about information associated with your own enquiry, seek a correction, object to a proposed use or request removal where applicable. The appropriate handling depends on the request and relevant obligations; this notice does not replace rights that apply to you. Someone acting for another person should explain that authority. The portfolio is intended for professional design enquiries and is not directed at children. The notice may be updated when the site or communication workflow changes; the displayed revision date identifies the current published version.