Privacy Policy
Kunduz Suite is a multi-tenant SaaS platform for logistics operations and tank-cleaning management. This policy describes what the software actually collects, why, who receives it and how it is protected. It was written from the source code, not from a template — including the parts that are inconvenient.
Effective: August 4, 2026 Last updated: October 12, 2026 Version: 1.3 Language: English (the Turkish version prevails in case of conflict)
01 Who we are
Kunduz Suite is developed and operated by Ayberk Ergezen, acting as an individual (natural person) data controller. No operating company has been incorporated yet, so there is no registered trade name, commercial registry or MERSIS entry, and no registered electronic mail (KEP) address to publish.
Contact runs through a single e-mail address: destek@kunduzsuite.com. General enquiries, privacy questions and requests to exercise your rights all go there. No postal address and no telephone line are published for the service; e-mail is the channel we operate and the one we answer.
What changes once a company is incorporated
When an operating company is incorporated, its trade name, registered address, tax details and — where registration becomes mandatory — its Turkish data controllers' registry (VERBIS) number will be added to this section, and the version number and "last updated" date will change. No EU or UK representative has been appointed at this time. The contact address will not change.
02 Scope and our two different roles
This policy covers Kunduz Suite, a multi-tenant software for logistics and tank-cleaning operations: its mobile application (iOS and Android), the web panel, the backend service, and the public marketing website. It is published to fulfil the duty to inform under the Turkish Personal Data Protection Law No. 6698 (KVKK).
Kunduz Suite is sold to companies. That means we act in two distinct roles, and your rights differ depending on which one applies:
- As a processor — for almost all operational data inside a customer's workspace: employee records, drivers, trips, work orders, photos, messages, customer and invoice records. The subscribing company decides what is entered, why, and by whom. It is the controller; we process on its documented instructions.
- As a controller — for data that belongs to the service itself: the subscription account, technical records of how the product is used, and support correspondence.
If you are an employee, driver or business contact of a company that uses Kunduz Suite, you can raise a data request with that company or with us. Requests sent to us are answered by us; where a request would also affect the company's own business records, we assess it together with the company's administrator. See section 11.
Under Turkish law (KVKK) the equivalent terms are veri sorumlusu (controller) and veri işleyen (processor). The specific allocation of roles will be set out in the service and data-processing agreement to be signed with each subscribing company.
03 Data we process
The table below lists every category of personal data the software processes, depending on your role. It was compiled from the database schema, the migrations and the API routes. Not every user comes across all of this data; for example, a driver cannot see employee records.
| Category | What it contains | Who it concerns |
|---|---|---|
| Account and identity | Full name, phone number, e-mail address, role, password (stored hashed), PIN (stored hashed), last-seen timestamp, linked customer account | All users |
| Employee records | Name, job role, phone, national identity number, start and end of employment, professional certificate names and their expiry dates, leave records (type, dates, note) | Tank-cleaning site staff |
| Driver documents | Whether a European passport / Schengen visa is held and its expiry date | Drivers on international routes |
| Vehicle and trip data | Plate numbers, the identity number field held on the vehicle (tractor-unit) record, employment start date, route (loading and delivery locations, free text), a manually entered location note, trip status history | Drivers and vehicle owners |
| Vehicle location | Latitude/longitude, speed, heading, ignition state, street address, province, country, time, total and daily kilometres, and the driver name reported by the tracking service — received live from the tracking provider, not stored in our database (see section 06) | Drivers, vehicles |
| Photographs and files | Work-order photos (before/after, interior/exterior), task completion photos, expense receipts, warehouse stock and operation photos, vehicle expense documents, message attachments | Whoever appears in or uploads them |
| Messages | Message text, attachment name/type/size, sender and recipient, read status, timestamp. Not end-to-end encrypted; stored as plain text in the database | All users except the warehouse role |
| Notification tokens | Push notification token and platform ("ios" / "android") | Mobile app users |
| Business contacts | Company title, tax office and tax number, phone, e-mail, addresses, payment terms, notes; named contact persons (name, position, phone, e-mail); bank account number (IBAN) on customer records | Contact persons of customer companies, sole traders |
| Names appearing in operations | Sender and recipient contact names on job records, driver and haulier names recorded at warehouse entry/exit, driver and consumer names on fuel movements | Your own staff and employees of other companies |
| Financial records | Invoices, amounts, currency, collection status, bank account names and balances, vehicle expenses — including traffic fines and accident records linked to a specific driver, with penalty type, policy number and agency | Customers, suppliers, drivers |
| Audit log | Timestamp, user id and name, action (HTTP method and path), and the first 500 characters of the request body. Credentials are masked; other personal data in the request body is not | Users who change data |
| Session data | Authentication token (JWT), session version. No advertising or marketing profiling, no device fingerprinting | All users |
| IP address | Every request to the application and API server is written to a server access log for security purposes: your IP address, the time, the requested address and your browser/app identifier. The log is deleted automatically after 30 days; session tokens, passwords and cookies are never written to it. In addition, for requests made before you are authenticated (the login screen, health checks, an invalid token), your IP address is used as the rate-limiting key; once you are signed in the limit is keyed to your account instead. Country and network information is derived from the address for security purposes only (section 12); the address is never used for advertising or marketing, and no device fingerprint is derived from it | All users, including before sign-in |
| Security event log | Sign-in attempts (successful and failed sign-ins, including drivers' PIN sign-ins; attempts on a locked account; system administrator sign-ins; and incorrect staff PINs entered on a shared site account), security rule triggers, permission changes (an account being created with, or raised to, the admin, manager or patron role; a custom-role change; and a user's password being reset to a temporary one by an administrator), and the security actions taken by the system administrator (locking or unlocking an account, ending sessions, lifting an IP block, marking an alert as a false alarm). Depending on the type of event, an entry holds: the time, the company, the user's id and name, the IP address, the browser/app identifier, the country, network number (ASN) and network name derived from the IP address, the measures taken or that could have been taken, and details of the event — for example the number of attempts, the IP addresses involved, the countries the account signed in from in the last 90 days, the old and new role in a permission change and, for bulk data extraction, the parts of the application most data was retrieved from and the record counts (not the content of the records). The e-mail address or phone number typed in a failed sign-in is not stored in readable form; only an irreversible, keyed hash of it (HMAC-SHA256) is kept. Entries are deleted automatically by a weekly clean-up once they are 1 year old. Who can see them and how they are used: section 12 | Anyone who attempts to sign in (including people without an account and staff entering a PIN on a shared site account), all users and Kunduz Suite system administrators |
| Read summaries | Counts only, per user and per minute: the number of requests, the number of records returned, the volume of data (bytes) and the number of exports (Excel/CSV). No content is recorded — not which customer, job or record was viewed. Summaries are deleted automatically after 90 days | All signed-in users |
Special categories
The application has no field intended for health, biometric, religious, trade-union or similar special-category (sensitive) data. The one risk is the type field of a leave record: if a subscribing company enters a medical report or sick leave into it, that is processing of special-category (health) data, which requires separate explicit consent under Article 6 KVKK (and a condition under Article 9 GDPR). We recommend that this field is not used for health information.
What we do not collect
- No analytics, crash-reporting, attribution or advertising SDKs of any kind. We verified this across the entire codebase.
- No device fingerprinting. The device information stored is the push token and the platform name, plus the browser/app identifier written to the server access log and the security event log.
- No smartphone location (see section 06).
- No microphone access and no audio recording of any kind.
- We do not sell personal data, and we do not use it for advertising or for training machine-learning models.
04 Purposes and lawful bases
Your personal data is processed for the purposes below, on the grounds listed in Articles 5 and 6 of KVKK. Where GDPR applies, the corresponding basis under Article 6 GDPR is shown alongside. The subscribing company is responsible for identifying the basis for data it enters about its own staff and customers.
| Purpose | Data used | Lawful basis (KVKK / GDPR) |
|---|---|---|
| Creating accounts, signing in, authenticating users and role-based authorisation | Account and identity data, session data | Establishing and performing a contract — KVKK Art. 5(2)(c), GDPR Art. 6(1)(b); under GDPR also the legitimate interests of the subscribing employer (Art. 6(1)(f)) |
| Running and tracking trip, work-order, tank-cleaning, warehouse and fuel operations | Trip, vehicle, employee and customer data, photographs | Performance of a contract — KVKK Art. 5(2)(c), GDPR Art. 6(1)(b); legitimate interests of the controller — KVKK Art. 5(2)(f), GDPR Art. 6(1)(f) |
| Employment administration: employee records, validity of professional certificates, leave | Employee records | Performance of the employment contract — KVKK Art. 5(2)(c), GDPR Art. 6(1)(b); legal obligation — KVKK Art. 5(2)(ç), GDPR Art. 6(1)(c) |
| Processing national identity numbers | Employee records, vehicle records | Legal obligation — KVKK Art. 5(2)(ç), GDPR Art. 6(1)(c): personnel-file and social-security obligations (keeping a personnel file under Art. 75 of Labour Law No. 4857; social-security notifications under Law No. 5510) |
| Invoicing, collections and statutory bookkeeping | Financial records, business contact data | Legal obligation — KVKK Art. 5(2)(ç), GDPR Art. 6(1)(c) (Tax Procedure Law, Turkish Commercial Code) |
| Monitoring vehicle position, verifying trips and showing the customer the live position of its shipment in transit | Vehicle location from the tracking device | Legitimate interests in fleet management and delivery visibility — KVKK Art. 5(2)(f), GDPR Art. 6(1)(f); performance of a contract — KVKK Art. 5(2)(c), GDPR Art. 6(1)(b) |
| In-app messaging and delivering work notifications | Message content and attachments; push token, notification title and body | Performance of a contract — KVKK Art. 5(2)(c), GDPR Art. 6(1)(b). Notifications reach your device only if you allow them in its settings |
| System security, abuse prevention and traceability of changes (audit log) | Audit log, server access log, session data | Legitimate interests — KVKK Art. 5(2)(f), GDPR Art. 6(1)(f); data-security obligation — KVKK Art. 12, GDPR Art. 32 |
| Account security: detecting and preventing unauthorised access attempts, large-scale password attacks (such as credential stuffing) and unusual bulk data extraction (section 12) | Security event log, read summaries, country and network derived from the IP address | Legal obligation (Art. 6(1)(c) read with Art. 32 GDPR; KVKK Art. 5(2)(ç) read with Art. 12); legitimate interests in protecting accounts and the service (Art. 6(1)(f); KVKK Art. 5(2)(f)) |
| Responding to requests from competent public authorities | Data within the scope of the request | Legal obligation — KVKK Art. 5(2)(ç), GDPR Art. 6(1)(c) |
When is explicit consent needed? None of the purposes above relies on explicit consent, so you are not asked for separate consent in order to use the application. Explicit consent comes into play only (a) where special-category data is processed, for example if health information is entered in a leave record, and (b) for a transfer abroad where the other safeguards in KVKK Article 9 cannot be provided (section 09). You can withdraw explicit consent you have given at any time, without affecting the lawfulness of earlier processing.
Where we rely on legitimate interests, we have considered the impact on the individuals concerned; you may object at any time (section 11).
Your personal data is not processed for advertising or marketing profiling, behavioural targeting or sale. The only automated evaluation that compares how an account is used with that account's own history is the security comparison described in section 12. The application contains no advertising network, analytics or crash-reporting tool, and your personal data is never sold or passed to third parties for marketing.
05 How we collect it
- Entered by your employer or its administrators — your account, your role and your employee record are created by your company's administrator, and your identity number, certificates and leave records are entered the same way. You may not have entered any of it yourself.
- Entered by you in the app — the forms you fill in on the web panel and in the mobile app: work-order, trip, warehouse and expense records, task completions, notes, and the messages you write.
- Through your device's camera and photo library — only when you start adding a photo, with permission requested at that moment. The app does not ask for bulk access to your photo library; only the file you choose is taken.
- Generated automatically by the system, to run and secure the service — session tokens, push tokens, timestamps, status history, change records (audit log), server access log entries, security event records, read summaries, last-seen indicator.
- From the tracking device in the vehicle, through the vehicle-tracking provider — vehicle location and the driver name reported by the provider (section 06).
- From your company's own systems — if your company asks for it, an accounting-software bridge is set up (section 08), or the company uploads an invoice list exported from its own accounting program.
- Marketing website — the public website makes no external requests, sets no cookies, contains no analytics and has no forms. It stores only a language preference in your browser. Contact is by e-mail only.
06 Location data — read this carefully
The Kunduz Suite mobile app does not read your phone's location. No location permission is requested — neither the iOS nor the Android version declares one — there is no background location tracking, and your device's location is never sent to our servers. The app contains no location library and makes no call to any positioning API; we verified this in the source code, not merely in policy.
The live map you see in the app comes from the tracking device installed in the vehicle. The data is obtained from the vehicle-tracking provider your company has a contract with, and contains coordinates, speed, heading, ignition state, street address, province, country, a timestamp, total and daily kilometres, and the driver name held in the provider's records.
The query is not made per plate: the provider's service returns the current position of every vehicle on the company's tracking subscription in one response, and the selection of the vehicles to show happens on our server, by matching against the plates we hold. Trip mileage is fetched the same way, for a date range, and selected by plate on our side. So the provider does not learn who looked up which vehicle; the data set it returns is wider than what is needed, and the rest is discarded unused.
This location data is not written to the Kunduz Suite database. Only a temporary 30-second copy is held in server memory, to reduce the load of repeated queries. The location history stays in the tracking provider's system, and its retention is governed by that provider's own policy.
- Who can see it. Users in your company's office roles (administrator, manager, operations, accounting and similar) can see the whole fleet. A user in the customer role can see only the vehicle of an ongoing trip belonging to its own company — plate, coordinates, speed, address, province and country. When the trip is completed, the customer's access to the location ends.
- It is personal data. Although the location belongs to the vehicle, it can be linked to the driver using the vehicle at the time (the tracking record names the assigned driver), so it is treated as personal data — in practice, employee location data — and every part of this policy applies to it, even though it does not come from a personal phone.
Phone-location infrastructure removed
An earlier version of this page stated that two phone-location tables left over from an old design of the application (konum_pingleri, konum_olaylari) and the two API endpoints that wrote to them were still in place. This infrastructure has been removed: both tables have been dropped from the database, the endpoints that wrote to them have been deleted from the server, and the read call in the web panel has been taken out. Phone location can no longer be collected, technically either.
07 Push notifications and message content
The app sends push notifications to your device for job assignments, trip status changes and new messages. They are delivered through the operating systems' notification infrastructure: on Android through Google Firebase Cloud Messaging, and on iOS through the Expo Push service to the Apple Push Notification service.
Message content is NOT written into notifications
When you receive a message while your app is not open, the notification title carries the sender's full name and the body only a fixed notice in Turkish: “Yeni mesaj” (“New message”) or, if a file was sent, “Yeni dosya” (“New file”). The message text and the file name do not pass through the notification infrastructure — they were deliberately removed, because they would travel unencrypted through a third party's servers and would show on your lock screen. Tapping the notification still opens the right conversation, because the notification carries the sender's identifier instead of the text. Other notifications contain a short fixed text and, where relevant, a trip or work-order number.
In-app messaging is not end-to-end encrypted; messages are stored in readable form in the database on the server. We recommend that you do not send sensitive information (identity numbers, passwords, bank details) by message.
If you do not want notifications, you can switch off your notification preference in the app, or remove the app's notification permission in your device's operating-system settings; the platform works without them. While notifications are switched off, your device's push token is not used.
Security alerts. Alerts from the security monitoring (section 12) are sent as push notifications only to the Kunduz Suite system administrator's phone. Because they pass through the same push infrastructure, their content is kept narrow: only the name of the rule that was triggered and the company name — no person's name and no IP address.
08 Who receives data
Your personal data is passed only to the parties below, and only to the extent needed for the service to work. The table also states exactly what reaches each one.
| Recipient | What is sent | Purpose | Outside Türkiye |
|---|---|---|---|
| Vehicle-tracking provider (currently SeyirMobil; the provider may change) | Outgoing: only our access credentials and, for mileage queries, a date range. Not even the plate is sent — the provider returns the whole fleet and the filtering happens on our server. Your company's customer or employee records are not sent. | Live map and trip mileage | No — no personal data is transferred to this party; data is only received from it |
| Google (Firebase Cloud Messaging) | Device push token, and the notification title and body: for a message, the sender's name and a fixed notice (“Yeni mesaj” / “Yeni dosya”) — the message text is not sent; for other notifications, a short fixed text and, where relevant, the trip or work-order number and its status; for security alerts, only the rule name and the company name (section 07) | Delivering Android notifications | Yes |
| Expo Push service | The same notification payload. iOS devices register an Expo push token and their notifications are sent through Expo's service; Android devices go directly to Firebase | Relaying iOS notifications to Apple | Yes |
| Apple (Push Notification service) | The same notification payload, via Expo | Delivery to the iOS device | Yes |
| OpenRouteService | Only a place string in the form “district, province”, a country code and two coordinate pairs. No person's name, customer name or trip number is sent | Road distance for vehicle suggestions | Yes |
| Google Drive (weekly backup) conditional — see the note below | A weekly summary spreadsheet: work-order and tank numbers, customer names, employee names, dates, status, amounts, invoice and collection details, supplier names, the name of the person who gave the health-and-safety approval and the time of approval, and free-text “before / after” notes | Backup | Yes |
| Exchange-rate service (open.er-api.com) | No application data is sent. The request is made directly from your device, so your IP address and browser/device information are visible to this service | Currency conversion | Yes |
| Map and content servers (Esri ArcGIS map tiles, unpkg, Google Fonts — web panel) | No application data is sent; your IP address and the coordinates of the map tiles you view are visible to these services. The mobile app and the marketing website make no requests to these hosts (see the next row for the mobile map) | Map display, interface components and fonts | Yes |
| Apple Maps (iOS) and the Google Maps SDK (Android) — mobile app | No application data is sent. The mobile map screens are drawn by the operating system's own map component, so your IP address, the coordinates of the region you are looking at and the positions of the vehicle markers are visible to Apple or Google. This applies equally to the screen where a customer views the location of its own shipment | Drawing the map screens in the mobile app | Yes |
| Google Maps (directions link) | When you tap a directions link, the address or coordinates travel inside the link | Directions (only when you tap the link) | Yes |
| Hetzner Online GmbH (hosting provider) | All data stored in the service; as infrastructure operator it has the technical means to access it | Servers and storage | Yes — Germany (Falkenstein), European Union |
| Competent public authorities | Data limited to the scope of the request | Legal obligation | No |
Condition for the weekly backup
The Google Drive row above does not apply to every company. The weekly summary backup is produced only for active companies with the tank-cleaning module enabled; no such file is ever created from the data of companies that use only the logistics module. The upload to Drive also requires a separate configuration on the server; without it, the backup stays only on the hosting server and nothing is sent to Google.
Not a transfer: the accounting-software bridge
If your company asks for it, invoice information for delivered jobs is passed to the accounting server in your company's own office (currently Mikro, through an agent installed on the company's premises), and invoice numbers, dates and amounts are read back. The complete list of fields sent: trip number, customer name, delivery date, transport type, currency and exchange rate, total charge, TRY sale price, container number, route (loading/destination province), loading and destination country, plate, accounting account code, account title and account tax number. A sole trader's tax number is the same as their national identity number, which is why we point this field out. This is a transfer to your company's own system, not a disclosure to a third party. The bridge is optional and is switched on only for companies that ask for it.
Not a transfer: the accounting import
Accounting software such as Luca is an import source, not a recipient. A customer can upload an invoice list exported from their own bookkeeping package; the file is parsed and the records are stored with a flag recording where they came from. The flow is one-way. Kunduz Suite makes no outbound call to Luca and sends it no data. An earlier draft of this table listed Luca as a recipient; that was wrong and has been corrected.
Not a transfer: the IP country and network lookup (DB-IP Lite)
For security purposes, the country and network of an IP address are looked up in a database that sits locally on our server. The database file is downloaded to the server and the lookup runs on the server itself, so this lookup does not send your IP address to DB-IP or to any other third party (section 12).
Other disclosures
We may also disclose data to courts, competent public authorities and our legal advisers to the extent required by law, and to the acquiring entity in the event of a merger, demerger or transfer of the business — in which case the individuals concerned will be informed.
Access by our own staff
Tenants are isolated from one another at the database level. However, the Kunduz Suite system administrator account sits outside the per-company isolation, for technical support and maintenance, and is technically able to access the data of all companies, messages included. We disclose this rather than imply that no one at the provider can ever see your data. This authority is used only when necessary. System administrator sign-ins are recorded in the security event log (section 03); note also the limitation stated in section 13: the audit log records changes, not reads.
09 Where data is stored and international transfers
Primary storage
The application, its PostgreSQL database and all uploaded files run on servers rented from Hetzner Online GmbH. The database runs on the same server and is not exposed to the network. There is no managed cloud database and no object-storage service: uploaded photographs, files and message attachments sit on the same server's disk, in separate directories for each company and under randomly generated file names. All traffic between the apps and the server is encrypted with HTTPS (TLS), using automatically renewed certificates.
Data centre location: Falkenstein, Germany (Hetzner region fsn1) — inside the European Union. This was confirmed from the server's own instance metadata rather than assumed. A WHOIS lookup on the server's IP address may show "Amsterdam"; that reflects only how the address block is registered with RIPE, and the physical data centre is in Germany.
Under Turkish law this is a transfer abroad and is treated as one throughout this policy. Under GDPR, Germany is inside the EEA, so the hosting itself does not give rise to a Chapter V transfer.
Transfers outside your country
Besides the hosting, the recipients marked “Yes” in the table in section 08 are outside Türkiye, and some of them also outside the EEA:
- Push notifications — Google, Expo and Apple operate globally, with infrastructure including the United States. What is transferred is the push token and the limited notification content described in section 07 — for a message, only the sender's name and a fixed notice; not the text of your messages.
- The weekly backup spreadsheet — uploaded to Google Drive, which is processed on US-based infrastructure. It contains customer and employee names and financial figures. This step is conditional: it is produced only for companies with the tank-cleaning module enabled, and the upload is skipped entirely if it is not configured on the server (section 08).
- Map tiles, the map library and fonts (web panel) and the exchange-rate service (requested directly from your device) — these receive your IP address (plus, for map tiles, the coordinates you view and, for the exchange-rate service, browser/device information), but no application data.
- The mobile map — Apple (iOS) or Google (Android) receive your IP address and the map region and marker positions being displayed, because the map is drawn by the operating system's map component.
- Road distance — OpenRouteService receives a place string (“district, province”), a country code and two coordinate pairs.
- Directions links — Google Maps receives the address or coordinates contained in a directions link you tap.
No personal data is sent to the vehicle-tracking provider (data is only received from it), and disclosures to competent public authorities are not transfers abroad.
Transfer mechanism: under KVKK Article 9 a specific ground is required for each transfer abroad — including the hosting in Germany — and under GDPR Chapter V an appropriate safeguard is required where data leaves the EEA. Putting standard contractual clauses in place with these recipients is work in progress. We deliberately do not claim a mechanism we have not yet concluded; when the process is complete, this section will be updated. In the meantime the optional ones can be avoided: push notifications can be switched off, and the map screens need not be opened.
10 Retention — an honest statement
Personal data is retained for the periods set out below. At the end of the applicable period it is deleted or irreversibly anonymised.
| Data | Retention period | Basis |
|---|---|---|
| Financial and accounting records (invoices, collections, ledger accounts) | 10 years | Statutory bookkeeping obligation under the Turkish Tax Procedure Law and the Turkish Commercial Code |
| Messages and message attachments | 5 years; if a company administrator permanently deletes an account, the messages that account sent and received are deleted immediately, and their attachments within about two weeks (section 11) | Evidence in the event of a dispute; general limitation period |
| Tank work-order photographs and service completion reports | 6 years from completion of the job | Proof that the service was performed; general limitation period |
| Warehouse operation documents and photographs | 5 years | Proof that the service was performed; general limitation period |
| Audit (access and change) logs | 6 years | Security obligation — KVKK Art. 12 / GDPR Art. 32 |
| Server access logs (IP address, time, requested address, browser/app identifier) | 30 days | Security obligation — KVKK Art. 12 / GDPR Art. 32; preventing abuse — legitimate interest |
| Security event log (sign-in attempts, security rule triggers, permission changes, system administrator security actions) | 1 year | Security obligation — KVKK Art. 12 and Art. 5(2)(ç) / GDPR Art. 32; protecting accounts and preventing abuse — legitimate interest |
| Read summaries (per-user, per-minute counts of requests, records, data volume and exports) | 90 days | Security obligation — KVKK Art. 12 and Art. 5(2)(ç) / GDPR Art. 32; protecting accounts and preventing abuse — legitimate interest |
| Account and user data | Until the account is deleted; within 30 days at the latest of a deletion request | Performance of the contract; KVKK Art. 7 and 11 / GDPR Art. 17 |
Removal from backups. Because backup files are rotated, a deleted record may still exist inside a backup for a short while. It is removed from backups within 90 days at the latest of the deletion being carried out.
Where a statutory obligation prevents immediate deletion, the request is not refused: the record is kept only to the extent that obligation requires, is not processed for any other purpose, and is deleted once the period expires. We tell you which records were kept and why.
Two time limits in the system are sometimes mistaken for retention periods, and are not: signed file access links expire after 7 days by default (the file itself is not deleted), and weekly backup files are rotated on the server, keeping only the last 12 copies.
11 Your rights
Under Article 11 KVKK — and, where it applies, under GDPR — you have the following rights, subject to the conditions of applicable law. You exercise them by applying to the controller:
- Access — learn whether personal data about you is processed; if it is, request information about it and a copy of it; and learn the purpose of the processing and whether the data is used in line with that purpose.
- Know the recipients — know the third parties in Türkiye or abroad to whom your data is transferred.
- Rectification — have incomplete or inaccurate data corrected.
- Erasure — have your data deleted or destroyed under the conditions in Article 7 KVKK, where there is no overriding legal obligation to keep it.
- Notification of recipients — have a correction, deletion or destruction notified to the third parties to whom your data was transferred.
- Restriction — have processing limited while a dispute over accuracy or lawfulness is resolved.
- Objection — object to processing based on legitimate interests, on grounds relating to your particular situation.
- Portability — receive data you provided, in a structured, commonly used, machine-readable format, and have it transmitted to another controller where technically feasible.
- Withdraw consent — at any time, where processing is based on consent.
- Object to automated decisions — object to a result that goes against you and was reached solely through automated analysis of your data (KVKK Art. 11(1)(g)), including the automated security measures described in section 12: a temporary IP block, ended sessions or a locked account. A lock is reviewed and lifted by a Kunduz Suite system administrator, and you can object, explain your point of view and have the measure reviewed by a person, as described below.
- Compensation — claim compensation if you suffer damage because your data was processed unlawfully.
- Complain — to your supervisory authority. In Türkiye this is the Personal Data Protection Board (KVKK Kurulu); in the EEA, the authority of your habitual residence.
How to exercise them
Write to destek@kunduzsuite.com, stating your request clearly together with information that lets us verify your identity. Requests are concluded free of charge within 30 days at the latest, the period required by KVKK, and within one month as required by GDPR; if handling a request involves an additional cost, the fee in the tariff set by the Personal Data Protection Board may be charged. Because the controller is a natural person and no postal or KEP address is published for the service, an e-mail is sufficient as a written request; you do not need to write to a postal address or use KEP.
Objecting to an automated security measure. If your account has been locked, your sessions have been ended or your IP address has been temporarily blocked (section 12), you can send your objection under KVKK Art. 11(1)(g) to the same address. If you cannot sign in with correct details, your account may have been locked; you can write to the same address in that case too.
If your request concerns your work at a company that subscribes to Kunduz Suite, that company is the controller of its operational records. Requests sent to us are answered by us; where a request would also affect the company's business records, we assess it together with the company's administrator.
If your request is refused, you find our answer insufficient, or you do not receive an answer in time, you have the right to complain to the Personal Data Protection Board (KVKK Kurulu).
Deleting your account and your data
You can request deletion of your account from inside the mobile app: Profil → Yasal ve Destek → Hesabımı Sil (Profile → Legal & Support → Delete my account; the app's interface is in Turkish) starts the request. To confirm it, you type the word you are asked for. As soon as your request is recorded, your company's administrators are notified, and the request stays on their list of pending requests until it is processed. Until the request has been completed, you can cancel it from the same screen. A deletion request for your own account cannot be opened from the web panel; if you use the web panel, use one of the two routes below.
There are also two other ways: you can ask your company's administrator, or write to destek@kunduzsuite.com with the subject “Account deletion request”, giving your name, the e-mail or phone number on the account, your company's name and your role. A deletion request sent through either of these routes that is not backed by a request opened in the app is met not by anonymisation but by the permanent deletion described below; if you prefer anonymisation, open your request from inside the mobile app. If you signed in with a department's shared site account, the in-app deletion button is deliberately not shown: that session belongs to a team, not to one person, and a single tap would cut off the whole team's access. In that case the request is handled through your administrator or the support address, after your identity has been verified.
Whichever route the request takes, it is completed within 30 days at the latest and confirmed to you; because backup files are rotated, the record also drops out of the backups within 90 days at the latest of the deletion being carried out. There is not yet a screen where you can export your data yourself; you can send a data portability request to the support address.
How a request made in the app is carried out: anonymisation
When the request you opened in the app is completed, your sign-in details and identity fields (name, e-mail, phone, password/PIN and, if any, passport and visa details) are removed, your push tokens are deleted and your open sessions become invalid; you can no longer sign in. Records whose statutory or contractual retention period has not yet ended (financial records 10 years, messages and attachments 5 years, tank work-order photographs 6 years, audit logs 6 years) are kept until the end of that period. Your account record no longer identifies you (subject to the exceptions below): your name is replaced with “Deleted User” (Silinmiş Kullanıcı) in your account and in the user field of the audit log, and the records linked to your account (messages, trips, work records) appear as linked to this anonymised account. Records whose period has expired are deleted entirely by the retention clean-up.
Your personnel file is not deleted on this route. The personal and employment details linked to your account (identity number, date of birth, address, emergency contact, start and end dates of employment; driving licence, SRC and psychotechnical details), your leave records and the documents attached to your account, with their photographs, stay linked to the anonymised account and can be seen by your company's administrators. Where no statutory retention obligation applies, you can ask in your request for them to be deleted as well.
Records that are not changed. Some records hold your name as a copy taken when a step was carried out, or as a name typed in by hand (for example the person who completed, closed or cancelled a tank work order; the person who created a service report; the person who changed the dates of a warehouse record; a driver who handed over or took over a trip; a driver's name written at warehouse entry or exit). The audit log also keeps the text of requests made about you (for example your name and e-mail address as sent when your account was created). These copies are not changed and are deleted together with the record when its retention period ends; where no statutory retention obligation applies, you can ask in your request for them to be removed.
The security event log is not changed either: so that possible unauthorised access can be investigated later, it is kept in a form that cannot be altered; after your account has been deleted it therefore still contains your name as recorded at the time, your user number, your IP address (with country and network) and your device details until its 1-year retention period ends, and it is then deleted by the weekly clean-up. Because these entries keep your name together with your user number, until they are deleted the Kunduz Suite system administrator — the only person who can see this log — could connect the other records that carry the same number (messages, work records, audit log entries) back to you; that link disappears when the entries are deleted. Read summaries contain only counts, linked to your user number, and are deleted after 90 days.
Deletion by this route therefore does not mean that every row is destroyed at the same moment; read it as the permanent de-identification of your account. You keep the right to request permanent deletion of data that is not subject to a statutory retention obligation.
Permanent deletion by an administrator: no anonymisation
Your company's administrator can permanently delete your account on the Kullanıcılar (Users) screen of the web panel with the Sil (Delete) button, without waiting for a request; this cannot be undone. Driver accounts can also be permanently deleted by your company's operations and accounting users; the consequences are the same. On permanent deletion, your account record (name, e-mail, phone, password/PIN hash and, if any, passport and visa details) is deleted entirely, and your sessions on all devices become invalid at that moment. At the same time, all messages you sent and received are deleted from the database, including the same conversations as the other party sees them; the 5-year message retention period in section 10 does not apply in this case. Your push tokens, the personnel file linked to your account (personal and employment details, and leave records) and the documents attached to your account, with their photographs, are deleted too. The files of message attachments and document photographs are also removed from the server's disk by the weekly retention clean-up, within about two weeks.
Records that remain but are unlinked from your account. Trip, work-order, warehouse, fuel, financial and similar business records, and the photographs and files you uploaded to them, remain as the company's operational data; in them, the link to your account as the person who carried out a step, uploaded a file or drove the vehicle is removed. Copies of names held in records, and names typed in by hand, do not change. The separate employee record kept for tank-cleaning site staff is not deleted either; only its link to your account is removed. The audit log entries for actions you carried out remain for 6 years and are unlinked from your account; unlike anonymisation, however, your name in these entries is not changed and stays as it was recorded. The stored text of requests made about you does not change either.
Records that remain unchanged. The security event log (1 year) and the read summaries (90 days) are not tied to the account record; permanent deletion therefore does not affect them, and they remain until their retention periods end. If you opened a deletion request in the app and it did not end in anonymisation, the request record also remains, together with your name, e-mail address, phone number and role as recorded when the request was made and the reason you gave; no retention period is defined for this record, and you can ask for it to be removed through the support address. Records also drop out of the backups within 90 days at the latest of their deletion from the database, and message-attachment and document-photo files within 90 days at the latest of their removal from the server's disk.
The Pasife al (Deactivate) option on the same screen, on the other hand, is not a deletion: the account can no longer sign in, but none of its records are deleted. Anonymisation is applied only when a request opened in the app is completed. Permanent deletion can also be applied to an account that has already been anonymised; the consequences of permanent deletion then apply to that account as well — for example, the messages kept for 5 years under anonymisation are deleted at that moment.
What a completed request actually removes (anonymisation)
| Data | When your request is completed |
|---|---|
| Account record: name, e-mail, phone, password/PIN hash, department, passport and visa details | Removed permanently. The user row itself is not deleted: it stays as an identity-free trace so that the records linked to it remain consistent until their own retention periods end; your name in it is replaced with “Deleted User”. Your open sessions become invalid immediately and you can no longer sign in. |
| Your in-app messages (sent and received) | Kept until the 5-year retention period in this policy ends (they are also the other party's records); the sender appears as the anonymised account (“Deleted User”). When the period ends they are deleted entirely by the retention clean-up. |
| Files attached to those messages | Kept with the messages for 5 years and deleted from disk together with the record when the period ends. If you want them deleted earlier, say so in your request; if they are not covered by a statutory retention obligation, we delete them manually. |
| Registered push device | Deleted; no notifications are sent to your account. |
| Personnel file (the personal and employment details and leave records linked to the account on the Users screen) and documents attached to the account, with their photographs | Not deleted or changed; they stay linked to the anonymised account and can be seen by your company's administrators. Where no statutory retention obligation applies, you can ask in your request for them to be deleted as well. |
| Trips, work orders, warehouse operations, expenses, vehicle costs | Kept as the company's operational data; they stay attached to the anonymised account, which appears as “Deleted User”. Where a record holds a copy of your name (for example as the person who completed, closed or cancelled a tank work order or created a service report) or a name typed in by hand, that name is not changed and is deleted with the record when its retention period ends; where no statutory retention obligation applies, you can ask in your request for it to be removed. |
| Audit log entries | Kept for 6 years. The name of the person who carried out the action is replaced with “deleted user”; the user number they refer to remains and now belongs to the anonymised account (see the security event log row). The stored request content (first 500 characters) is not changed and may contain your name or e-mail address, for example from the request that created your account. They are deleted by the retention clean-up when the period ends. |
| Security event log entries | Kept unchanged until their 1-year retention period ends, including your name as recorded at the time, your user number, IP address (with country and network) and device details. The log is kept in a form that cannot be altered, so that possible unauthorised access can be investigated later; deleting the account therefore does not change these entries. Because these entries keep your name together with your user number, until they are deleted (at most 1 year) the Kunduz Suite system administrator — the only person who can see this log — could connect the other records in this table that carry the same number back to you. The basis is the data-security obligation (KVKK Art. 12) and the protection of accounts. They are deleted by the weekly clean-up once they are a year old. |
| Read summaries | Kept with your user number — counts only, no content — until their 90-day retention period ends, then deleted automatically. |
| Employee record (site staff: name, start date, certificates) | A separate record from the user account. It is not deleted automatically and must be requested separately. |
| Photographs and files you uploaded to work records | Remain on the server unless the work record they belong to is itself deleted. |
| Copies inside backups | Because backup files are rotated, a record may remain in backups for a while; it drops out of them within 90 days at the latest of your request being completed. |
What permanent deletion by an administrator removes
When a company administrator deletes an account on the Kullanıcılar (Users) screen of the web panel with Sil (Delete) and then Evet, kalıcı olarak sil (Yes, delete permanently), no anonymisation takes place: the account record and some records directly tied to it are deleted from the database at that moment, and the other records remain but are unlinked from the account. This cannot be undone. Driver accounts can also be permanently deleted by the company's operations and accounting users; the consequences are the same. Permanent deletion can also be applied to an account that has already been anonymised; the consequences below then apply to that account as well (for example, messages kept for 5 years are deleted at that moment).
| Data | On permanent deletion by an administrator |
|---|---|
| Account record: name, e-mail, phone, password/PIN hash, department, passport and visa details | Deleted immediately; the user row itself does not remain either. Sessions on all devices become invalid at that moment and the account can no longer be used to sign in. |
| Your in-app messages (sent and received) | Deleted immediately — including the same conversations as the other party sees them. The 5-year message retention period in this policy does not apply in this case. |
| Files attached to those messages | Deleted from the database immediately, together with the message; the file itself is also removed from the server's disk by the weekly retention clean-up, within about two weeks. |
| Registered push device | Deleted. |
| Personnel file (the personal and employment details and leave records linked to the account on the Users screen) and documents attached to the account, with their photographs | Deleted immediately. The files of the document photographs are also removed from the server's disk by the weekly retention clean-up, within about two weeks. |
| Trips, work orders, warehouse operations, fuel movements, expenses, vehicle costs and financial records | Kept as the company's operational data; the link to your account as the person who carried out or approved a step, or as the driver, is removed. Where a record holds a copy of your name (for example as the person who completed a tank work order, or as the driver's name written at warehouse entry or exit) or your name was typed in by hand, that name is not changed; where no statutory retention obligation applies, you can ask for it to be removed. |
| Photographs and files you uploaded to work records | Kept with the work record they belong to; the link to your account as the uploader is removed, and where the uploader's name is held as a copy, that name does not change. |
| Audit log entries | Kept for 6 years. In the entries for actions you carried out, the link to your account is removed, but the name of the person who carried out the action is not changed: unlike anonymisation, your name as recorded at the time remains. The stored request content (first 500 characters) is not changed either and may contain your name or e-mail address, for example from the request that created your account. The deletion itself is also written to the audit log, under the name of the person who carried it out. The entries are deleted by the retention clean-up when the period ends. |
| Security event log entries | Kept unchanged until their 1-year retention period ends: your name as recorded at the time, your user number, IP address (with country and network) and device details. Because this log is not tied to the account record, permanent deletion does not affect it; the entries are deleted by the weekly clean-up once they are a year old. |
| Read summaries | Counts only. Because they are not tied to the account record either, they are kept with your user number for 90 days and then deleted automatically. |
| Account deletion request record (if you opened a request in the app and it did not end in anonymisation) | Kept; your name, e-mail address, phone number and role as recorded when the request was made, and the reason you gave, are not deleted. No retention period is defined for this record; you can ask for it to be removed through the support address. |
| Employee record (site staff: name, start date, certificates) | A separate record from the user account; it is not deleted, only its link to your account is removed. Its deletion must be requested separately. |
| Copies inside backups | Because backup files are rotated, deleted records may remain in backups for a while; records drop out of them within 90 days at the latest of their deletion from the database, and message-attachment and document-photo files within 90 days at the latest of their removal from the server's disk. |
These tables reflect how the application behaves today; the same tables appear in Turkish on the support page. Where certain records cannot be deleted because of a statutory retention obligation, we tell you so, with the reason. Requests for rectification, information and data portability are handled through the same address.
12 Security measures
Only measures that are actually implemented are listed here. No certifications are claimed, and none are implied.
- Tenant isolation enforced by the database. Every operational table carries a tenant identifier and is protected by PostgreSQL row-level security in forced mode, applied to both read and write. The application connects with a database role that cannot bypass it. On startup the service verifies this and refuses to run in production if the guarantee is missing. An application bug therefore cannot leak one customer's data to another.
- Credentials are hashed. User passwords and driver PINs use bcrypt. Site staff PINs use HMAC-SHA256 with a secret "pepper" kept in the server environment rather than in the database. If that secret is missing in production, the application fails closed rather than degrading silently. We do not claim that a stolen database backup could not expose short PINs today: a migration bridge still in place is described under "Known limitations" below.
- Administrators can set a staff PIN but cannot read it. The PIN and its hash are stripped from API responses; only a "PIN is set" flag is returned.
- Encryption in transit. All traffic between the apps and the server uses HTTPS/TLS with automatic certificate management.
- Signed, time-limited file links. Uploaded photographs and attachments are stored under random UUID filenames and are not publicly served. Each link carries an expiry and an HMAC signature, verified with a constant-time comparison. Path traversal is rejected, HTML/SVG/JavaScript files are never served, content type is forced from the extension, and a restrictive content-security policy plus no-sniff headers are applied.
- Role-based access control across ten roles, with endpoints restricted to the roles that need them — for example a customer account can only ever reach records tied to its own account, and the warehouse role sees only the warehouse screens and has no access to messaging.
- Audit logging with credential masking. Changes are recorded with the acting user, the action and the request payload; fields whose names suggest a password, PIN, token, key or secret are masked before the payload is written to disk.
- Login hardening. A uniform error message, a constant-time response floor and a decoy hash computation prevent account enumeration; failed attempts are rate-limited. Sessions can be invalidated in bulk when necessary; at present this is done only on the server side, and there is no button in the interface that offers it to users.
- Further controls: rate limiting, restricted cross-origin access, size and connection ceilings on the real-time channel, separate signing keys for user and administrator sessions with a minimum key length enforced in production, and a session-version mechanism that allows existing sessions to be invalidated.
- Token storage. On mobile, the session token, your user profile and your workspace record are held in the device's secure keystore (iOS Keychain / Android Keystore).
Security monitoring
To protect accounts, and to detect and prevent unauthorised access attempts, large-scale password attacks (such as credential stuffing) and unusual bulk data extraction, the service keeps a security event log and read summaries. To notice something unusual, a sign-in to an account and the amount of data retrieved from it are also compared with that account's own recent history. What these records contain is listed in section 03, and how long they are kept in section 10.
- Who can see them. The security event log and the read summaries can be viewed only by the Kunduz Suite system administrator; company administrators do not see them.
- Country and network from the IP address, looked up locally. The country and network an IP address belongs to are looked up in a database that sits locally on our server and is updated regularly (DB-IP Lite). The database file is downloaded to the server and the lookup runs on the server itself; this lookup does not send your IP address to any third party. The result is used only for security — for example, to notice a sign-in to an account from an unusual country, or from a data-centre or VPN network — and never for advertising or marketing. Attribution: IP Geolocation by DB-IP (CC BY 4.0 licence).
- Automated measures. When there are clear signs of an attack (for example, many failed sign-ins in a short time), or when an unusual amount of data is retrieved from an account in a short time, the IP address concerned may be temporarily blocked, the account's open sessions may be ended, or the account may be locked to protect it. A lock is reviewed and lifted by a Kunduz Suite system administrator. For security reasons, a locked account shows the same error at sign-in as a wrong password; if you cannot sign in with correct details, your account may have been locked. You can object to these measures through the procedure in section 11.
- Security alerts. These are sent as push notifications only to the Kunduz Suite system administrator's phone; they contain only the rule name and the company name, with no person's name and no IP address (section 07).
If there is a breach
If personal data is unlawfully accessed, we will notify the Turkish Personal Data Protection Board (KVKK Kurulu) as soon as possible and in any event within 72 hours of becoming aware of it, and we will inform the affected individuals and, where we act as processor, the subscribing company without undue delay. Where GDPR applies, the same 72-hour rule under Article 33 is followed.
13 Known limitations
No system is without weak points. These are the ones we know about and consider material enough to disclose:
- The audit log records changes only, not reads. There is no record of which user viewed a given record — only of who modified it. Separately, the server access log keeps which IP address requested which address for 30 days; it does not contain the user account or the content of the request. The read summaries count how much data each user retrieved; they do not show which records were viewed. We do not claim otherwise.
- Signed file links are not bound to a specific user. Anyone who obtains a link can open that file until it expires — up to 7 days by default. We therefore recommend that you do not share file links outside the application.
- The audit log's request payload is not scrubbed of personal data. Masking covers credentials only; an identity number or phone number submitted in a form is written to the log in readable form.
- National identity numbers are stored without field-level encryption or masking. They are protected by tenant isolation, role restrictions and transport encryption, but not by encryption of the field itself. Note also that the identity number held on a tractor-unit record is visible to every office role (admin, manager, operations, patron and accounting), not only to administrators; only the identity number on the employee record is restricted to administrator and manager.
- A plain-text PIN column still exists for site staff. PINs were moved to HMAC-SHA256 hashes, but the old plain-text column was not dropped, and where a hash has not yet been generated for a person, verification still accepts the plain-text PIN. The plain text is cleared when that person's PIN is next changed, or when the back-fill tool is run. Until the column is dropped, a stolen database backup could expose the PINs of any staff record that has not yet been migrated. The column will be dropped once every record has been migrated to a hash; when it is, this item will be removed from the list.
- Messages are not end-to-end encrypted; they are stored in readable form in the database on the server. Their text is not sent in push notifications (section 07).
- In the web client, the session token is stored in browser local storage; a successful cross-site scripting attack against the browser could expose it. On shared computers, sign out when you have finished. The mobile app is not affected.
- A provider system administrator can technically reach all tenants' data, including messages (section 08). This authority is used only when necessary, but we do not hide that it exists.
14 Children
Kunduz Suite is business software designed for corporate use and is not directed at anyone under the age of 18. Accounts are opened by the companies that use the service, for their own employees and business partners; the application has no sign-up flow open to individual users.
If we find, or are told, that a child's personal data has been entered into the system without our knowledge, we delete that data without delay. You can report such a case to the address in section 11: destek@kunduzsuite.com.
15 Cookies, tracking and local storage
Kunduz Suite does not use cookies. Authentication uses a bearer token sent with each request, not a session cookie. There are no advertising, analytics or tracking cookies anywhere in the product or on the marketing website. When you sign out, the records kept on the device are deleted.
What is stored on your device:
- Mobile app: in the operating system's secure key store (iOS Keychain / Android Keystore), not only the session token but also your user profile (name, role and account details) and the details of the company you belong to; your notification preference (if you have switched notifications off) is kept there too.
- Web panel: the session token and interface preferences in browser local storage. The session lasts 30 days by default; system administrator sessions last 12 hours.
- Marketing website: one entry recording your language choice. It is strictly functional, is never sent anywhere, and does not identify you. The site makes no external requests at all — fonts are embedded in the page rather than loaded from a font provider — which is why no cookie banner is shown.
In the web panel, map and interface components are loaded from external servers, so your IP address is visible to those providers, as stated in section 08. In the mobile app the map is drawn by the operating system's map component, so your IP address is visible to Apple or Google (section 08 as well).
You can clear this storage at any time through your browser or by signing out; doing so simply ends your session.
16 Mobile app permissions
The permissions the mobile app asks for — and does not ask for — are listed below. Permissions are not requested in bulk in advance, but at the moment you first use the feature concerned.
| Permission | Used for | When requested |
|---|---|---|
| Camera | Work-order, task, warehouse and expense-receipt photographs | At the moment you take a photo |
| Photo library | Attaching an existing image to a record or a message | At the moment you attach an image; individual files are chosen by you — the app is not granted bulk access to your library |
| Notifications | Job assignment, message and trip-status alerts | When notifications are first enabled |
| Location | Not requested. The app has no component that reads the device's location (section 06) | Never |
The app requests no permission other than the three above. On iOS, usage descriptions are declared only for the camera and the photo library; no location, contacts, calendar or health permission is declared.
17 Changes to this policy
This policy may be updated because of changes in legislation or in the way the application processes data. When it is updated, the "last updated" date and the version number at the top of this page change; for significant changes, users are also informed in the application or by e-mail.
Version 1.0 of this policy took effect on August 4, 2026. Version 1.1 (October 10, 2026) added the server access log and its 30-day retention period. Version 1.2 (October 12, 2026) added the security event log, read summaries, the country and network lookup from IP addresses, the automated security measures and the DB-IP attribution. In the same version, the retention period of audit logs and of tank work-order photographs was corrected to the 6 years applied in the system; the notification content described in sections 07 and 08 was updated to show that neither the message text nor details such as customer names or routes are sent in notifications; and the description of deletion in section 11 was corrected to show that the request is started from the mobile app and which records anonymisation does not change. This English version was also brought into line with the Turkish text where it had fallen behind; among other things, message notifications do not carry the message text (sections 07, 08, 09 and 13), the phone-location tables have been removed (section 06), account deletion can be requested from inside the mobile app and is carried out by anonymisation (section 11), and the statement on how changes to this policy are announced now matches the Turkish text (this section; earlier English versions said that affected users would be notified before a material change took effect). Version 1.3 (October 12, 2026) added the consequences of a company administrator permanently deleting an account (including messages being deleted before their retention period ends) to sections 10 and 11; section 11 now also states that a deletion request not opened in the app is met by permanent deletion and that anonymisation does not delete the personnel file; the version also made clear that the period for removal from backups starts when the deletion is carried out, and removed wording that implied a desktop application exists, so that those passages now refer only to the web panel. The same version corrects the name of the provider the web panel loads map tiles from (Esri ArcGIS, not OpenStreetMap).
Superseded versions are kept so that it is possible to see what changed and when, and are sent to you on request to destek@kunduzsuite.com.
18 Contact
For any question about this policy, or to exercise the rights described in section 11:
- All enquiries, privacy questions and rights requests: destek@kunduzsuite.com
This is the only contact channel we operate. No telephone support line and no postal address are published; a written request sent by e-mail is sufficient to exercise the rights described in section 11.
If you are in Türkiye, you may also apply under the procedure set out in KVKK and, if unsatisfied with our response, complain to the Personal Data Protection Board (KVKK Kurulu). If you are in the EEA or the UK, you may complain to your local supervisory authority.
Questions about your data?
Write to us. We will answer within 30 days, and sooner if we can.