Privacy Policy

1. Scope

This policy covers viewing website pages, establishing a secure session, and any data generated when a visitor voluntarily uses the telephone, email or WhatsApp links on the contact page.

The contact and dealership form accepts identity, contact, company and enquiry details and submits them for email delivery to info@tirebot.com.tr. The application creates no permanent local submission record. The quotation form and file attachments remain disabled.

2. Data Controller and Contact Point

The Türkiye contact-centre details appear on the Contact page. External records have not yet established that this contact is the data controller or an authorised representative of the TIREBOT brand.

The controller’s full registered name, registered address and dedicated personal-data request channel will be added after documentary and legal approval. Until then, the Contact page may be used only as an initial enquiry point.

• Türkiye Contact Centre

3. Data That May Be Generated

A page request may generate an IP address, request time, requested URL, HTTP method, browser user agent, referrer and error information in hosting or security logs. The live hosting operator must confirm the exact log fields.

A random session identifier supports session and request integrity and contains no name, email address or telephone number. If a visitor starts a call, email or WhatsApp conversation, the information they choose to provide is also processed through that channel.

• Connection and security data, including IP address, time, request and error records
• Device and browser information available in HTTP headers
• The random, strictly necessary tirebot_session identifier
• Identity, contact and enquiry information voluntarily shared through an external contact channel

4. Purposes and Legal Assessment

Technical records may be used to deliver pages, protect the session and request integrity, restrict abuse, diagnose faults and maintain service security. Direct-contact data may be used to understand and answer an enquiry and, where requested, to prepare a commercial discussion.

The controller must document which condition under Article 5 of Turkish Law No. 6698 applies to each activity. This page does not treat a site visit as marketing consent and does not claim that one legal basis applies to every activity.

5. Service Providers and Transfers

Live hosting, network-security, email and backup contracts have not been finalised in this repository; no recipient or country is therefore invented. Providers, processing locations and transfer safeguards must be entered in the approved inventory before release.

If a visitor chooses WhatsApp or an external email application, data may enter that provider’s systems. These channels are optional and are not required to read the website. Any international-transfer assessment remains pending.

6. Retention, Deletion and Security

The tirebot_session cookie expires with the browser session. The application stores no local copy of contact-form fields; the session retains only non-personal validation state needed to show an error. Submitted email is handled in the recipient mailbox and deleted under the mailbox owner’s process. No unsupported fixed period is stated for mailbox or hosting records.

The code provides HTTPS deployment controls, Secure and HttpOnly session cookies, SameSite=Lax, a content security policy, CSRF protection and rate limiting. Mailbox access and deletion remain the responsibility of the mailbox owner.

7. Rights Under Turkish Data-Protection Law

Article 11 of Law No. 6698 gives data subjects rights to learn whether data is processed, request information, learn the purpose and whether data is used accordingly, and know recipients in Türkiye or abroad.

They may also request correction, deletion or destruction where the conditions are met, notification of those steps to recipients, object to an adverse result based solely on automated analysis, and seek compensation for unlawful processing.

8. Requests

A request should identify the applicant, provide an address suitable for notice, state the subject of the request and include only documents needed to verify identity and support the request. Special-category data or excessive identity documents should not be sent.

Until the controller’s formal channel is confirmed, the Contact page is the initial contact point. A valid request should be answered as soon as possible and no later than thirty days, subject to the tariff set by the Turkish authority where additional cost arises.

• Turkish authority guidance on requests ↗

9. Changes

If a form, analytics tool, advertising technology, embedded map, chat service or new provider is introduced, this policy and the cookie inventory must be updated before that feature is released. The version and update date appear at the top of the page.