Privacy policy
16 November 2026
How information moves through this portfolio, its enquiry form and the email conversation you choose to begin.
1. Website identification and scope
This portfolio is presented under the name Asim Ciceksay. The About page gives the identification details used on this website. Privacy questions about the site or any correspondence can be prepared using [email protected]. This notice covers the requests your browser makes to load the portfolio and the information you choose to put into a draft. Your browser and email application also have their own settings and data practices.
2. Fields in the message tool
The contact panel accepts a reply address and a name. A topic menu identifies a study or general feedback. A separate box accepts the note itself, with a label for an optional company or project. The numbers printed in the fictional library chart are fixed example values. They do not come from visits to this website, and the message fields do not update them.
3. Editing and previewing a message
The button builds a preview on the current page. The draft text is built from the visible fields and stays in the browser at that point. Choosing a topic only changes the form. The link in the preview hands the address and message to the email handler configured on the device. Sending from that handler is a distinct action under the visitor’s control.
4. The visitor’s mail settings
A device can hand an email link to a desktop program or to a browser based mail service. Settings on that device determine which application opens. Review the recipient, subject and contents there. The mail provider may store unfinished drafts or sent copies according to its own arrangements. Neither an open window nor a draft preview establishes that a recipient received a message.
5. Purposes of an enquiry conversation
If a message arrives, the information in it can help identify the study or page in question, clarify a correction or reply to an enquiry. Access to the static site does not require an account. Technical data serves a different purpose from message content. For example, connection details may help a delivery provider respond to network issues, while an email address supplied in a message may enable a reply. The appropriate ground for processing depends on the purpose and the applicable rules.
6. Requests to deliver the chart
An internet connection is needed to obtain HTML, the chart image and the small script for the message tool. Those requests ordinarily include browser and connection details. A provider can use delivery information to serve the requested file, troubleshoot a failed connection or protect the service. In contrast, the labels and counts shown as the visual example are editorial content and stay the same for each visitor.
7. What the source pages store
The portfolio code uses the current document to hold form entries and the preview. It adds no local database, storage key, account session or saved preference. A browser can still cache a local resource or retain a field through its own autofill features. Controls for clearing that information live in the browser. Hosting and network services run independently of the authored page code.
8. Analytics, email protection and links
The site is served through Cloudflare and origin hosting. Network and security features can process request details, connection information or browser information independently of the enquiry preview. Some configurations can add performance measurement or protect visible email addresses. The authored pages contain no advertising tags, third-party media embeds, uploads or payment controls. The domain name displayed on a page is not proof of mail delivery. An outgoing draft is handled by the visitor's selected email application or provider.
9. Handling by website and mail providers
Website delivery and a later correspondence can involve separate infrastructure. An email sent by the visitor can pass through systems operated by the sender’s provider and the recipient’s provider. Their processing locations depend on their services. The portfolio does not offer a choice of processing region. It also provides no file channel for sending a dataset or opening a private shared document.
10. Where a copy may remain
The web preview is not an inbox, a submitted record or a saved ticket. An application can retain its own draft, outbox or message copy. Delivery infrastructure can keep technical records for operating and securing its service. Requests about information in a received email should identify the exchange. There is no single retention period stated for the browser, network and mail systems.
11. Keeping an enquiry narrow
A chart question can usually identify the page, label and displayed value. Leave out passwords, payment details and data about other people. If reporting a display problem, a description of the browser and the relevant label is usually a better starting point than sending other tabs, network logs or an entire screenshot with account details in view.
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.