Citiveo is a city-guide and local-business platform. This policy explains which personal data we process when you use Citiveo, why we process it, with whom we share it, and what rights you have in relation to it.
Data controller: Ebtnet Bilişim ve İnternet Hizmetleri Limited Şirketi, Esenyalı Mah. Yanyol Cad. Varyap Plaza No:61 İç Kapı No:247, Pendik / İstanbul (0323141039100001). Contact: kvkk at citiveo.com.
1. What data we process
Account data. Registration on Citiveo is carried out using e-mail address and password only. We store your e-mail address, the irreversible hash of your password (bcrypt), your name if provided, and your preferred language. Upon registration, we send a verification link valid for 24 hours to your e-mail address.
Phone number (optional). A phone number is not a sign-in method on Citiveo and is not verified. It is stored solely as contact information, and only if you choose to add it. You may remove it from your profile at any time.
Content you generate. Your reviews and ratings, the places you have saved, the routes you have created, and the photos you have uploaded.
Coupon and passport data. The single-use coupon codes you have obtained, whether those codes have been redeemed, the points you have earned, and your city-passport stamps.
Business-ownership data. The application information you submit in order to claim a business, and the verification documents you upload (such as a tax certificate, licence, tour-guide badge or health-tourism authorisation certificate). These documents are not publicly accessible; they are viewed only by the authorised personnel reviewing the application. Image location metadata (EXIF data) is stripped at the time of upload. For health institutions, a claim may also be verified by calling the institution back on its official phone number as listed by the Ministry; the date and outcome of this call are recorded.
Billing information. The billing information you provide when purchasing a business subscription: business type, the first name and surname of the authorised person, the billing title or full name, the tax office and tax number or (for a sole proprietorship) the Turkish national identity number, the billing address, the billing e-mail address and, where applicable, e-invoice details.
Payments. For business subscriptions, your card details never reach us. Payment is taken on iyzico's own secure page; iyzico is a licensed payment institution. For automatic renewal, your card is stored by iyzico with your consent. We hold only the following:
- card tokens issued by iyzico, which cannot be used outside iyzico;
- your card's brand, type (credit/debit card), last four digits and expiry month/year;
- subscription status, amount, currency, and receipt and invoice records;
- a record of the consent you gave to the storage of your card and to automatic renewal: date, time, IP address and the version of the consent text.
City-partner data. The information you submit when applying to the city-partner programme (region preference, experience, references), together with, for active partners, the name, IBAN and tax-identification details required for service-fee payments, as well as service-fee and payment records. Any change to an IBAN is confirmed with an authenticator app (two-factor authentication).
Usage measurement. On the website and in the mobile app, we measure events such as which business page is viewed and whether the call, WhatsApp or directions buttons or social-media links are tapped. For on-site searches, we count which result was selected (the query, the result type and its position) as daily aggregates. This measurement is non-identifying: even if you are signed in, an event is not linked to your account, no user ID is recorded, no IP address is stored and no cookies are used; on the website, the browser's "Do Not Track" signal is honoured, and while this signal is on, no event is recorded at all. An event record contains only the business, the event type (e.g. "call button"), the place where the event occurred (e.g. "list", "map") and the time. Measurement data is shown to the business owner in their dashboard as aggregate counts.
Google Analytics 4 (with your explicit consent only). If you enable the Analytics category in your cookie preferences, Google Analytics 4 is loaded to measure how you use the site. In that case, the data processed comprises: pseudonymous online identifiers (a cookie ID placed in your browser), the pages you view and your interactions on those pages, and device and browser information. Your IP address is anonymised; Google Analytics 4 does not record or store IP addresses. If you do not grant consent, Google Analytics 4 is not loaded at all. No analytics or measurement code runs on the administration panel, the business dashboard, or the sign-in and profile pages.
Two-factor authentication data. When you use two-factor authentication (mandatory for business, city-partner and administration accounts):
- the secret key paired with your authenticator app is stored in encrypted form;
- your recovery codes are stored only as irreversible hashes;
- a record is kept of the devices for which you have selected the "remember this device" option.
Location. We use your location only when you grant permission and only for the duration of that session (for "near me" features). We do not track your location in the background and we do not store your location.
Mobile app. When you use the Citiveo mobile app, in addition to the above:
- Notifications. If you allow notifications, then, so that we can send notifications to your device, a random device ID generated by the app for each installation, the notification token, the platform (Android/iOS), the app version, the language and your device's time zone are stored together with your account. The time zone is used only to avoid sending notifications during night-time quiet hours. Notifications are delivered via Expo and, on Android, Google Firebase Cloud Messaging, and on iOS, Apple Push Notification service. When you sign out, the device record is deleted. Notification permission is not requested as soon as the app opens; you are asked only when you take an action such as setting a reminder or following something.
- Error reports. When the app crashes or an error occurs, so that we can find and fix the problem, the error log (the error message and the line of code at which execution stopped), the device model, the operating system version, the app version, the app language and the selected city are sent to the error-reporting service Sentry. Your account ID, e-mail address, phone number, location, screenshots and any content you have written are not sent; session information contained in link addresses is removed before sending.
- Camera and photos. The camera is used only to scan coupon QR codes in business mode and when you want to add a photo. Camera images are not recorded; only the photo you choose to upload is sent to the server, with its location data (EXIF data) stripped.
- Location. The app asks for your location only when you tap an option such as "Use my location", "Near me" or directions; your location is not saved on the server.
- App integrity check. To confirm that requests to our servers come from the genuine Citiveo app, and to limit automated bulk copying of our content, the app creates a random installation ID for each installation; this ID is not linked to your account. On Android, Google Play services on your device produce an integrity token (Google Play Integrity API), which we send to Google to be checked; on iOS, the app uses Apple's App Attest service and we verify the result on our own servers. We store only the installation ID, the platform, the app version and the outcome of the check (whether the app is recognised by Google Play and whether the device passed the integrity check); on iOS, also the public key the device generated for this check. Your name, e-mail address, location and anything you have written are not part of this check.
- Request limits. To protect the service from abuse, requests to our servers are counted per installation and per IP address. Minute counters are kept only in the server's memory; hourly and daily counters, which contain the installation ID or the IP address, are deleted after 2 days.
- Signing in on the app. When you sign in on the app, a sign-in token is stored on your device. On our side we keep only an irreversible hash of this token and its validity period (60 days, renewed while you use the app). When you sign out or request the deletion of your account, your tokens are revoked.
Approximate location (IP). When you have not granted location permission, we use the approximate city that Cloudflare derives from your IP address to suggest cities near you. This information is used only for that one request; it is not stored, logged or shared with anyone. No permission is requested, because your device's location is not accessed.
Health tourism section. Citiveo does not collect health data or patient data:
- When you press a health institution's contact buttons (WhatsApp, phone, e-mail, website), you contact the institution directly; the privacy rules of the institution and of the relevant service apply to that communication.
- These taps are counted in a non-identifying way, only in aggregate by institution, button and date; even if you are signed in, who you are is not recorded.
- The doctor information entered by institutions (title, name, specialty, languages) is entered by the institution after obtaining the consent of the persons concerned.
Phone-view log. When you are signed in and reveal a health institution's masked phone number, we record which institution it was, the time and your account. This record is used only to limit misuse and to show the institution how many times its number was viewed; it is deleted after 12 months.
City assistant. The questions you ask the city assistant are sent to Anthropic so that the answer can be generated (see section 3). So that we can keep the service within its limits and improve the answers, we keep each question together with the city, the language and whether you marked the answer as helpful; if you are signed in, with your account, otherwise with a salted, irreversible hash of your IP address instead of the IP address itself.
Reporting and blocking. When you report an assistant answer, a review, a photo or a question, we record the reported item, the reason you chose, your optional note and, if you are signed in, your account; for an assistant answer, the question and the answer are kept with the report so that it can be reviewed. When you hide a person's content, we record that choice together with both accounts; the other person is not told.
2. Why we process data and our legal basis
| Purpose | Data | Legal basis |
|---|---|---|
| Creating your account and enabling sign-in | e-mail address, password hash | Formation and performance of a contract |
| Issuing coupons and validating them at the checkout | coupon code, redemption record | Performance of a contract |
| Publishing reviews | content, account name | Performance of a contract / legitimate interests |
| Verifying business ownership | application, documents, call-back record | Performance of a contract, legal obligation |
| Subscription billing, automatic renewal and invoicing | billing information, card tokens and card details (brand, type, last four digits, expiry), payment and invoice records | Performance of a contract, legal obligation (tax legislation) |
| Proving consent to card storage and automatic renewal | consent record (date, time, IP, text version) | Legal obligation, establishment and protection of a right |
| Preventing abuse and payment fraud | rate limiting, human verification, IP address at the time of payment | Legitimate interests |
| Business-dashboard statistics | non-identifying measurement events | Legitimate interests |
| Sending notifications in the mobile app | device ID, notification token, platform, app version, language, time zone | Performance of a contract (when you grant notification permission) |
| Finding and fixing errors in the mobile app | error report, device model, operating system and app version | Legitimate interests |
| Newsletter and marketing communications | e-mail address | Explicit consent (including IYS), withdrawable at any time |
| Measuring how the site is used (Google Analytics 4) | pseudonymous identifiers, pages viewed, device and browser information | Explicit consent, withdrawable at any time via cookie preferences |
| Protecting your account with two-factor authentication | encrypted authenticator key, recovery-code hashes, remembered-device records | Performance of a contract and data-security obligation (KVKK Art. 12) |
| Confirming that requests come from the genuine app, and preventing abuse and bulk copying of content | installation ID, integrity-check result, app version; installation ID and IP address in request counters | Legitimate interests |
| Keeping you signed in on the mobile app | sign-in token hash | Performance of a contract |
| Answering your questions in the city assistant and keeping it within its limits | question, city, language; account ID or salted IP hash | Performance of a contract / legitimate interests |
| Reviewing reported content and applying your blocks | report record, block record | Legitimate interests |
Consent to marketing is separate from your sign-in and use of the service. Unsubscribing from the newsletter has no effect on your account.
3. With whom we share data
The following are the service providers we actually use in order to operate the service. We do not sell your personal data to anyone for advertising purposes.
| Provider | Purpose | What is transferred |
|---|---|---|
| iyzico (Turkey) | Subscription billing, card storage, 3D Secure, refunds | The authorised person's first name and surname, e-mail address, phone number, billing address, IP address at the time of payment, Turkish national identity number for sole proprietorships, amount and subscription reference. Card data goes directly to iyzico and never passes through us |
| Resend (US/EU) | Transactional and newsletter e-mails | E-mail address, message content |
| Cloudflare Turnstile (US) | Bot/human verification on forms | Technical data relating to the verification request |
| Anthropic (Claude) (US) | Content translations and city-assistant responses | The text content being translated; the question you ask the assistant |
| CollectAPI (Turkey) | On-call pharmacy data | Province/district information only; no personal data is transferred |
| Open-Meteo (EU) | Weather and sea conditions | City coordinates only; no personal data is transferred |
| AeroDataBox / RapidAPI | Flight information board | Airport code only; no personal data is transferred |
| OpenFreeMap / OpenStreetMap | Map tiles | Technical request data from the browser displaying the map |
| Cloudflare | CDN, security and image delivery | Technical connection data |
| Expo (US) | Delivery of mobile app notifications | Notification token and notification content |
| Google Firebase Cloud Messaging (US) / Apple Push Notification service (US) | Delivering the notification to the device (Android / iOS) | Notification token and notification content |
| Sentry (EU, Germany) | Mobile app error reports | Error log, device model, operating system and app version, language, selected city; account ID, e-mail address and location are not sent |
| Google (Google Analytics 4) (US) | Site-usage statistics, with your explicit consent only | Pseudonymous identifiers, pages viewed, device and browser information; IP address is anonymised |
| Google Play Integrity API (US) | Checking that the Android app is genuine and runs on a genuine device | The integrity token produced on your device by Google Play services; no account data, e-mail address or location is sent |
| Apple App Attest (US) | Checking that the iOS app is genuine | Our servers send no personal data to Apple; the check runs between your device and Apple |
For invoices to be issued, your billing information and receipt records are shared with the certified public accountant who provides accounting services on behalf of Citiveo.
International transfers. Some of the providers listed above are located outside Turkey. In such cases, personal data is transferred pursuant to KVKK Art. 9 and GDPR Chapter V, on the basis of the provider's standard contractual clauses and technical security commitments. No personal data is sent to the on-call pharmacy, weather or flight providers; only geographic information such as a city or an airport is transmitted to them.
International transfers of Google Analytics 4 data. Data processed through Google Analytics 4 is transferred to Google's servers in the United States. This transfer is based on your explicit consent under KVKK Art. 9: if you do not enable the Analytics category, Google Analytics 4 is not loaded and this transfer does not take place. You may withdraw your consent at any time by disabling the Analytics category via the "Cookie preferences" link at the bottom of every page; upon withdrawal, collection ceases, but data already transmitted cannot be recalled.
4. How long we retain data
- Account data: for as long as your account remains open.
- Reviews: for as long as they remain published; if you delete your account, your reviews are anonymised under the label "deleted user".
- Coupons and passport stamps: if you delete your account, unused coupons are invalidated and stamps are deleted.
- Ownership documents and call-back record: deleted 1 year after the claim is decided (approved, rejected or revoked); pending applications keep them. For an approved health institution, the certificate file, the call-back date and who made the call are deleted at that point; only the two facts behind the "verified" badge (that the call-back confirmed the institution, and the date the certificate was verified) are kept while the listing remains verified.
- Card tokens: your card stored with iyzico is deleted, and the token held by us becomes invalid, in the following cases:
- when the subscription ends;
- when the 7-day period during which payment could not be collected expires;
- when you change your card;
- when you delete your account.
- Payment, receipt and billing information and the card-storage consent record: 10 years, as required by tax and commercial legislation (Turkish Commercial Code Art. 82, Tax Procedure Law Art. 253).
- City-partner service-fee and payment records: 10 years, as required by tax legislation.
- Non-identifying usage measurement: individual event records are retained for 400 days, after which only daily aggregate counts remain; as they contain no personal data, these aggregate statistics may be retained indefinitely.
- Mobile app device record (notifications): until you sign out or delete your account; tokens reported as invalid by the notification service are deleted.
- Mobile app error reports: retained in Sentry for a maximum of 90 days, then deleted.
- Google Analytics 4: identifier cookies remain in your browser for a maximum of 2 years; event data on Google's side is deleted upon expiry of the retention period configured in Google Analytics.
- Two-factor authentication: the secret key and recovery-code hashes are retained for as long as two-factor authentication is enabled; remembered-device records expire after 30 days. All three are deleted when you disable two-factor authentication.
- App integrity check: the installation record is deleted 180 days after the app last contacted us; request counters are deleted after 2 days, and one-time check codes 1 day after they expire. Daily totals of check results contain no personal data and are kept for 400 days.
- App sign-in tokens: valid for 60 days from their last use; revoked at once when you sign out or request the deletion of your account, and revoked tokens are deleted within 7 days.
- City assistant questions: kept for 180 days, then deleted.
- Content reports: kept until they are reviewed and for 12 months after the review, then deleted; if you delete your account, your account and your note are removed from your reports before then.
- Blocks: until you remove the block or either account is deleted.
- Security and audit logs: entries recording actions on your account are kept in the database for 1 year, then moved to a monthly archive file kept for accountability. Entries belonging to a deleted account are not archived; they are deleted at the one-year mark.
- Notifications: after 90 days, notification records are moved to a monthly archive that keeps only the type, channel, status and dates with your account ID, without your e-mail address, phone number or the message text. Entries belonging to a deleted account are not archived.
- Used coupons: the redemption record stays in the business's statistics; if you delete your account, it no longer carries your name, e-mail address or phone number.
- Backups: we keep the last 7 nightly copies of the database, so deleted data leaves the backups within 7 days.
5. Your rights and how to exercise them
Under KVKK Art. 11 and GDPR Arts. 15–22, you have the rights to access, rectify and erase your data, to object to its processing, and to data portability. Citiveo has built two of these directly into the product:
- Download your data. From your profile page, you can obtain an immediate machine-readable export of the data associated with your account.
- Delete your account. You may submit a deletion request from your profile. The request is processed with a 30-day waiting period: during this period you may change your mind and cancel the request; once the period expires, your account is irreversibly deleted and your personal data fields are cleared. If you are the sole owner of a business, you must first transfer your ownership of the business or close it. Payment and invoice records that are subject to a statutory retention period continue to be retained for that period.
For all other requests and complaints: kvkk at citiveo.com. We will respond to your request within 30 days at the latest. You also retain the right to lodge a complaint with the Personal Data Protection Board (Kişisel Verileri Koruma Kurulu).
6. Security
Our measures:
- Passwords are stored only as bcrypt hashes.
- Session cookies are HttpOnly and HTTPS is enforced.
- Location metadata (EXIF data) is stripped from uploaded images.
- Rate limiting and Cloudflare Turnstile human verification are applied to guard against abuse.
- Access to administration screens is role-based.
- Two-factor authentication is mandatory for business, city-partner and administration accounts; the authenticator app's secret key is stored in encrypted form, and recovery codes are stored only as irreversible hashes.
- Card details never reach our systems.
- Card tokens and secret keys are not written to the technical logs of the payment system.
Protection against bots and scrapers. To make bulk copying of our content by automated tools harder, we show a human check to connections that send many requests in a short time. Only for these protection events (a check shown, a hidden trap link, a fake search-engine bot, a block) do we record the IP address, browser information and the address requested; these records are deleted after 7 days and are not used for analytics. The cv_h cookie, which remembers for 1 hour that you passed the check, contains no identity.
7. Children
Citiveo is not designed for persons under the age of 18 and does not knowingly collect personal data from children.
8. Changes
When we update this policy, we will change the "last updated" date at the top of the page. For material changes, we will notify users who have an account by e-mail.