How information moves through this portfolio, its enquiry form and the email conversation you choose to begin.
1. Responsible professional and scope
This portfolio identifies MIRZOAZAMJONI SOBIROV, an independent professional using the public name Mirzoazamjoni Sobirov, at Oqqorgonlik kochasi 64, 130100, Jizzax, Uzbekistan. 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 enquiry form asks for your name, reply email, an optional company or project name, a project interest and your message. You may include a desired output, audience, format, deadline or relevant project context. These details help define the conversation you are proposing. Please leave out identity documents, passwords, payment card details and unrelated sensitive information. There is no file upload field. If project files become necessary later, agree an appropriate transfer method before sharing confidential material, rather than adding it to an initial enquiry.
3. What the form actually does
Typing into the form changes the current page in your browser. Selecting “Prepare email draft” creates a preview containing those entries and a link that can open your chosen email application. The authored form has no server submission endpoint. Preparing the draft does not send an email or create a booking. Information can reach the recipient through this route only if you take the separate sending action in your email service. You can edit the preview, abandon the draft or close the page before choosing to send anything.
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
If an enquiry is received, its relevant contents can be used to understand the proposed design work, ask clarifying questions and discuss scope. A conversation that develops into a project may require separate records of agreed deliverables, permissions, correspondence and administrative arrangements. The website does not decide those arrangements automatically. Providing a project enquiry is not a request for an unrelated advertising subscription. If you ask about an existing conversation, include enough context to identify it without resending unnecessary personal or confidential details. Further purposes should be explained when they arise.
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 authored pages use device fonts and load styles, images and the interaction script from this site's own paths. The authored enquiry script does not write cookies, local storage or session storage. It keeps entered values in the open page so you can review your draft. Browser autofill, history, caching and restored tabs may preserve information according to your browser settings. Hosting or security layers can have separate technical behavior. You can use your browser controls to inspect or clear site data and control autofill; those controls operate independently of this form.
8. Analytics, email protection and links
Cloudflare delivers the pages and may add Web Analytics for traffic and performance measurement, email-address protection, and network error reports using browser reporting headers. Such reports can contain connection, browser and resource information. These delivery features are separate from the enquiry form, which has no server submission endpoint. The authored pages use local assets and do not embed a social feed or video player. Your email service has its own policies when you choose to open or send a draft. Inspect browser site-data controls and the published page behavior when deciding what to share.
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
The authored form does not create a separate website database of enquiries. Copies in an email application, sent folder, inbox, backup or project record are different from the browser preview and may have different retention needs. The applicable retention period depends on the purpose and requirements of the relevant record. To ask about a particular message or request deletion, contact [email protected] and identify the relevant conversation. Any response should distinguish records that can be removed from records that may need to be retained for an applicable obligation or an ongoing matter.
11. Security and practical choices
No online method offers an absolute security guarantee. Keep the initial enquiry limited to what is needed to discuss the design task. Confirm the address shown in your email application, use a device and account you trust, and avoid including access credentials or private third-party data. The portfolio does not ask for account registration or payment credentials. If you notice a suspected issue involving this website or a message associated with it, describe the issue through the contact channel without sending exploit files, unnecessary private content or credentials in the report.
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.