Virtual Ajans
Virtual Ajans

Privacy Policy

This policy explains how the data collected through the offer/request form on virtualajans.com is processed.

01Data Controller

Emrah EMREZ, the individual operating under the Virtual Ajans brand, is the data controller for the data collected on this site.

Contact: email [email protected].

02What Data Is Collected and How

When you fill out the offer form, we collect your full name, at least one of your email and/or phone number, your need type, your budget information if provided, and your project description. This data is collected electronically through the form and entered directly by you. Every request is automatically assigned a record ID and timestamp by the system. To prevent misuse, your IP address is not stored in raw form; only its hashed form is kept briefly for rate-limiting purposes. This hashing makes the data pseudonymous, not irreversibly anonymized; infrastructure providers that carry the traffic (e.g. Cloudflare) may see your raw IP address within their own systems.

03Purpose of Data Use

Data is used only to respond to your request, to carry out the pre-contractual proposal process, and to secure the form (preventing spam/bot abuse). It is not used for marketing or newsletter purposes; there is no mandatory consent checkbox on the form.

04Cookies and Tracking

No advertising or analytics tracking cookie, nor any third-party tracking script, is used on the site. The preference window opened via Cookie Settings in the footer is not a tracking tool: your choice is stored only in your own browser, in localStorage under the key va-cookie-preferences, together with a version number and record date, and automatically expires after at most 6 months, reverting to default values. This record is not sent to the server.

The required/security category (form submission and Turnstile protection) is always active and cannot be turned off from this window. The analytics and marketing categories are off by default, and even if checked in this window, they do not run any script today; they only pre-record a preference to be applied if these tools are added in the future. This record does not count as valid, informed consent for a future analytics/marketing tool — if such a tool is added, you'll be informed and asked again. You can change or reject your preference at any time; this choice does not affect form security (Turnstile) in any way.

05Data Flow and Service Providers

When form submission is active, the form data is saved to an SQLite database on the primary server hosted in Istanbul, Turkey; only Emrah EMREZ can access this database. Once the record is completed, a notification covering your full name, contact information and request content is sent via Telegram. If the primary server cannot be reached, it attempts to deliver a notification to the Telegram channel through a backup Cloudflare Pages Function; this backup path does not write any record to the SQLite database, so a database record is not guaranteed for every request.

The following providers are used to deliver the service: Cloudflare (hosting the site, routing traffic, and securing it via Tunnel — and also via Turnstile when enabled — technical data such as your IP address and request information, as well as the backup notification data sent when the primary server is unreachable, passes through Cloudflare's infrastructure in this context), Telegram (delivering request notifications), and Yandex (used solely for conducting email correspondence). Communication via WhatsApp is an entirely optional channel initiated by the user's own choice, independent of the form data.

The primary server is located in Istanbul, Turkey, and is accessed only by Emrah EMREZ. Because the providers above may process your data abroad as well, it is not claimed that all data remains solely in Turkey.

06Retention Periods

  • Requests that do not turn into a contract: 12 months from the last meaningful contact
  • System logs: 30 days (may be exceptionally extended for a justified reason such as investigating a security incident)
  • Backups: a 30-day cycle is targeted
  • Records that turn into a contract: for as long as required by applicable law

These periods reflect the approved policy; there is no automated deletion/destruction system that operates strictly by these periods.

07Your Rights

For your rights under KVKK Article 11 (access, correction, deletion, notifying third parties the data was transferred to, objecting to automated processing, seeking compensation for damages) and the application procedure, see the Disclosure Notice page.

09Updates

This policy may be updated in line with ongoing legal review and system changes. The current version is always published on this page.

For your rights under KVKK and the application procedure, see the Disclosure Notice page.