Skip to content
MASHKHURBEK
IBROKHIMOV

Website information / Updated 20 October 2026

Privacy policy

Information in the browser, network delivery and voluntary correspondence.

Mashkhurbek Ibrokhimov presents this website, with the identification address Alisher Navoiy shoh ko'chasi 29a, 140000, Samarqand, Özbekistan. Questions about information associated with freelance project discussions can be raised through [email protected]. This notice concerns the published pages and the email-draft tool. It distinguishes information visible inside the browser from correspondence a visitor independently decides to send. The pages do not establish the internal practices of a visitor’s own network, device or email service. A later commercial arrangement may need additional information appropriate to that arrangement.

The enquiry asks for name, reply email, optional company or project, interest and message. There is no file upload, login or payment field. A prospective brief can include audience, output and medium. A summary is usually enough to introduce a layout question. Do not disclose unpublished customer research, named participants or an entire confidential content set just to explain a visual preference.

The draft preview preserves the selected study so a visitor can refer to Field Notes, Wayfinding or Rhythm accurately. It does not create a freelance booking, submit a real brief for approval or authorise publication of the visitor’s project. The form creates a local preview and a separate link to the device’s email application. It does not post fields to a website database. You review and send separately; the email service handles that step under its own policies. A prepared draft is not delivery confirmation.

cPanel hosting and Cloudflare delivery are used to serve the pages. A request can include an IP address, resource URL, request time, browser characteristics and protocol information. Hosting and network services may handle these technical records to deliver resources, diagnose faults and protect infrastructure. The absence of a website enquiry database does not mean that infrastructure has no records. Technical delivery data is separate from the message text you type in the form; this notice does not promise anonymous access or a particular provider log-retention period.

The authored script does not set cookies or write local storage or session storage. Original illustrations, styles and scripts use local site paths. Browser history, cache, autofill and restored tabs depend on your device settings. Cloudflare may add traffic and performance analytics, email-address protection and network-error reporting at its delivery layer. Those features can process resource and connection information independently of the form preview. The site contains no authored advertising pixel, social feed, external video player or online payment control. Browser controls can inspect and clear site data.

A creative discussion can involve supplied content, proposed outputs and the people responsible for approvals. The portfolio’s fictional examples contain no visitor data. A real brief needs its own decisions about confidential material, project recipients and factual approval; those choices cannot be inferred from a concept page. Handling must follow the purpose and applicable grounds, such as steps requested before an agreement, performance of an agreement or legal obligations. A distinct consent-based purpose needs its own explanation and choice. An enquiry does not enrol a visitor in unrelated promotions.

A project reference, approval note and initial idea can have different purposes and record requirements. Ending a conversation does not automatically settle the retention of an accepted commission’s correspondence. The public preview remains distinct from any later working files or approval records. Network and email providers can operate in different countries. A record’s purpose, applicable obligations and unresolved matters influence retention. No universal provider deletion schedule is promised by this page.

Contact [email protected] to identify a conversation you want to ask about, correct or have reviewed for removal. Give enough context to locate the information without disclosing unnecessary identity documents. Depending on applicable law, rights can include information about processing, access, correction, deletion, objection or withdrawal of consent where relied on. Conditions and exceptions may apply. A request should distinguish your own data from business specifications or material belonging to someone else. Complaints may also be raised with a competent authority under the rules that apply. Use a brief or conversation reference when asking about information associated with a project. Clarify whether you are asking about your contact details, another contributor’s comments or a proposed use of unpublished work. Sending a brief does not automatically authorise a public case study.

The folio does not ask for passwords to a publishing platform or private design repository. If implementation later requires access, that must be scoped separately. The enquiry is not an access-management system or a channel for granting unrestricted control over another organisation’s material. Use a device and email account you trust. Confirm the recipient before sending. The initial contact does not create a confidentiality agreement, and no online method supplies absolute security.

The revision shown on the page identifies the published version. A change to the enquiry interface, infrastructure or commercial workflow can require a corresponding update. A new website notice does not silently change a separate agreement governing earlier records. Read the form explanation when using it, and ask about any processing requirement that affects your decision before sending material. The Contact page identifies the same enquiry route, while the Terms explain how a conversation differs from an accepted order or commissioned project.

The portfolio’s concept studies are public fictional briefs. Your own proposed project may involve unpublished text, designs or information about collaborators. Use a summary for the first conversation rather than disclosing an entire confidential brief. No confidentiality undertaking arises from preparing a message preview. Before sending working files, identify permissions, recipients and a suitable transfer route. Sample content can often explain a layout question without exposing real customer data, private research participants or credentials for a production system.

A potential freelance engagement may later involve an agreed brief, revision notes and approval correspondence. Names attached to comments and approvals can be personal information even when the main subject is a design. Clarify who is entitled to approve work and how other contributors should be contacted. Publishing an example in this portfolio does not authorise publication of a visitor’s project. Any later use of commissioned material as a public case study needs its own permission and accurate description, distinct from this enquiry workflow.

Related information: Company details · Contact · Privacy policy · Terms of use.