ICANBUY ULUSLARARASI GAYRİMENKUL YAT. A.Ş., trading as iCanBuy in Turkey, is the data controller for icanbuyinturkey.com. Address: Marmara Mah., Ulusum Cad. No:4/38, Dükkân 7, Deniz İstanbul, Beylikdüzü, İstanbul, Türkiye. Contact: info@icanbuyinturkey.com.
Last revised 25 August 2026.
Company identifiers
- MERSIS number, trade registry number and tax number:
- to be completed.
- KEP (registered electronic mail) address:
- to be completed.
- VERBIS registration number:
- to be completed.
Current state: active on 2026-08-24
The site currently has no visitor accounts, on-site payment or checkout. The enquiry form collects name, email, phone country code and number, optional nationality, interest, budget band, message, project/page/brochure context, any Match brief carried in the URL, language, newsletter choice, UTM parameters or gclid present in the URL, and technical anti-spam fields. It sends them to the site endpoint and, when configured, Zoho CRM EU; on failure, the visitor's device opens an email draft.
Operational data are collected from browser requests and provider infrastructure. The enquiry API rate-limits with a process-lifetime salted hash of the visitor IP header, not a permanent visitor profile. Sanitised CSP reports may contain the violated directive, status code and document/source/blocked URLs without query strings. Hosting providers process standard request data such as IP, URL, time and browser information to serve and protect the site.
The only first-party localStorage key found is icb-theme, storing dark, light or system after a visitor changes appearance. It does not send itself to the server. No first-party cookies, analytics/ad pixels, account storage, shortlist/compare storage or payment storage are active.
Mapbox loads on map pages and may receive IP, user agent, request and interaction data directly from the browser. Consent-gated Zoho SalesIQ is not loaded on entry; if the visitor chooses to load chat, Zoho may use its own cookies/storage. WhatsApp opens outside the site and may process connection/device data under its own terms; only if the visitor sends the prepared message does the company receive its content and the profile/phone details visible in the chat. No current WhatsApp message includes a stored shortlist.
Purposes and KVKK bases are: requested enquiry and pre-contract steps, Article 5/2(c); CRM lead management and proportionate follow-up, Article 5/2(f) legitimate interest after balancing visitor rights; legal/accounting obligations and claims, Articles 5/2(ç) and 5/2(e); security, abuse prevention, necessary hosting, maps and CSP diagnostics, Article 5/2(f); optional marketing and non-essential chat storage, explicit consent where required plus commercial-electronic-message rules. Special-category data are not requested and should not be put in free text; if received incidentally, they must be restricted and deleted unless an Article 6 condition applies.
Recipients, only for the stated purposes, are authorised company staff/advisers, Zoho CRM/SalesIQ, hosting and email providers, Mapbox, WhatsApp/Meta when chosen by the visitor, professional advisers and legally authorised public bodies. Data are obtained directly from the visitor, the URL/browser and those service channels by automated or electronic means.
Foreign-provider use must satisfy KVKK Article 9 as well as one of the conditions in Article 5 or 6. Routine transfers must not rely on the Article 9/6 incidental-transfer exceptions. The owner/lawyer must document the actual destination and role of each provider and confirm an adequacy decision or appropriate safeguard; a KVKK standard contract, if used, must be signed in the prescribed form and notified to the Authority within five business days. This policy does not claim that this release gate has been completed.
Retention periods for enquiry/CRM, marketing-consent, CSP, contract and dispute records: to be completed.
Under KVKK Article 11, data subjects may ask about processing, purposes and recipients; request correction, deletion/destruction and third-party notice where applicable; object to an adverse result produced solely by automated analysis; and seek compensation for unlawful processing. Responses are given as soon as possible and no later than 30 days.
If GDPR Article 3 applies, EU/EEA data subjects also have applicable rights to access, rectification, erasure, restriction, portability, objection, consent withdrawal and supervisory-authority complaint. GDPR bases are requested pre-contract steps/contract, legitimate interests, legal obligation and consent; this addendum does not assert that mere site accessibility makes GDPR apply.
Dormant modules: activate, date and complete before the trigger; otherwise they describe no current processing
- S1: shortlist/compare, upon activation:
- trigger only when verified localStorage key(s), planned as icb.shortlist.v1 plus any compare key, ship. Replace this sentence with exact keys, fields and lifespan. The intended design stores selected property/project references, order and comparison settings only on the device; the company receives nothing unless the visitor reviews and sends a WhatsApp message containing the selections. Operation at the visitor's request and resulting enquiry follow-up are pre-contract steps under Article 5/2(c). Any sync, profiling, reuse or automatic transmission invalidates this module and requires a new assessment.
- C1: calculators, upon activation:
- total-cost and instalment-viewer inputs/results remain in browser memory, are not persisted and do not leave the device. On that design the company does not collect the inputs and no personal-data basis is invoked. Any server call, logging, storage, prefill from a profile or third-party SDK requires a revised module before launch.
- A1: accounts, upon activation:
- there are no accounts today. Before registration opens, insert exact identity/contact fields, credential handling, saved preferences/properties, security logs, vendors, recipients, retention and transfers. Pre-drafted bases: account creation/performance under Article 5/2(c), proportionate authentication/security under 5/2(f), and mandatory records/claims under 5/2(ç) and 5/2(e). Optional marketing or profiling requires separate choice and basis.
- N1: analytics, upon activation:
- none is active today. Before any tag/request runs, insert vendor, event and identifier inventory, purposes, destinations, retention and Article 9 route. Non-essential performance/behavior analytics must remain off until freely given, specific, informed opt-in consent, with equally accessible rejection and withdrawal. This module does not authorize advertising, cross-site tracking or profiling.