This English version is provided for information purposes only. In the event of any discrepancy between the Turkish and English versions, the Turkish version shall prevail.
§ 1Data Controller
Under Law No. 6698 on the Protection of Personal Data ("KVKK"), the data controller is KRONO YAZILIM VE BİLİŞİM TİCARET LİMİTED ŞİRKETİ ("Krono", the "Company" or the "Data Controller"), whose details are set out below.
Dual role: Krono acts as the data controller in respect of its own corporate activities and the services it provides directly. However, in transactions that a travel agency carries out through the Krono platform regarding its own tourists/passengers/suppliers, the agency is the data controller and Krono acts as the data processor, acting on the agency's instructions (see the DPA).
§ 2Scope and Categories of Data Subjects
This notice addresses the following categories of data subjects. Data relating to each category is processed only to the extent of that person's relationship with Krono; it is not necessary that every category below be processed in every case.
- Travel agency owners, managers, employees and users,
- Professional tourist guides,
- Freelance or agency-affiliated field staff,
- Tourists, passengers and tour participants,
- Prospective customers and customer representatives,
- Authorised persons and employees of hotels, restaurants, vehicle, transfer and other tourism suppliers,
- Visitors to the Krono website and mobile application,
- Persons contacting our support and communication channels,
- Business partners, integration providers and their employees,
- Job/internship candidates and consultants,
- Company officers, shareholders and employees,
- Other natural persons whose communication/operational data is held in Krono systems.
§ 3Categories of Personal Data Processed
| Category | Example data |
|---|---|
| Identity | First name, surname, username, date of birth, age, gender, nationality/citizenship; authorisation/representation details for transactions carried out on behalf of a company |
| Contact | Phone, email, address, country/city of residence, WhatsApp number, Instagram username, preferred channel |
| Travel / passenger | Passport number and issue/expiry dates (MRZ), whether the passport contains a chip, second nationality, visa status, boarding stop, room/tent, seat, for passengers under 18 whether parental consent has been given, reservation/tour details, destination/route |
| Customer transaction/reservation | Tour request, reservation number, date, flight/transfer, hotel/room, vehicle/driver, group details, amendment/cancellation, quotation, support records, operational notes |
| Guide | Licence/work card, professional chamber membership, languages, expertise, region, availability, assignment, tour history, earnings/invoicing, bank payment details |
| Supplier / business partner | Authorised person/employee identity-contact details, role/authority, contract, pricing, invoicing, payment, performance information |
| Financial | IBAN, invoice, collection/payment, currency, earnings, receivables/payables, reconciliation, accounting documents (card details are not stored by Krono) |
| Transaction security | IP, device/session information, login/logout time, activity/access logs, verification, error and security-event records, API calls |
| Location / field | Mobile location with the user's explicit permission, guide/field task location, tour start/end, meeting points, vehicle location |
| Visual / audio | Profile and field photographs, uploaded images, user voice recordings, (where notified) support call recordings |
| Messaging content | WhatsApp/Instagram messages, email, in-app messaging, chatbot conversations, attachments and metadata |
| Marketing | Commercial-communication preferences, campaign interactions, consent records, segment/interest information |
| Legal/compliance | Contracts, consent/explicit-consent records, privacy-notice acknowledgement records, applications and responses, official correspondence |
Identity/passport documents in full are processed only where genuinely necessary for the tour, visa, accommodation, transport, insurance or a statutory obligation. Email and address are not collected for passengers. Document images are uploaded as a photograph or screenshot; PDF files are not accepted. Identity/passport images are not shown to users other than the agency (guides, administration panel); OCR is used only for passport and identity document images. Infrastructure providers are listed in § 9.
§ 3.1 Special Category Personal Data (Art. 6 KVKK): Krono does not collect or process special categories of personal data (such as health data). Passenger document images (identity/passport) are stored in Krono's own database, can be viewed only by the users of the agency account that uploaded the document, and are not made available to guides or the administration panel. They are deleted from the live database 30 days after the tour ends. For health data and vaccination card or health report images collected earlier, the rights to deletion and to withdraw explicit consent are preserved, and the text version and date on which the earlier consent was given are kept in a separate record.
§ 4Purposes of Processing
- Membership/account: account creation, authentication (including multi-factor), roles/permissions, session and subscription management, security.
- Tour operations: itinerary/route planning, guide-vehicle-hotel-restaurant assignment, reservation/amendment/cancellation, flight-transfer-accommodation coordination, notifications.
- Field information sharing: museum/site/venue information, closure/congestion/weather alerts, task communication among field teams.
- WhatsApp/Instagram management: transferring messages to the panel, matching, classification, routing, AI-drafted responses, authorised automatic replies, history retention.
- AI-assisted service: classification, drafting quotations/notes, risk/conflict detection, analysis, translation/summarisation (see § 6).
- Finance/accounting: invoicing, collection, earnings, profitability/cash-flow analysis, reconciliation, tax obligations.
- Guide portal and mobile application: profile, availability, task offers, notifications, location-based features.
- Support, security and legal obligations: resolving requests/complaints, preventing misuse, log-keeping, public-authority requests, protecting rights in disputes, data-breach management.
- Product development/analytics: improvement using data that is, to the extent possible, anonymous/pseudonymous/aggregated.
- Marketing: based solely on preference/consent; not a mandatory part of the service, and consent can always be withdrawn.
§ 5Legal Grounds
Your data is processed on the basis of one or more of the grounds set out in Art. 5 and 6 KVKK:
- Explicitly provided for by law Art. 5(2)(a) — tax, commercial, e-commerce, tourism/agency, accounting records.
- Necessary for the establishment or performance of a contract Art. 5(2)(c) — account, tour operations, message management, reservations, assignments, subscription, support.
- Compliance with a legal obligation Art. 5(2)(ç) — invoicing/accounting, public-authority requests, application records.
- Establishment, exercise or protection of a right Art. 5(2)(e) — debt collection, disputes, evidence.
- Legitimate interest Art. 5(2)(f) — security, fraud prevention, quality measurement, limited logging; subject to a balancing test.
- Explicit consent Art. 5(1), 6 — marketing, non-essential cookies, certain special-category/location processing. Explicit consent is given freely, is never made a precondition for the core service, and is obtained separately from this notice.
§ 6Special Provisions on Artificial Intelligence Systems
6.1 Role: The artificial intelligence systems used by Krono are decision-support tools that assist users/authorised staff (draft replies, classification, tour/route suggestions, risk indicators, analysis). Outputs carry no guarantee of accuracy; critical information such as museum opening hours, prices, availability, visas, border rules or health and safety must be separately verified from an authoritative source.
6.2 Human oversight: Decisions that produce legal or similarly significant effects on a person (removing a guide from the system, deducting earnings, permanently closing an account, denying service, or imposing a sanction) are never made solely on the basis of automated output; an authorised natural person reviews them.
6.3 Data minimisation: Only the data necessary for the purpose is sent to the artificial intelligence system; identity identifiers (national ID number, phone number) are masked, content is pseudonymised, special category data is excluded from the model input, and unnecessary attachments are not processed.
6.4 Model training: Personal data belonging to agencies, tourists, guides or suppliers is not used to train general-purpose models unless there is a separate legal basis and explicit information. Where data is needed for quality/performance work, it is first anonymised or pseudonymised, access is restricted, and the source, purpose and duration are recorded.
6.5 Providers: Krono uses third-party providers for its artificial intelligence services: Anthropic PBC for chat responses and for TurAI inscription/epitaph photos (sent raw, unmasked); Google LLC (Gemini API) for document/image text recognition (OCR). We prefer a corporate/closed API under which the provider does not train its own model on our data; the data transferred is limited and the cross-border rules in § 10 apply.
6.6 User control: Users are given, to the extent possible, clear information about whether a message was prepared/processed by artificial intelligence, whether an automatic reply is in use, how it can be switched off, and how a human review can be requested.
§ 7WhatsApp, Instagram and Third-Party Platforms
Once these platforms are connected, your account and messages are processed only within the scope of the authorisation you have granted; your account identifier, username, profile, message content and timestamp, sender/recipient information, attachments and delivery/read status may be transferred to Krono. The relevant platforms may act as independent data controllers for their own activities. Krono does not collect passwords, uses only the API permissions granted to it, and stops any further access once authorisation is withdrawn. It is the user's responsibility to ensure that the necessary privacy notices and legal requirements are satisfied before connecting messages belonging to third parties.
§ 8Methods of Collection
Personal data may be collected wholly or partly by automated means, or by non-automated means forming part of a data-recording system, through the website, mobile application, management panel, WhatsApp Business/Instagram integrations, email/phone, in-app messaging, registration/application forms, tour/reservation files, guide/supplier portals, payment/accounting systems, map/ticketing integrations, technical logs and cookies, and through authorised public authorities and business partners.
§ 9Parties to Whom Data May Be Transferred
| Recipient | Purpose | Location |
|---|---|---|
| Travel agencies and their authorised users | Operation of the tour | Turkey |
| Professional tourist guides | Customer/tour information necessary for the assignment (passport and financial data, passenger document images and sensitive data are not transferred); before accepting an offer, the guide also sees only the average age and the number of registered persons of the tour guests (names, dates of birth and personal details are not shown) | Turkey |
| Hotels, restaurants, vehicle and other suppliers | Minimum information necessary for reservation/service | Turkey |
| iyzico (iyzi Ödeme ve Elektronik Para Hizmetleri A.Ş.) | Payment collection, subscription management, card storage and transfer of the authorised person's identity number (card data held exclusively by iyzico) | Turkey |
| E-document service provider (TÜRMOB-TESMER) | E-invoice issuance | Turkey |
| Anthropic, PBC | Artificial intelligence — chat responses (Claude API); national ID number/phone masked, name and free text not masked; TurAI inscription/epitaph photos not masked | USA |
| Google LLC | Artificial intelligence — document/image text recognition, OCR (Gemini API) | USA |
| Groq, Inc. | Artificial intelligence — voice message transcription (Whisper API) | USA |
| Hosting infrastructure (our own servers) | Database, authentication, application | Germany (EU) |
| Cloudflare, Inc. | CDN/WAF/bot protection and file storage (R2) | Storage in the EU, traffic global |
| Resend | Transactional email | EU / USA |
| Open-Meteo (Open-Meteo.com) | Weather information: the name or coordinates of the selected city are sent; the browser's IP address and request information reach the provider's servers | Abroad |
| Mapbox, Inc. | Map and route service: map tiles and the coordinates of route points are sent; the browser's IP address and request information reach Mapbox's servers | USA |
| Google Fonts (Google LLC) | Font delivery on legal pages, login and the marketing page; the browser's IP address and request information reach Google's servers | USA |
| TUREB | Guide licence verification: the licence number, national ID number and language setting are sent (see § 9.1) | Turkey |
| Legal/financial advisers and audit consultants | Bound by confidentiality, for legal/financial processes | Turkey |
| Parties to a merger/investment/transfer | Limited disclosure subject to confidentiality and security safeguards | As applicable |
| Authorised public authorities and institutions | Legally valid requests | Turkey |
9.1 Guide Licence Verification (TUREB)
The professional licence of tourist guides is queried through the document verification service of the Turkish Tourist Guides Union (TUREB). The purpose is to confirm that a guide account is based on a valid licence and to take the professional details on the profile from the official source. Legal grounds: establishment/performance of the contract Art. 5/2/c and legitimate interest Art. 5/2/f.
The three moments at which verification is performed:
- Registration: once, immediately after you confirm your email address when registering as a guide, using the details you provided at registration.
- Profile refresh: when, as a guide, you press the "Update from TUREB" button on your profile.
- Administrator scan: when a Krono administrator checks a guide record, or when the administration panel scans records that have not yet been queried or for which no result could be obtained (including the bulk check the system starts for pending records). At this moment Krono starts the query, not you; no action is expected from you.
Information sent to TUREB: your licence number, your national ID number and the response language (Turkish). No other information is sent; this information is not sent to artificial intelligence systems.
Information returned by TUREB and stored:
| Information | Why it is stored |
|---|---|
| Full name | Compared with the first name and surname you gave at registration; if they match, the TUREB spelling is used, and if they do not match, the difference is recorded and the account is not approved automatically. |
| Licence number | To show that the queried licence matches your record. |
| Date of starting the profession | The experience information on the guide profile. |
| Licence type | To determine the working region shown on the profile. |
| Activity status | Whether the licence is active; an inactive licence is not approved automatically. |
| Foreign languages | The language information on the profile. |
| Affiliated chamber | The professional chamber information on the profile. |
| Photo address | The web address of the photo on the TUREB record; shown on the licence card during administrator review. The photo itself is not copied to Krono. |
| Professional training record (pandemic training) | The "has completed the pandemic training" information on the TUREB record (yes, no or not stated). |
| Information mismatch record | The list of differences between your registration details and the information returned by TUREB (field names only, for example full name, affiliated chamber, activity status). |
Your national ID number is not written a second time into the record returned by TUREB. The verification result alone does not reject your account: if no match is found, if the name does not match, if the licence is inactive or if the service cannot be reached, your record is reviewed by an administrator (see § 6.2). This information is kept for as long as your guide account exists and is erased when your account is deleted (anonymised) (see § 12).
§ 10Cross-Border Transfer and Artificial Intelligence
In order to provide the service, your message content (including your first and last name and any free text you write) is processed by artificial intelligence providers established abroad: Anthropic, PBC (USA) for chat responses; Google LLC (Gemini API, USA) for document/image text recognition (OCR); Groq, Inc. (Whisper API, USA) for voice message transcription. Before transmission, your national ID number and phone number are masked; your first and last name and free text are not within the scope of this masking. If you send an identity/passport document image, it is processed in its raw form for the purpose of reading the document details; the information read is not written to your record until it has been confirmed by staff. The provider's corporate API does not train its model on this data. If you send a voice message, your audio recording is processed in its raw form for transcription purposes; this content is not masked. This processing relies on the legal ground of performance of the service/contract (Art. 5(2)(c) KVKK) and forms part of the service covered by the Terms of Service.
This cross-border transfer is assessed under Art. 9 of Law No. 6698, within the framework of the Regulation on the Procedures and Principles Regarding the Transfer of Personal Data Abroad (Official Gazette 10 July 2024, No. 32598). The mere presence of a policy on the website does not, by itself, satisfy the conditions for a cross-border transfer. Within the hosting/email infrastructure (Cloudflare — storage in the EU; Resend), data is processed in appropriate locations. Google Fonts, used for font delivery, also sends your browser's IP address and request information to Google's servers (USA). Open-Meteo, used for weather information, and Mapbox, Inc. (USA), used for the map and route service, likewise receive the city name or coordinates together with your browser's IP address and request information on their servers abroad; no first or last name, telephone number, e-mail address or national ID number is sent to these services.
§ 11Visibility Between Parties and Data Accessed by Krono
To provide the service, certain information becomes visible between parties (legal ground: performance of the contract/legitimate interest; the guide's explicit consent for the phone number):
| Who sees it | What they see |
|---|---|
| Business → Guide | Contact details (phone number, with explicit consent) |
| Guide → Business | Business profile |
| Agency → Guide | Professional profile (experience, age, city, languages) and contact details (with explicit consent) |
In the interest of transparency: to operate the platform, Krono processes and displays members' transaction, usage and earnings/statistical data; it does not sell or rent this data to third parties, and uses it only for the service, invoicing, security and improvement.
11.1 Advertising Measurement and Demand Counter
Impressions and clicks are counted in order to measure and report that the promotion (advertising) packages purchased by businesses were displayed. Counting is done in aggregate per package and per hour; no personal identifier (user ID, name, phone number, email address, IP address) is written to the counters. Legal grounds: performance of the contract Art. 5/2/c and legitimate interest Art. 5/2/f; the delivery record is also kept as evidence.
- De-duplication: so that the same person is not counted repeatedly for the same advertisement within a short time, a short-lived salted (irreversible) digest derived from the user ID is held in memory only: a few minutes for impressions and 24 hours for story views. This digest is not written to the database and is deleted automatically when its time runs out.
- Rate limiting: a rate-limit record is kept to restrict excessive requests to the advertising endpoints; if memory is unavailable, this record falls to the database with the IP address (or a digest derived from the IP address) and is kept for at most 48 hours.
- Demand counter: the number of advertising requests that arrive for a business category in a province is kept only as an anonymous total per province, category and day (the number of requests targeting a district is counted separately). No user, device, session or IP information is written to this counter; it is used to measure the level of demand.
- Retention: the delivery record (hourly aggregate impression and click counts) is kept for the commercial ledger retention period (10 years); the demand counter is kept for 180 days.
§ 12Retention Periods
- Account/membership: for the duration of the contract, plus the applicable limitation period from its termination (Art. 82 of the Turkish Commercial Code: 10 years).
- Tour/reservation: from completion of the tour, for the applicable legal/tax/commercial obligation period.
- Invoicing/accounting: the period set out in tax legislation.
- WhatsApp/Instagram records: the active relationship plus 3 years (for dispute/operational needs).
- Passenger document images (identity/passport): deleted from the live database 30 days after the tour ends; if there is no tour end date, the tour start date applies, and failing that the upload date.
- Previously collected meningitis vaccination status, type and date, health report status and health note: deleted from the live database 30 days after the tour ends; the rights to deletion and to withdraw explicit consent are preserved for this data (details: the Health Data Explicit Consent Text, no longer in use).
- Explicit consent/communication permission records (including the record showing which text version the earlier health explicit consent was given on and when): the evidentiary/obligation period following withdrawal.
- Security/transaction logs: a period appropriate to Law No. 5651 and security needs.
- Location: a short period necessary for operations; not retained long-term absent a legal requirement.
- TUREB licence verification information (§ 9.1): for as long as the guide account exists; erased when the account is deleted (anonymised).
- Advertising delivery record (§ 11.1): for the commercial ledger retention period (10 years); advertising demand counter: 180 days; de-duplication digest (in memory): a few minutes, 24 hours for stories; rate-limit record: at most 48 hours.
Once the period ends, data is deleted, destroyed or anonymised. Anonymised data may continue to be used for statistics and product development.
§ 13Technical and Administrative Measures
Technical: encryption in transit using TLS 1.3, AES-256 for storage, database/backup encryption; role-based access and the principle of least privilege; multi-factor authentication; bcrypt password hashing; transaction/access logging (hash plus timestamp); anomaly/suspicious-access detection; firewall and network segmentation; vulnerability scanning, code review and security testing; API authentication and rate limiting; PII masking/pseudonymisation; secure backup and disaster recovery; separation of production and test environments; secrets held in a secure vault.
Administrative: a personal-data processing inventory; defined data controller/processor roles; an access-authorisation matrix; employee/contractor confidentiality undertakings; KVKK/information-security training; supplier risk assessment and data-processing agreements; a retention-and-destruction policy; a data-breach response plan (see § 16); a data-subject application procedure; separate access/security rules for special category data; immediate revocation of access for departing staff.
§ 14Mobile Application Permissions
The Krono mobile application may request the following permissions, only before the relevant feature is used and through the operating system:
- Location: for route, task, meeting-point and field features,
- Camera: to upload a profile or field photograph,
- Photo library: to select documents/images from the device,
- Microphone: for voice messages or support features,
- Notifications: for tour/task/operational notifications,
- File access: to upload documents you select.
You may withdraw these permissions from your device settings; doing so only affects the operation of the related feature. Continuous background location tracking is carried out only where necessary for the relevant function, and only where it has been separately explained and permission has been granted.
§ 15Personal Data Relating to Children
Where children are present in tour groups, their personal data is processed only to the extent necessary for the operation of the reservation/tour (identity/passport, age, guardian contact details, and information necessary for safety are separately protected). Children's data is not used for marketing, behavioural advertising or the training of general-purpose artificial intelligence models. It is the responsibility of the relevant data-controller agency to inform the guardian and obtain any necessary permissions.
§ 16Data Breach Management
When a data breach is detected, Krono contains the breach, identifies the affected data/data subjects, investigates the cause and consequences, implements technical remedies and — pursuant to the Personal Data Protection Board's decisions of 24 January 2019 (2019/10) and 18 September 2019 (2019/271) — notifies the Board no later than 72 hours after becoming aware of the breach, and notifies the affected data subjects as soon as reasonably possible. Where the data was processed in the capacity of data processor, the controlling agency is informed without delay. Krono maintains a Data Breach Response Plan.
§ 17Cookies
Krono uses only necessary and functional cookies; it does not use marketing/analytics tracking cookies. For details and preference management, see our Cookie Policy.
§ 18Data Accuracy and User Obligations
Users are required to provide accurate, up-to-date information, not to share their account, to transfer other people's data only in accordance with the law, not to upload unnecessary special category data, to keep authorisations limited to the relevant role, and to revoke access for departing staff. Krono provides account and application channels for the correction of inaccurate information.
§ 19Your Rights
Under Art. 11 KVKK, you have the right to learn whether your data is being processed, to request information/access, to request correction, to request deletion/destruction, to learn the third parties to whom it has been transferred, to object, and to seek redress where you have suffered damage. For details and how to apply, see our Data Subject Rights page. Applications: [email protected].
§ 20Amendments
This notice may be updated in line with changes in legislation or the service; the current version takes effect once published on this page, and material changes are additionally announced.
Note: In respect of agency users, the data controller for their own passengers/customers is the agency; Krono acts as the data processor. This framework is supplemented by the DPA and the Passenger Privacy Notice.