HazırSoft

Privacy policy

Bir talep gönderdiğinizde oluşan kayıtları, siteyi kullanırken devreye giren araçları ve gizlilik tercihlerinizin farklı iletişim kanallarında ne anlama geldiğini açıklıyoruz.

This privacy policy distinguishes the information you share when describing a project to HazırSoft from the technical records created as you browse. It explains the separate contact and website-use processes on www.hazirsoft.com. The website presents services and receives inquiries; it does not offer visitor accounts, product sales, or online payments.

Business identity and legal review

HazırSoft is the trading name used on this website. This page does not identify the data controller’s full legal name or an address for service of notices. For privacy questions, write to [email protected]. This policy has not been reviewed by a lawyer, and it does not provide complete legal-identity or formal request-submission details. It is an explanation of the website’s data practices, not confirmation of full legal compliance or the findings of an audit.

Information you provide with an inquiry

  • Project quote: We collect your first and last name, email address, phone number, service selection, and project description. Your business name and approximate budget category are optional.
  • Contact: Your name, email address, subject, and message are used to understand your inquiry and send a reply.
  • Newsletter: Subscriptions use your email address. To unsubscribe, use the option in the email or write to [email protected].
  • Support conversation: Your messages, any name and contact details you add, and files you send make up the conversation record.

Do not enter payment card details, identification numbers, health records, or unnecessary information about other people. To explain a software requirement, use sample records without personal information rather than sending real customer data.

Inquiry content is processed to assess requirements, answer questions, and prepare proposals. Security records help assess spam, automated requests, and misuse. Relevant records may also be considered where a legal obligation or protection of a right requires it. Selling or renting personal data for marketing is not the purpose of these processes.

Browsing records and correspondence are different

Server and security tools may process technical data such as IP addresses, browser and device information, pages accessed, and access times. Usage analytics involves other information, including traffic sources, content viewed, and page interactions. A tool that does not store cookies can still transmit data in a network request. Browser storage and server records can also have different retention periods.

The infrastructure your message passes through

Hosting and email services provide the technical infrastructure for the website and correspondence. Cloudflare is used for network security, content delivery, and Turnstile verification; it also performs cookieless performance measurement. Telegram helps deliver form notifications and live support messages to the team. The roles of Google Analytics 4 and Microsoft Clarity are described in the measurement process above. Any disclosure to authorities needs to take account of the legal scope of the request.

Requirements entered in the Project Wizard, and messages processed for AI responses in live support, may pass through infrastructure that generates suggestions or replies. This is a service process separate from your analytics choice. AI services may also process data in systems outside Turkey, so do not enter confidential information, unnecessary personal information, or sensitive personal data in these fields.

Providers such as Cloudflare, Google, Microsoft, and Telegram may use infrastructure outside Turkey. Loading font files through Google Fonts on legacy login/password pages also creates an external connection. If you move to WhatsApp, that service’s rules apply separately. This explanation does not claim that standard contractual clauses have been signed or that an adequacy decision applies. Cookie choices alone should not be treated as sufficient for ongoing international transfers.

Retention and access limits

The retention of contact records depends on the inquiry’s status, any subsequent business relationship, and applicable legal retention obligations. Support correspondence, newsletter records, and analytics systems do not share a single retention rule. This page does not state a verified internal retention schedule, a fixed retention period, or a promise of automatic deletion. A cookie’s inventory lifetime is not the date your message will be deleted from the server.

HTTPS and form validation help reduce data-transfer risks and automated misuse; they do not eliminate every risk. Access, backups, and deletion of relevant records also need to be managed. We do not claim that every system has a particular certification or that a breach is impossible.

Requesting information and changing preferences

You may request information about your records, correction, or deletion; ongoing obligations also matter when a deletion request is assessed. Statutory rights and the request framework under Turkey’s Personal Data Protection Law are explained in the Personal Data Protection Notice (KVKK) (in Turkish). Technical preference details are in the cookie policy. Use the contact page to specify which channel or record your question concerns.

When a portfolio or blog link takes you to another website, review its privacy notice too. This website is intended for adults and businesses; if you notice records concerning children, write to [email protected]. This privacy policy is subject to review as the tools used and published business-identity details change. Content revised: October 7, 2026.

Last updated: 7 October 2026

Get a quote

Let's Discuss Your Project

Let's clarify your needs

Message us on WhatsApp