Bu metni Türkçe oku

Privacy

Kadranname Privacy Policy and Personal Data Notice

Version 1.0 · Effective date: 19 November 2026

This is the English translation of the Turkish text. If the two differ, the Turkish text prevails, unless the mandatory law of your country gives you the right to rely on this version (section 19).

In short

This summary is for convenience; the full text below governs.

1. What this policy covers

1.1. This policy explains how the Kadranname mobile app (App Store and Google Play versions) and the kadranname.com website process personal data. It is the information notice required by Article 10 of Türkiye's Law No. 6698 on the Protection of Personal Data ("KVKK") and the information required by Articles 13 and 14 of the EU General Data Protection Regulation ("GDPR") and the UK GDPR.

1.2. The third-party services the app connects to (Google, Apple, the AI provider you choose, the sites you add) are governed by their own privacy policies. This policy describes what they do only as far as the developer can know it and as it concerns you.

2. Controller and contact

2.1. Controller: the developer of Kadranname (the "developer"). The developer is an individual resident in Türkiye; their name is shown as the developer or seller on the app's App Store and Google Play pages.

2.2. Contact and requests: support@kadranname.com

2.3. Website: https://kadranname.com

2.4. The developer has no data protection officer, and no representative has been appointed in the European Union or the United Kingdom. Wherever you are, you can reach the developer directly at support@kadranname.com.

3. How the app works

3.1. Kadranname is a tool for keeping your watch collection on your phone. There is no account and no sign-in. Everything you enter is kept in the storage the operating system reserves for this app on your phone.

3.2. The developer has no server that collects, stores or sees this data. The app is software that processes your data on your phone under your control; the developer cannot access this data, cannot recover it for you and cannot delete it.

3.3. The app connects to the internet for some tasks. These connections go directly from your phone to the service concerned; there is no intermediary server of the developer in between. Section 5 lists each connection, when it is made and what it carries.

3.4. Ads in the free version are shown through Google's advertising library, which sends data from the phone to Google (section 6). This is the only case in which the app collects data for a party other than you (Google).

4. Data stored on your phone

4.1. The following data is stored only on your phone and does not leave it except in the cases listed in section 5.

DataContentsNote
Collection recordsBrand, model, reference, nickname, movement, style, serial number, status (in collection, sold, wish list), personal note and the watch's story, manufacturer page addressSerial numbers and personal notes may be sensitive
Purchase, sale, service and insurance detailsPurchase date and price, currency, seller, box and papers, warranty end, sale date and price, service records and costs
PhotosWatch photos, wrist photos, dial photosWhen a photo is added, all metadata including location (EXIF, GPS, XMP) is removed; only the time it was taken is read and kept separately
DocumentsInvoices, warranty cards, service forms, insurance documentsA file you pick is stored as it is; its metadata and the personal details in it (for example your name and address on an invoice) are not removed. For documents scanned with the camera, metadata is removed
Wear logWhich watch you wore on which day, the time and time zone of the entry, and, if you choose, that day's wrist photoKeeping wrist photos can be turned off in Settings
MeasurementsResults of accuracy measurements (offset, daily rate, beat rate and beat error, position, method, time)Microphone sound and camera images are not stored (5.9)
Value informationValues you enter, AI estimated price ranges, comparable watches, exchange-rate information
Specifications and historyTechnical specifications of your watches, the history of the model family and the source addresses
FeedAddresses of the blog, YouTube, X, Instagram and shop sources you add; the headlines, links, product names and prices downloadedProduct pictures are not written to disk
AI usage logFor each AI call: time, provider, model, feature and the number of units (tokens) usedSo you can see your cost
SettingsAppearance, language, app lock, reminder time, currency, AI choices, measurement preferences, backup preferences, audio-clock calibration
API keysKeys of AI providers that you enterNot in the database but in the phone's secure storage (the Keychain on iPhone, Keystore-protected storage on Android)
Membership statusWhether you are a member, plan, end of the current period, when the store last confirmed it, and a one-way hash of the purchase identifierRead from the store and kept only on the phone
Ad and consent statusThe record of your ad consent kept by Google's consent tool, the app's launch count, ad frequency counters in the free versionThe launch count is kept for every user (the app open ad is not shown on the first three launches); the others are used only in the free version. None of them is included in backups
Device identifierA random identifier the app creates on first launchOnly to tell which phone wrote a backup; it is not the advertising ID or a hardware identifier

4.2. When you delete the app from your phone, the operating system deletes all data on the phone, including the on-phone backup folder. A possible exception: on iPhone, whether items in secure storage (the Keychain), namely API keys and the Google Drive sign-in session, are deleted together with the app depends on iOS, and the developer cannot guarantee it. To be sure they are deleted, delete the key and disconnect Google Drive in Settings before removing the app. Your cloud backups are not deleted with the app (5.1).

4.3. Android's own automatic backup and device-to-device transfer are turned off for this app: Android does not back the app's data up to your Google account. Data moves from one phone to another only through the app's own backup or zip export.

5. Data that leaves your phone

Each connection below is made because you start something or turn a setting on. As with any internet connection, the other side sees your phone's IP address and the technical details of the connection (time, client type).

5.1. Cloud backup (Google Drive or iCloud)

5.2. Zip export and the share sheet

5.3. AI features (with your own API key)

The AI features are optional and work only if you enter an API key of an account that you opened with an AI provider. The app connects to the provider directly with your key. Every request also carries your key, the model name, fixed instructions, the app's language and today's date.

FeatureWhenWhat is sentTo whom
Specifications, catalogue picture candidates, comparable watchesWhen you tap the buttonBrand, model, the reference if you entered oneAnthropic (Claude)
Model family historyWhen you tap the buttonBrand and model familyAnthropic (Claude)
Estimated price rangeWhen you tap the button; this feature is off by defaultBrand, model, reference, the watch's condition (e.g. "excellent"), box and papers, currency codeAnthropic (Claude)
Asking AI during wrist recognitionIf you turned this option on and the phone is not sure; off by defaultThe wrist photo cropped to the watch, metadata removed, scaled down, and small photos of candidate watches from your collection. No watch names, notes or identifiers are sent; candidates are labelled A, B, CAnthropic (Claude)
Photo enhancementWhen you start it for a photo; off by defaultThe photo you chose (metadata removed, at most 1536 pixels) and a fixed editing instruction; nothing else about the watchThe provider you chose in Settings: OpenAI or Google (Gemini), with a separate key

5.4. Currency conversion

5.5. Network time

5.6. Content feed and shops

5.7. Specifications from a web page

5.8. External links

When you tap a source link, a manufacturer page, an article in the feed, the store's subscription management page or this policy, the link opens in your phone's browser or the relevant app. From then on that site's own privacy policy applies. This policy and the terms of use open on the website from the ABOUT section in Settings; the app adds only the app's language to the link.

5.9. What never leaves your phone

6. Advertising (free version)

6.1. Who: Ads in the free version are shown through AdMob, the advertising service of Google (Google LLC and its affiliates, including Google Ireland Limited for users in Europe; "Google"). The app contains the Google Mobile Ads SDK and Google's consent tool, the User Messaging Platform (UMP).

6.2. Members: If you are a member, neither the advertising library nor the consent tool is started; no ads are requested and the data in this section is not collected. On the app's first launch, neither is started until the store has reported your membership status. In the free version, the consent tool connects to Google at launch to learn which consent message is needed.

6.3. Data Google collects: According to Google's published disclosures, the advertising library sends the following data from the phone to Google for advertising, analytics and fraud prevention:

This data is encrypted in transit (TLS). The app adds nothing from your collection, notes, measurements or photos to ad requests; the app has no location permission.

6.4. Personalised and non-personalised ads: Personalised ads are chosen using what Google knows about you. Non-personalised or limited ads are chosen from context, such as the app and approximate location, not from your past behaviour; for these ads too, Google may process data to cap ad frequency, for reporting and to prevent fraud.

6.5. Consent:

6.6. Changing or withdrawing your choice:

6.7. Google's role: Google processes this data for its own purposes (providing, measuring and improving its advertising services and preventing abuse) as a controller in its own right. Google lists AdMob among the products for which it acts as an independent controller under the data protection terms it publishes for its advertising products (Google Ads Controller-Controller Data Protection Terms). The developer, too, because it places the advertising library in the app and thereby causes the data to be sent to Google, is responsible for that collection and transmission; the developer does not see the data sent to Google and receives only aggregate advertising revenue reports from Google. How Google uses this data: "How Google uses information from sites or apps that use our services": https://policies.google.com/technologies/partner-sites. Google's privacy policy: https://policies.google.com/privacy. Google is the only third party with which the developer causes user data to be shared; under these terms each party undertakes to comply with its obligations under the applicable data protection legislation. Relying on these terms, the developer confirms that Google gives this data the same or equal protection as set out in this policy and in the store rules.

6.8. Users in the United States: In California and other US states with similar rules, sending data to Google for personalised advertising may count as a "sale" or "sharing" of personal information under state law. The developer receives no separate payment from Google for the data the advertising library sends to Google; the developer's revenue comes from ads being shown. The app uses Google's US state privacy message: in the states where it applies, the "Ad privacy choices" row in Settings opens the "Do Not Sell or Share My Personal Information" link; if you choose to opt out there, your choice is communicated to Google. You can also refuse or turn off tracking on iPhone, delete your advertising ID on Android, or become a member.

7. Purchases and membership

7.1. Membership is bought through Apple's in-app purchase system on the App Store and Google's on Google Play. Apple or Google takes the payment; your card details, billing address and store account details do not reach the developer. Apple and Google process this data as controllers in their own right, under their own terms and privacy policies.

7.2. The app reads from the store only the membership products and the status of purchases: which plan, when it renews or ends, whether a purchase still needs to be confirmed. For this, the transaction identifier given by the store (the App Store transaction ID or the Google Play purchase token) is used on the phone; the app keeps only a one-way hash of it to remember the plan. Membership is verified on the phone; this information is not sent to the developer.

7.3. The developer sees the sales, refund and subscription reports the stores give developers. These reports contain information such as order number, product, date, price, transaction status and the buyer's country. On Google Play, for sales in countries where the developer is the merchant of record (including Türkiye; excluding the European Economic Area and the United Kingdom), the reports also contain the buyer's city, state and postcode; Google Play Console also lets an order be searched by the buyer's full e-mail address. The developer uses this information only for accounting, tax, refunds and handling your support request. Order details may also contain other buyer information shown by the store.

8. Permissions

PermissionWhyWhen it is asked
CameraPhotographing watches and your wrist, scanning documents, camera measurementOn first use
Photos (iPhone)Picking photos from your library. On Android the system photo picker is used and no permission is needed; only the photo you pick reaches the appWhen you first open the library
MicrophoneMeasuring a mechanical watch's accuracy from its ticking, audio-clock calibrationAt the first microphone measurement
Motion sensorShowing whether the phone is level when taking a collection photoOn iPhone, on first use
NotificationsDaily reminder and service remindersWhen you turn a reminder on
Face ID, Touch ID, fingerprint, face unlockApp lockWhen you turn the lock on
Tracking (iPhone only, free version only)Sending the advertising identifier to Google (6.5)Within Google's consent flow
Internet and network stateThe connections in section 5; the "back up on Wi-Fi only" optionNot asked (system permission)

The app has no location, contacts, calendar or phone permission. You can revoke permissions at any time in your phone's settings; the feature concerned then stops working and the others continue.

9. App lock and biometrics

If you turn the app lock on, the app asks for your phone's authentication (Face ID, Touch ID, fingerprint, face unlock or the screen-lock passcode) when it opens and when it returns from the background. The phone's operating system performs the check; the app has no access whatsoever to your fingerprint, face or passcode and receives only a "verified" or "not verified" answer. The app therefore does not process biometric data. While the lock is on, the screen content is hidden when the app is in the background. The lock is an access barrier; it does not additionally encrypt the data on the phone.

10. Data the developer itself processes

10.1. Support correspondence: When you write to support@kadranname.com: your e-mail address, your name (if you give it), the content of your message and any attachments. Messages to this address are forwarded to the developer's mailbox by the e-mail routing service of Cloudflare, Inc. and are stored at the e-mail service provider the developer uses.

10.2. Store reports: The sales and subscription reports described in 7.3; and the crash and performance reports the stores give developers where the user allowed this in the device settings (technical information such as the technical record of the error and the type of device). The developer uses these reports only to fix errors and does not try to identify you.

10.3. Advertising reports: The aggregate reports Google gives the developer in AdMob (impressions, revenue, breakdown by country). These reports do not show individual users.

10.4. Website: See section 17.

11. Purposes and legal bases

The processing for which the developer is the controller, and its legal bases:

ProcessingMethod of collectionPurposeKVKKGDPR
Collection of data by the advertising library for personalised ads, and storing or reading information on the deviceAutomatically, electronically from the phone, by the advertising library in the appFunding the free version through advertisingExplicit consent (Art. 5(1))Consent (Art. 6(1)(a)); for storing and reading on the device, Art. 5(3) of the ePrivacy Directive
Delivering limited ads to the device when there is no consent (technical data such as the IP address)Automatically, by the advertising libraryFunding the free version through advertising, preventing ad fraudLegitimate interest (Art. 5(2)(f))Legitimate interests (Art. 6(1)(f)); consent where storing or reading on the device is required
Support correspondenceFrom you, by e-mailAnswering your questions, handling your requests, fixing problemsPerformance of a contract (Art. 5(2)(c)); for data subject requests, legal obligation (Art. 5(2)(ç)); otherwise legitimate interest (Art. 5(2)(f))Contract (Art. 6(1)(b)), legal obligation (Art. 6(1)(c)), legitimate interests (Art. 6(1)(f))
Store sales and subscription reportsFrom Apple and Google, through the developer consolesAccounting, tax obligations, refunds and disputesLegal obligation (Art. 5(2)(ç)); performance of a contract (Art. 5(2)(c)); establishing, exercising or defending a right (Art. 5(2)(e))Legal obligation (Art. 6(1)(c)), contract (Art. 6(1)(b)), legitimate interests (Art. 6(1)(f))
Crash and performance reportsFrom Apple and Google, through the developer consolesFixing errorsLegitimate interest (Art. 5(2)(f))Legitimate interests (Art. 6(1)(f))
Hosting the website and server logsAutomatically, from your browser when you open the site, through the hosting providerServing the site, keeping it secureLegitimate interest (Art. 5(2)(f))Legitimate interests (Art. 6(1)(f))

Data processed on your phone under your control (section 4) and data that goes directly to third parties through connections you start (section 5) does not reach the developer. To the extent the developer is considered a controller of this processing, the legal basis is providing the function you asked for, that is, entering into and performing the contract (KVKK Art. 5(2)(c), GDPR Art. 6(1)(b)). The app is not designed to process special categories of personal data (health, biometric data and the like). If you write such information in your notes or documents, it too stays only on your phone and in the backup you choose.

12. International transfers

12.1. The developer is in Türkiye. The following recipients process data outside Türkiye, in particular in the United States and the European Union, in the countries where their servers are located:

RecipientWhich dataPurposeWho sends it
Google (advertising)The data in 6.3Showing and measuring ads, preventing fraud (section 6)The advertising library in the free version
Cloudflare (e-mail routing, website hosting)Support e-mails; server logs of website visitsForwarding your e-mail to the developer; serving and protecting the siteWhen you write an e-mail or open the site
The developer's e-mail service providerSupport e-mailsStoring the correspondenceThrough Cloudflare's forwarding
Apple, Google (stores)Purchase and store account dataHandling the sale and paymentThe store, as part of its own service
Google, Apple (cloud backup)Your backupsKeeping your backups in your accountThe app, through the backup setting you turned on, to your account
AI provider (Anthropic, OpenAI or Google)The data in 5.3Producing the AI answer you asked forThe app, at your request, with your key

12.2. Cloud backup, AI and feed connections go directly from your phone to your own account or to a service you chose, through an action you start; the developer does not receive this data and does not pass it on or make it accessible to anyone. According to the Turkish Personal Data Protection Board's guide on transfers abroad, such cases, in which the data subject sends the data directly, are not a "transfer" by the developer within the meaning of KVKK Art. 9; the receiving company's own processing is governed by the applicable law.

12.3. For data whose transfer the developer causes as a controller (advertising, support e-mails, website), the safeguards the recipients provide are:

13. Retention

DataPeriod
Data on the phoneUntil you delete it. A watch you delete first goes to "Deleted watches" and can be brought back from there; permanent deletion is done there, with your confirmation. When you remove the app, the data on the phone is deleted (including the exception in 4.2)
Cloud backupsUntil you delete them. The app keeps the last 10 database copies and deletes older ones itself; photos you delete in the app stay in the backup folder for 30 more days and are then deleted. Removing the app does not delete the cloud backup
Zip and PDF filesWhere you put them, until you delete them
Support correspondence2 years after the last message, then deleted; if a legal claim or dispute requires longer, until it is resolved
Store sales reportsFor the retention period required by tax and commercial law
Advertising dataNot kept by the developer; Google keeps it under its own retention rules (https://policies.google.com/technologies/retention)
Data sent to the AI providerNot kept by the developer; the period in the provider's contract with you

14. Security and its limits

14.1. Measures in the app:

14.2. Limits you should know about:

15. Your rights

15.1. Under KVKK Art. 11 you may apply to the developer to: learn whether your personal data is processed; request information about it if so; learn the purpose of processing and whether data is used in line with that purpose; know the third parties in Türkiye or abroad to whom it is transferred; request correction of incomplete or inaccurate data; request erasure or destruction under the conditions of KVKK Art. 7; request that correction and erasure be notified to third parties to whom the data was transferred; object to a result to your detriment arising from analysis exclusively by automated systems; and claim compensation for damage arising from unlawful processing.

15.2. If you are in the European Economic Area or the United Kingdom, under GDPR Arts. 15–22 you have the rights of access, rectification, erasure, restriction of processing, data portability and objection; the right to withdraw consent for processing based on consent (processing before withdrawal remains lawful); and rights relating to automated decisions. The app makes no automated decisions about you and builds no profile; you can object to Google's profiling for advertising in the ways listed in 6.6.

15.3. How to exercise these rights:

15.4. Complaints: Under KVKK you must first apply to the developer. If your application is rejected, the answer is found insufficient or no answer is given in time, you may complain to the Personal Data Protection Board (https://www.kvkk.gov.tr) within 30 days of learning the answer and in any case within 60 days of the application. If you are in the European Economic Area you may complain to the data protection authority where you live, work or where you think the infringement took place; in the United Kingdom, to the Information Commissioner's Office (ICO).

16. Children

16.1. Kadranname is offered to people aged 16 and over; the stores are told that its target audience is 16 and over. The app is not directed at children.

16.2. The app does not ask for age and does not know the user's age. If you are under 16, do not use the app. If you are under 18, buy a membership or give consent for advertising only with your parent's or guardian's permission. The AI providers' terms also set their own age limits (for example 18 for Google's Gemini API). If we learn that a child has sent personal data to the developer, we will delete it; you can write to support@kadranname.com for this.

17. Website

17.1. kadranname.com is a site for presenting the app and providing information. The site uses no cookies and contains no visitor analytics or advertising tools. It loads all its files, fonts included, from its own address; its security settings do not allow scripts, images or fonts to be loaded from other sites. When you choose a language on the site, your choice is kept only in your browser's local storage (kadranname.lang) and is not sent to the server; you can remove it by clearing your browser's data for this site.

17.2. The site is hosted by Cloudflare, Inc. As with any website, the hosting provider processes your IP address, the time of the request, the page requested and the technical information your browser sends (such as the browser type) to deliver the page to you and to protect against attacks, and may keep these in logs for a short time. In the data processing addendum that is part of its customer agreement, Cloudflare states that it does this on its customer's behalf, as a processor.

18. Changes

18.1. If the way the app processes data changes, this policy is updated. The new text is published at this address with a new version number and effective date.

18.2. If a change significantly affects the processing of your data (for example a new recipient or a new type of data), it is announced in the app or in the store release notes before it takes effect. For new processing based on consent, your consent is asked for separately.

18.3. Previous versions are sent on request from support@kadranname.com.

19. Language

This policy is published in Turkish and English. If the two texts conflict, the Turkish text prevails; however, if the mandatory law of your country gives you the right to rely on a text in your own language or on the English text, that right is not affected.