Privacy
Kadranname Privacy Policy and Personal Data Notice
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.
- No account, no server. You do not create an account in Kadranname. The developer has no server that receives or stores what you enter in the app. Your watches, photos, wear log, measurements and documents stay on your phone; the developer cannot see them.
- Data leaves your phone only through things you start: backups to your own Google Drive or iCloud, AI queries with your own API key, the feed sources you add, exchange-rate and network-time requests. The full list is in section 5.
- The free version shows ads from Google. Google's advertising library sends data such as the advertising ID, IP address, device information and ad interactions to Google. Nothing from your collection is added to ad requests. If you are a member, the advertising library is never started.
- Your payment details never reach the developer. Membership is bought through the App Store or Google Play.
- The only personal data the developer holds are the e-mails you send and the sales and crash reports the stores give developers.
- Your rights and how to exercise them are in section 15.
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.
| Data | Contents | Note |
|---|---|---|
| Collection records | Brand, model, reference, nickname, movement, style, serial number, status (in collection, sold, wish list), personal note and the watch's story, manufacturer page address | Serial numbers and personal notes may be sensitive |
| Purchase, sale, service and insurance details | Purchase date and price, currency, seller, box and papers, warranty end, sale date and price, service records and costs | |
| Photos | Watch photos, wrist photos, dial photos | When a photo is added, all metadata including location (EXIF, GPS, XMP) is removed; only the time it was taken is read and kept separately |
| Documents | Invoices, warranty cards, service forms, insurance documents | A 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 log | Which watch you wore on which day, the time and time zone of the entry, and, if you choose, that day's wrist photo | Keeping wrist photos can be turned off in Settings |
| Measurements | Results 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 information | Values you enter, AI estimated price ranges, comparable watches, exchange-rate information | |
| Specifications and history | Technical specifications of your watches, the history of the model family and the source addresses | |
| Feed | Addresses of the blog, YouTube, X, Instagram and shop sources you add; the headlines, links, product names and prices downloaded | Product pictures are not written to disk |
| AI usage log | For each AI call: time, provider, model, feature and the number of units (tokens) used | So you can see your cost |
| Settings | Appearance, language, app lock, reminder time, currency, AI choices, measurement preferences, backup preferences, audio-clock calibration | |
| API keys | Keys of AI providers that you enter | Not in the database but in the phone's secure storage (the Keychain on iPhone, Keystore-protected storage on Android) |
| Membership status | Whether you are a member, plan, end of the current period, when the store last confirmed it, and a one-way hash of the purchase identifier | Read from the store and kept only on the phone |
| Ad and consent status | The record of your ad consent kept by Google's consent tool, the app's launch count, ad frequency counters in the free version | The 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 identifier | A random identifier the app creates on first launch | Only 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)
- When: When you turn cloud backup on and afterwards when the app opens or comes back to the foreground (at most once an hour), and when you start a backup yourself. The app does not back up in the background on its own. Cloud backup is available to members; restoring from an existing cloud backup is available to everyone.
- What: Your database (the records in 4.1), your photos, documents, settings and API keys. Membership status, ad and consent status and settings that belong only to this phone (such as the backup target and the cloud connection) are not included.
- Where: A folder named "Kadranname" in your own Google Drive or iCloud Drive. On Google Drive the app asks for a narrow permission (
drive.file) that lets it reach only the files it created; it cannot see your other Drive files. The app does not read or store your Google account's name or e-mail address; on iPhone, however, Google's sign-in library keeps the account details in the phone's Keychain to maintain the session. - Who processes it: Google or Apple, as the provider of the cloud storage service, under their contract with you and their own privacy policies. The developer has no access to these accounts or the folder.
- What you should know: Backups are not encrypted. The database and photos in the folder can be read by anyone who can access your Google or Apple account, and your API keys are in these backups in plain text. The security of your backups depends on the security of your Google or Apple account; we recommend two-step verification.
- On-phone backup: You can also back up to the app's own storage on the phone instead of the cloud. This backup does not leave the phone and is deleted with the app.
5.2. Zip export and the share sheet
- The zip file you create in Settings contains your records (CSV and JSON), photos, documents and settings; it does not contain API keys. The zip file is not encrypted.
- The PDF collection inventory contains a summary of the collection and, for each watch, its photo, serial number, specifications, history, measurement and service history, the list of its documents, purchase details and value.
- Sharing (journal pictures and photos), the PDF file of a single watch and the PDF inventory of the collection are membership features; the zip export is available to everyone. The PDF file of a single watch may contain that watch's details, photo, measurement and service history and documents. Shared files are temporary copies prepared for the share sheet and are deleted after the sheet closes; the app uploads them nowhere.
- These files, and photos you share, leave the phone only to the place you pick in the phone's share sheet (an app, a person, a folder). What happens there depends on that party.
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.
| Feature | When | What is sent | To whom |
|---|---|---|---|
| Specifications, catalogue picture candidates, comparable watches | When you tap the button | Brand, model, the reference if you entered one | Anthropic (Claude) |
| Model family history | When you tap the button | Brand and model family | Anthropic (Claude) |
| Estimated price range | When you tap the button; this feature is off by default | Brand, model, reference, the watch's condition (e.g. "excellent"), box and papers, currency code | Anthropic (Claude) |
| Asking AI during wrist recognition | If you turned this option on and the phone is not sure; off by default | The 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, C | Anthropic (Claude) |
| Photo enhancement | When you start it for a photo; off by default | The photo you chose (metadata removed, at most 1536 pixels) and a fixed editing instruction; nothing else about the watch | The provider you chose in Settings: OpenAI or Google (Gemini), with a separate key |
- Before sending, the app checks every photo meant for an AI provider; an image that carries metadata or exceeds the limits is not sent.
- For specifications, history, price and comparables, the provider searches the web and reads web pages to find the answer. These searches are made from the provider's servers.
- When you choose one of the catalogue picture candidates, the app downloads that picture directly from the site that hosts it (usually the manufacturer's or a retailer's site).
- When you send a photo to another app through "Share" (5.2), a copy with its metadata removed is sent; you choose where it goes.
- Information first: The first time you use an AI feature, the app shows what will be sent, what will not be sent and to which provider; sending happens only when you continue.
- The provider's role: You choose the AI provider, you open the API account, you enter into the contract and you pay for it. The data sent is processed under the provider's contract with you and its privacy terms. The developer does not see this data, has no contract with the provider on your behalf and gives the provider no instructions. According to the providers' terms (as of 18 November 2026):
- Under Anthropic's data processing addendum, the API customer (that is, you as the key holder) is the controller and Anthropic is the processor; Anthropic does not train its models on API data and as a rule deletes inputs and outputs within 30 days.
- OpenAI states that it does not use data sent to its API to train its models unless you explicitly opt in, and that it keeps logs for up to 30 days for abuse monitoring.
- On Google's Gemini API, for unpaid use Google uses the content you submit and the responses to improve its products and models, and humans may read them; for paid use (a key tied to a Google Cloud project with billing) it does not. For users in the European Economic Area, Switzerland and the United Kingdom the paid-use terms always apply. If you choose Google for photo enhancement, we recommend a billed key.
- The provider may change these terms; what applies is the provider's current contract with you.
- A wrist photo does not show your face but may show your skin, a tattoo or clothing. These photos are not used to identify you; the app compares a wrist photo only to find which watch is being worn, on the phone and (if you turned the option on) at the provider.
5.4. Currency conversion
- When: When an amount in another currency is converted on the value screen or in the collection total. PDF files only use rates already on the phone; they fetch none.
- What: Only a date and currency codes. No amounts and no watch details.
- Where: The Frankfurter exchange-rate service (
api.frankfurter.dev; European Central Bank rates).
5.5. Network time
- When: When a measurement method, the watch-setting screen or the wrist photo flow is opened, and during audio-clock calibration.
- What: Only a standard time request (NTP). It carries nothing about you or your watches. This protocol is not encrypted.
- Where: Public time servers:
time.google.com(Google),time.cloudflare.com(Cloudflare),pool.ntp.org(servers run by volunteers).
5.6. Content feed and shops
- When: When you add a source; when you open the Feed tab (each source at most once every 15 minutes) and when you pull to refresh.
- What: An ordinary request to the feed address of the blog, YouTube channel or shop site you added. When a shop is added, a few well-known product feed addresses on the same site are also tried. Product pictures are downloaded from the server that hosts them (usually the shop's content server). No cookies or information identifying you are added to these requests.
- Where: Only the sites you added. The six suggested blogs are not followed unless you tap to add them.
- X and Instagram: The app never sends requests to these two sites; when you tap an account you added, the link opens in that app or in your browser.
5.7. Specifications from a web page
- When: When you paste the address of a product page and tap "Fetch from page".
- What: Only a request to that address; nothing about you or your watch is added and no cookies are sent.
- Where: The site at that address.
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
- Microphone measurement: The watch's sound is processed on the phone, in memory; it is not recorded, not written to a file and not sent anywhere. Only the measurement result is stored.
- Camera and photo measurement: The dial image is read on the phone; no video is recorded and no image is sent.
- Wrist recognition: By default it runs entirely on the phone, with a model built into the app.
- Reminders: Notifications are scheduled on the phone; they are not sent from a server. The notification text may be visible on the lock screen.
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:
- the device's IP address (which may also be used to estimate general location);
- device and account identifiers: on Android the advertising ID, the app set ID and, if applicable, other identifiers related to accounts signed in on the device; on iPhone the advertising identifier (IDFA) if you allowed it, and identifiers scoped to the app or the developer;
- advertising data and product interactions: ads shown, taps, video views, app launches;
- diagnostic and performance data: app launch time, hang rate, energy use, crash logs;
- approximate location derived from the IP address.
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:
- In the free version, wherever you are (including Türkiye, the European Economic Area, the United Kingdom and Switzerland), Google's consent message is shown. It opens not during a measurement, while the camera is in use or while you fill in a form, but at a calm moment of the app (on the first page of the Collection, Journal or Feed tab, with no other window over it). The advertising library is not started and no ad is requested until your choice has been recorded.
- The app requests personalised ads only if your recorded consent covers personalised advertising and, on iPhone, you have also allowed tracking; in every other case it adds Google's non-personalised ads signal to the ad request. Storing or reading information on your device for advertising takes place only for the purposes you consented to. If you do not consent, non-personalised or limited ads are shown: with limited ads, personal data is not collected or used to personalise ads; data such as the IP address is still used to deliver the ad to your device. If you do not want these either, the only way is membership.
- Your choice on the consent screen does not depend on accepting the terms of use or this policy; refusing does not restrict any feature of the app.
- On iPhone, your advertising identifier (IDFA) is sent to Google only if you answer "Allow" to iOS's "Allow to track" question. If you do not allow it, or if you turned off apps' requests to track in iOS settings, the advertising identifier is not sent. This question is asked within Google's consent flow after a short explanation.
6.6. Changing or withdrawing your choice:
- If the consent message was shown to you, you can open it again at any time from the "Ad privacy choices" row on the app's Settings page and change or withdraw your choice. The row appears when Google's consent tool considers it necessary. When you withdraw consent, ads already loaded are discarded.
- Android: In Settings, Privacy (or Google), Ads, you can reset or delete your advertising ID.
- iPhone: In Settings, Privacy & Security, Tracking, you can turn off tracking for Kadranname or for all apps; Settings, Privacy & Security, Apple Advertising manages Apple's own ads.
- You can manage the information Google uses for ads about you in My Ad Center in your Google account (
myadcenter.google.com). - The most certain way is membership: with membership the advertising library never runs.
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
| Permission | Why | When it is asked |
|---|---|---|
| Camera | Photographing watches and your wrist, scanning documents, camera measurement | On 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 app | When you first open the library |
| Microphone | Measuring a mechanical watch's accuracy from its ticking, audio-clock calibration | At the first microphone measurement |
| Motion sensor | Showing whether the phone is level when taking a collection photo | On iPhone, on first use |
| Notifications | Daily reminder and service reminders | When you turn a reminder on |
| Face ID, Touch ID, fingerprint, face unlock | App lock | When 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 state | The connections in section 5; the "back up on Wi-Fi only" option | Not 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:
| Processing | Method of collection | Purpose | KVKK | GDPR |
|---|---|---|---|---|
| Collection of data by the advertising library for personalised ads, and storing or reading information on the device | Automatically, electronically from the phone, by the advertising library in the app | Funding the free version through advertising | Explicit 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 library | Funding the free version through advertising, preventing ad fraud | Legitimate interest (Art. 5(2)(f)) | Legitimate interests (Art. 6(1)(f)); consent where storing or reading on the device is required |
| Support correspondence | From you, by e-mail | Answering your questions, handling your requests, fixing problems | Performance 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 reports | From Apple and Google, through the developer consoles | Accounting, tax obligations, refunds and disputes | Legal 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 reports | From Apple and Google, through the developer consoles | Fixing errors | Legitimate interest (Art. 5(2)(f)) | Legitimate interests (Art. 6(1)(f)) |
| Hosting the website and server logs | Automatically, from your browser when you open the site, through the hosting provider | Serving the site, keeping it secure | Legitimate 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:
| Recipient | Which data | Purpose | Who sends it |
|---|---|---|---|
| Google (advertising) | The data in 6.3 | Showing 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 visits | Forwarding your e-mail to the developer; serving and protecting the site | When you write an e-mail or open the site |
| The developer's e-mail service provider | Support e-mails | Storing the correspondence | Through Cloudflare's forwarding |
| Apple, Google (stores) | Purchase and store account data | Handling the sale and payment | The store, as part of its own service |
| Google, Apple (cloud backup) | Your backups | Keeping your backups in your account | The app, through the backup setting you turned on, to your account |
| AI provider (Anthropic, OpenAI or Google) | The data in 5.3 | Producing the AI answer you asked for | The 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:
- for users in the European Economic Area and the United Kingdom: under Google's advertising data protection terms, data of users in the EEA and Switzerland goes to Google Ireland Limited in the European Union; for transfers from the United Kingdom to Google LLC, the standard contractual clauses in those terms apply. Cloudflare's data processing addendum, which is part of its customer agreement, relies for transfers on the European Commission's standard contractual clauses, the UK addendum and the EU-US Data Privacy Framework (GDPR Arts. 45 and 46(2)(c)). These terms are published on Google's (https://business.safety.google/adscontrollerterms/) and Cloudflare's (https://www.cloudflare.com/cloudflare-customer-dpa/) sites;
- for users in Türkiye: the data goes to the same recipients under the same terms.
13. Retention
| Data | Period |
|---|---|
| Data on the phone | Until 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 backups | Until 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 files | Where you put them, until you delete them |
| Support correspondence | 2 years after the last message, then deleted; if a legal claim or dispute requires longer, until it is resolved |
| Store sales reports | For the retention period required by tax and commercial law |
| Advertising data | Not kept by the developer; Google keeps it under its own retention rules (https://policies.google.com/technologies/retention) |
| Data sent to the AI provider | Not kept by the developer; the period in the provider's contract with you |
14. Security and its limits
14.1. Measures in the app:
- Data is kept in the area the operating system reserves for this app, which other apps cannot access.
- API keys are kept in the phone's secure storage (on iPhone a Keychain item bound to this device only, on Android Keystore-protected storage).
- Optional app lock, and hiding the content in the app switcher while the lock is on.
- Android's automatic backup and device-to-device transfer are turned off.
- Metadata including location is removed when photos are added; images to be sent to AI are checked before sending.
- Connections for AI, backup, exchange rates, feeds and web pages use HTTPS encryption; plain
httpaddresses in feed and page requests are switched to HTTPS. The network time request (NTP) is not encrypted but carries no personal information.
14.2. Limits you should know about:
- The database on the phone is not encrypted beyond the operating system's device encryption. Someone who can unlock your phone can see your collection if the app lock is off.
- Cloud backups, the on-phone backup and zip export files are not encrypted. Cloud and on-phone backups contain your API keys in plain text. Protecting these files and your accounts is in your hands.
- No system is perfectly secure. Keep your phone updated, use a screen lock, turn on two-step verification for your Google and Apple accounts, and set a spending limit for your API key in your provider's console.
- Because the developer has no server, there is no risk of data leaking from a database held by the developer; however, the developer cannot detect a breach on your phone, in your backups or at third-party services. If the developer learns of a breach concerning the data it processes itself (section 10), it will make the notifications required by law.
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:
- You already hold all the data on your phone: in the app you can view it, correct it, export it as a zip (portability) and delete it item by item or entirely by removing the app. You can delete your cloud backups from the "Kadranname" folder in your own Google Drive or iCloud account. Because the developer does not hold this data, the developer cannot carry out a request concerning it; this does not limit your rights, it lets you exercise them directly.
- For advertising data: you can withdraw consent in the ways listed in 6.6; for requests about data held by Google you can contact Google (https://policies.google.com/privacy, "Exporting and deleting your information"). Because advertising data is not given to the developer linked to individual users, the developer cannot provide it to you, but will help you direct your request.
- For data sent to the AI provider, Apple and Google, contact the company concerned through your account with it.
- For data the developer processes (section 10), you make your requests by e-mail to support@kadranname.com; the developer offers no other channel (no form and no postal address). Under the Communiqué on the Procedures and Principles of Application to the Data Controller, an application by e-mail is made from an e-mail address you previously notified to the developer and that is in the developer's records; an address from which you have written to the developer before counts as recorded, and if you are writing for the first time the developer records your address and processes your application. Applications made through registered electronic mail (KEP), with a secure electronic signature or mobile signature can be sent to the same address. In your application state your name and surname, your Turkish identity number if you are a Turkish citizen or your nationality and passport or identity number if you are not, your address of residence or work for notification, your e-mail address for notification, your telephone number if any, and the subject of your request. If you are outside Türkiye and apply under the GDPR, writing your request in the e-mail is enough. The developer asks only for the information needed to verify your identity.
- An application under KVKK is concluded free of charge within 30 days at the latest, and the answer is given to you in writing or electronically. If the answer is given on paper, there is no charge up to ten pages; for each page above ten the processing fee in the Communiqué, or, if the answer is given on a storage medium, the cost of the medium, may be charged. Requests under the GDPR are answered within one month; where the complexity or number of requests requires, this period may be extended by two further months, and you will be told so, with the reasons, within the first month.
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.