Skip to main content
KiwiCall
FeaturesEditionsWhy KiwiCall?Feature Guide
ENDEJA
Google Play
← Back to Home

Privacy Policy

Information pursuant to Art. 13 and 14 GDPR — last updated 6 November 2026

1. Two editions — read the section that applies to you

This policy covers two separate Android applications published by KiwiCanopy. They differ in exactly one respect that matters for your privacy, and this document does not blur that difference.

KiwiCall, the paid edition:

  • Package name: com.kiwicanopy.kiwicall
  • Price: paid, one-off purchase
  • Advertising: none
  • Internet permission: absent from the app
  • The section that applies to you: section 4

KiwiCall Lite, the free edition:

  • Package name: com.kiwicanopy.kiwicall.lite
  • Price: free
  • Advertising: yes, Google AdMob
  • Internet permission: declared, required by the advertising SDK
  • The section that applies to you: section 5

Which edition you have is written on the app itself: the paid edition is named KiwiCall and the free one KiwiCall Lite, on your home screen and in Android under Settings → Apps. The package name is shown on the Google Play listing.

2. Controller

Responsible for data processing within the meaning of Art. 4(7) GDPR:

Maikel Hajiabadi — KiwiCanopy

Moselstraße 43

60329 Frankfurt am Main

Germany

Email: [email protected]

Website: https://kiwicall.kiwicanopy.com

A data protection officer has not been appointed, as the conditions of Art. 37 GDPR and § 38 BDSG are not met.

We are established in Germany, so the GDPR and the TDDDG govern our processing for every user of these apps, wherever you are. That is why KiwiCall Lite asks you for consent to advertising, and why the safeguards described below apply to you wherever you are.

3. What both editions do on your device

Both editions are dialers. To work, they handle:

  • telephone numbers you enter, dial or schedule;
  • your call history within the app, including attempt counts, durations and outcomes;
  • your call schedules, including recurrence rules and archived entries;
  • contact names, numbers and photos, read from your device's contact store to suggest contacts as you type a number, to show who a number belongs to wherever the app shows one, and to list and search your contacts, favorites first, in the app's contact sheet and fill in a number from it; the name shown for a call — from your contacts, or the caller name your network supplies — is kept with it in the app's call history, and a schedule you create from a contact is titled with its name;
  • entries from Android's own call log, read so that the history screen and the recent calls on the dial pad also show calls made or received outside the app and so that the dial pad's contact suggestions list the people you called recently first, and — for missed calls only — marked as read once you open the call history; calls you select and delete on the history screen are deleted from it;
  • Android's own list of blocked numbers, read to show it on the Blocked numbers page and to tell whether a caller is blocked, and changed only when you block or unblock a number in the app; Android keeps this list on your device, not in the app's database, so it applies to every phone app and stays after you uninstall the app — you can manage it in your default phone app's settings;
  • SIM and subscription information, used to route a call over the SIM you chose.

All of this is processed exclusively on your device. What the app keeps itself lives in its private SQLite database inside its protected app sandbox; Android's call log, your contacts and Android's list of blocked numbers stay where Android keeps them. None of it is transmitted to us, and we have no access to it at any time — not in either edition, not with advertising enabled, not under any circumstances. We cannot read your call history because it never reaches us.

You can erase the call history the app itself stores at any time: open the Call History screen and use “Clear History”. Clear History leaves entries from Android's own call log in place. The app changes two things about those entries: it marks missed entries as read, as described under Android permissions below, and calls you select and delete on the Call History screen are deleted from the app and from Android's call log. The app deletes no other entries. Uninstalling the app removes its database with it. Numbers you blocked stay on Android's list of blocked numbers until you unblock them, in the app or in your default phone app's settings.

Neither edition puts any of this into Android's cloud backup. The app's data extraction rules exclude everything from cloud backup, so no copy of your database or of your settings is written to a backup server. Android's direct device-to-device transfer does carry the app's database and your settings when you move to a new phone — that transfer runs from the one device to the other and not through a server.

If you move from KiwiCall Lite to the paid edition, the paid app can read KiwiCall Lite's schedules and in-app call history once — when you accept the offer it shows you. That copy is made on the device, between the two apps, and only when both apps are verifiably ours, checked by their signing certificates. Nothing is transmitted.

4. KiwiCall (paid edition) — no network capability at all

This section applies to com.kiwicanopy.kiwicall.

The paid edition of KiwiCall does not declare the Android permission android.permission.INTERNET. Without that permission the Android operating system refuses the app any network connection at all. The consequence is not a promise we ask you to trust — it is a property of the app that you can check for yourself:

  • The app is technically incapable of transmitting any data to any server, ours or anyone else's.
  • It contains no advertising SDK, no analytics SDK, no crash reporting and no tracking technology of any kind — no Firebase, no Google Analytics, no Sentry, no AdMob.
  • No advertising identifier is read, used or transmitted. The app does not declare the com.google.android.gms.permission.AD_ID permission.
  • There is no user account, no registration and no cloud synchronisation.

You can verify the absence of the internet permission yourself in the Google Play listing under App permissions → See more, or with any APK analysis tool. We check it on every commit to the app's source code: an automated gate builds the merged manifest of both editions and rejects the commit if the paid edition declares the permission — or if KiwiCall Lite has lost it.

Accordingly, no personal data is collected, transmitted or shared by us through the paid edition of KiwiCall. One thing does happen on the device, and only at your request: if you upgrade from KiwiCall Lite, the paid edition can read its schedules and call history once, as section 3 describes — that copy never leaves the phone. Sections 5.1 to 5.7 do not apply to it.

5. KiwiCall Lite (free edition) — advertising

This section applies to com.kiwicanopy.kiwicall.lite.

KiwiCall Lite is financed by advertising and therefore declares android.permission.INTERNET. Everything stated in section 3 remains true: your call history, your contacts, your schedules and the numbers you dial stay on your device and are never transmitted, not to us and not to any advertising partner. What an advertising partner may infer about your calls from which advertisements are requested and shown, and when, is described in section 5.2 — for example when a redial runs, roughly for how long, and that you stopped one that had not connected. Sections 5.1 to 5.7 concern only the data the advertising SDK processes.

5.1 Advertising partner

KiwiCall Lite integrates the Google Mobile Ads SDK (AdMob).

Provider for users in the EEA, the United Kingdom and Switzerland: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.

Google's privacy policy: https://policies.google.com/privacy

How Google uses information collected from apps that use its services: https://policies.google.com/technologies/partner-sites

Where you have consented to them, additional advertising partners (vendors under the IAB Transparency and Consent Framework) may also receive data. The complete and current list of those partners is shown to you in the consent dialog and can be reopened at any time under Settings → Advertising and privacy options.

5.2 Data the advertising SDK processes

  • Device identifiers — the Android Advertising ID, a resettable identifier assigned by your device; it is read, and used to deliver, cap and measure advertising and to prevent abuse, only after you have consented to storage on your device (sections 5.3 and 5.4) — without that consent the advertising SDK is not started at all; the app set ID, an identifier shared by apps from the same developer on your device; and, where applicable, identifiers related to accounts signed in on the device.
  • IP address and the approximate location derived from it — at the level of a region or a city. KiwiCall Lite requests no location permission and does not access GPS or any precise location.
  • Device and app information — device model, operating system version, app version, the app's identifier, language and region settings.
  • Interaction data — when the app is launched, which advertisements were displayed, for how long, and whether they were tapped or played. While a KiwiCall redial runs, its screen shows a banner, so Google may be able to infer when a redial runs, roughly for how long, and how it ended. The full-screen advertisement is shown only when you stop a KiwiCall redial that has not connected, so Google can tell that this happened, and when. Neither reveals the number, the contact, or anything else about the call beyond this.
  • Diagnostic information — technical performance data about the advertising SDK in the app, such as how long the app takes to start, whether it stops responding, and energy use.

Never processed for advertising, in any form: your telephone numbers, your contacts, your call history, your call schedules, the content of any call, or any message text. What the timing of advertisements can reveal about your calls is described above.

5.3 Purposes and legal bases

Advertising has to clear two separate requirements, and they are not the same one. Reading anything from your device or storing anything on it needs your consent under § 25(1) TDDDG, unless it is strictly necessary (§ 25(2) TDDDG). Processing the data that results needs a legal basis under Art. 6 GDPR. The first two entries below are the first requirement; every use of your advertising identifier for advertising depends on the first.

  • Storing information on your device and reading it for advertising, where you have consented (advertising identifier, ad SDK storage) — your consent, § 25(1) TDDDG.
  • What is stored on or read from your device whether or not you have consented: the record of your consent decision (section 5.6) and the app's own reading of that record to honour it, and the device and app information read to check your consent status or to load the consent form (last entry below). We rely on § 25(2) no. 2 TDDDG for this, on the basis that it is necessary to ask for and record your choice. If you refuse consent to storage on your device, the advertising SDK is not started, so nothing else is stored on or read from your device for advertising (section 5.4). Once you have consented, what the advertising SDK stores and reads to operate — including the cookies and local storage it uses to detect invalid traffic and advertising fraud, and identifiers such as the app set ID and the advertising identifier — rests on that consent (first entry). The paid edition (section 5.7) stores and reads nothing for advertising. The processing that follows is set out in the entries below.
  • Delivering advertisements, frequency capping and measuring advertising performance, where you have consented to these purposes — your consent, Art. 6(1)(a) GDPR.
  • Delivering advertisements, frequency capping and measuring advertising performance where you have consented to storage on your device but not to these purposes, together with selecting basic advertising, selecting content using limited data, and audience statistics — the legitimate interest of the controller in financing the free edition through advertising, and of Google and its advertising partners in operating the advertising system, Art. 6(1)(f) GDPR. Where you have consented to storage on your device but not to personalised advertising, your advertising identifier is read and transmitted under that consent (first entry) and may be used for frequency capping, aggregated measurement and abuse prevention, but not to personalise advertising. What is stored on or read from your device is described in the second entry, and what may be transmitted is set out in section 5.2. You can object to each of these purposes separately under “Manage options” in the consent form, Art. 21 GDPR; you can avoid this processing entirely with the paid edition (section 5.7).
  • Personalised advertising, where you have consented to it — your consent, Art. 6(1)(a) GDPR.
  • Measuring the performance of the advertising SDK and developing and improving Google's services, and those of the advertising partners you have consented to, using the interaction data and diagnostic information in section 5.2, whenever the advertising SDK runs, which is only after you have consented to storage on your device — for Google, its legitimate interest in an advertising system that works and improves, Art. 6(1)(f) GDPR; for partners you have consented to, the basis each declares in the consent form, either your consent (Art. 6(1)(a) GDPR) or its legitimate interest (Art. 6(1)(f) GDPR). You can object under “Manage options” in the consent form, Art. 21 GDPR; you can avoid this processing entirely with the paid edition (section 5.7).
  • Detecting invalid traffic and advertising fraud, and keeping the advertising system secure — the legitimate interests of the controller and of the advertising partner in the integrity of the advertising system, Art. 6(1)(f) GDPR.
  • Checking your consent status with Google's consent management platform each time the app is opened, and loading the consent form — before you have made a choice, whenever you reopen it under Settings → Advertising and privacy options, and when Google asks you to renew your choice. Each of these requests transmits your IP address, the app's identifier and basic device information such as the model, Android version and language (section 5.4) — our legitimate interest in obtaining a valid consent choice, keeping it current, and letting you change or withdraw it as easily as you gave it, Art. 6(1)(f) GDPR. Consent cannot be the basis for asking for consent.

Where advertising partners process this data for their own purposes, they act as independent controllers for that processing. Their own privacy policies then apply in addition to this one, and you can reach them through the consent dialog.

5.4 Consent, and how to withdraw it

Before the first advertisement is requested, KiwiCall Lite presents you with a consent dialog through a Google-certified consent management platform (Google's User Messaging Platform) under the IAB Transparency and Consent Framework. Loading the consent form, and the check of your consent status the app makes each time it is opened, transmit your IP address, the app's identifier and basic device information; that is our legitimate interest in obtaining a valid consent choice and keeping it current (Art. 6(1)(f) GDPR; section 5.3). No advertising is requested and no advertising identifier is read before you have made a choice.

If you refuse consent to storage on your device, KiwiCall Lite does not start the advertising SDK: no advertising is requested, and nothing is stored on or read from your device for advertising apart from the record of your choice (section 5.3). Because KiwiCall Lite is financed by advertising, it then stays locked: its screens show a notice that lets you reopen the consent form, get the paid edition, which carries no advertising at all (section 5.7), or choose another phone app in Android's settings. Calls are never locked — incoming calls, the in-call screen, calls another app places directly, and emergency calls keep working; a number another app only opens in the dialer shows the lock. Schedules you created before refusing keep firing, without advertising. If you consent to storage on your device but not to personalised advertising, you see non-personalised advertising: your advertising identifier is then read and transmitted and may be used for frequency capping, aggregated measurement and abuse prevention, but not to personalise advertising (section 5.3). This describes the case where you have not objected to the advertising purposes under “Manage options” in the consent form.

You may withdraw your consent at any time with effect for the future, and doing so is as simple as giving it (Art. 7(3) GDPR): open Settings → Advertising and privacy options in the app. Withdrawing consent to storage on your device locks KiwiCall Lite just as a refusal does: from the withdrawal no further advertising is requested, from the next start of the app the advertising SDK is no longer started, and the way back is “Allow ads” on the app's lock screen. You can additionally reset or delete your advertising identifier in Android under Settings → Privacy → Ads.

5.5 Transfers to third countries

Advertising data, and the data transmitted when your consent status is checked or the consent form is loaded (section 5.3), may be processed by Google LLC and other partners in the United States and in other countries outside the EEA. Such transfers are based on the European Commission's adequacy decision of 10 July 2023 on the EU-US Data Privacy Framework where the recipient is certified under that framework, and otherwise on Standard Contractual Clauses pursuant to Art. 46(2)(c) GDPR. Despite these safeguards, a level of data protection equivalent to that of the EU cannot be guaranteed in every case, in particular with regard to access by public authorities in the recipient country.

5.6 Retention

We store no advertising data ourselves: no data reaches a server operated by us at any point, and we operate no such server. Retention by the advertising partners is governed by their own retention policies, set out in the privacy policies referred to in section 5.1. Your consent decision is stored locally on your device by the consent management platform until you change or withdraw it, or until you uninstall the app. Other storage the advertising SDK keeps on your device (section 5.3) is governed by Google's policies referred to in section 5.1, and is removed when you uninstall the app. The app set ID is held by Google Play services, not by the app: Google resets it when the last app from the same developer is uninstalled, when none of them has used it for 13 months, or when the device is reset to factory settings.

5.7 The advertising-free alternative

KiwiCall Lite is financed by advertising. The alternative to consenting is the paid edition of KiwiCall, a one-time purchase on Google Play at the price shown there. It has the same features, contains no advertising SDK and no internet permission, as described in section 4, and can take over your schedules and call history from KiwiCall Lite, as described in section 3. If you refuse or withdraw consent to storage on your device, KiwiCall Lite stays locked until you consent or use the paid edition instead (section 5.4); calls are never locked.

6. Android permissions and why they are needed

  • Default phone app role (ROLE_DIALER) — required so that Android permits the app to place, monitor and end calls through InCallService, and to read and change Android's list of blocked numbers (section 3). Without this role automatic redial cannot work.
  • CALL_PHONE — placing calls.
  • READ_PHONE_STATE, READ_PHONE_NUMBERS — recognising the state of a call and identifying the available SIM cards for SIM routing.
  • READ_CONTACTS — local, read-only lookup of contact names, numbers and photos, for suggestions while you dial, to show who a number belongs to, and for the app's contact sheet. No contact data is transmitted, in either edition.
  • READ_CALL_LOG — reading Android's own call log so that the history screen and the recent calls on the dial pad also show calls made or received outside the app, so that the dial pad's contact suggestions list the people you called recently first, and so that the History tab in the bottom bar can show how many missed calls you have not seen yet.
  • WRITE_CALL_LOG — marking as read every missed call Android still counts as new, when you open the history screen and for as long as it stays open — all of them, not only the ones the list happens to show — so Android stops announcing the same missed calls after every restart; and deleting the calls you select and delete on the history screen. Nothing else in the call log is changed and no other entry is deleted.
  • Foreground service (FOREGROUND_SERVICE, FOREGROUND_SERVICE_PHONE_CALL) — keeping an automatic redial session running, with a persistent notification so that a running session is always visible.
  • Exact alarms (SCHEDULE_EXACT_ALARM, USE_EXACT_ALARM) — starting scheduled calls at the intended second.
  • POST_NOTIFICATIONS — notifications for incoming, ongoing and missed calls, running redial sessions and scheduled calls.
  • USE_FULL_SCREEN_INTENT — showing a scheduled call on the lock screen at the scheduled time, so that no call is placed unannounced.
  • RECEIVE_BOOT_COMPLETED — restoring your schedules after the device restarts.
  • MANAGE_OWN_CALLS, WAKE_LOCK, VIBRATE, MODIFY_AUDIO_SETTINGS — routing a call through Android's telephony stack, keeping a running redial session from being suspended, vibrating for call notifications, and switching between earpiece and speaker during a call.
  • Carry-over from KiwiCall Lite — no permission is used for it, in either edition. KiwiCall Lite answers the paid edition and no other app, recognising it by its signing certificate. That lets the paid edition read KiwiCall Lite's schedules and call history on the same device, once, when you accept the upgrade offer. The data moves between the two apps on the device and is never transmitted. Section 3 describes it.
  • INTERNET — declared by KiwiCall Lite only, to serve advertising (section 5). The paid edition does not declare it (section 4).
  • ACCESS_NETWORK_STATE — KiwiCall Lite only: the ad SDK checks whether the device is online before it requests an ad.
  • com.google.android.gms.permission.AD_ID — KiwiCall Lite only: access to the resettable advertising ID. It is read and sent only after you have consented to storage on your device; without that consent the advertising SDK is not started (sections 5.2 to 5.4).
  • ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION, ACCESS_ADSERVICES_TOPICS — KiwiCall Lite only: the Android Privacy Sandbox interfaces that the Google Mobile Ads SDK brings with it. They serve advertising and nothing else. The app does not initialise the advertising SDK until Google's consent platform reports that ads may be requested, which is after you have answered the consent form. The measurement the SDK would otherwise start for itself is held back until then too.
  • DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION — generated by the Android build tools and prefixed with each edition's own package name. It lets androidx register an internal broadcast receiver without exporting it, on Android 13 and newer. It is signature-level, names no data, reaches nothing outside the app's own process, and Play lists it under "Other".

Only two things above move any of your data. In KiwiCall Lite, the six advertising permissions send to Google — what they collect and where it goes is section 5. The carry-over reads KiwiCall Lite's schedules and call history into the paid edition, on the device and only when you accept the offer, and that copy never leaves the phone (section 3). No other permission here moves anything: what they read stays in the app on your device, as section 3 describes. Neither edition sends anything to us: we run no server.

While KiwiCall is your default phone app, almost all of the sensitive ones above arrive with that role rather than through a prompt of their own — placing calls, phone state, contacts, notifications (Android 13 and later) and the two call-log permissions. You can deny any of them in Android's permission settings, and KiwiCall stays your phone app if you do; giving the role to another app withdraws them together. The remaining entries are not prompted at all: the app cannot run without them, and Android grants them when it is installed. Before the app asks to become your default phone app, it explains on its start screen why it needs that role.

7. Your rights

Under the GDPR you have the right to request access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20), and the right to object to processing based on legitimate interests (Art. 21). Where processing is based on consent, you may withdraw it at any time with effect for the future (Art. 7(3)); see section 5.4.

Please note that data held only on your device is beyond our reach: we cannot provide access to it, correct it or erase it, because we never receive it. You control it directly, in the app and through Android.

To exercise your rights, contact [email protected].

You also have the right to lodge a complaint with a supervisory authority (Art. 77 GDPR). The authority competent for us is:

Der Hessische Beauftragte für Datenschutz und Informationsfreiheit, Gustav-Stresemann-Ring 1, 65189 Wiesbaden, Germany

You may also lodge a complaint with the supervisory authority of your habitual residence.

8. Children

Neither edition is directed at children. We ask that persons under the age of 16 do not use KiwiCall Lite; where the law of a Member State sets a lower age, that age applies (Art. 8(1) GDPR). We have no way to verify a user's age and do not attempt to.

9. Changes to this policy

We update this policy when the app changes or the legal position requires it. The current version is always available at https://kiwicall.kiwicanopy.com. The date of the most recent change is given at the top of this page.

KiwiCanopy

Because our time is precious 🥝

Support on Ko-fi
FeaturesFeature GuideGoogle PlayKiwiCall LiteGitHubKiwiCanopyKiwiDeskImprintPrivacy PolicyTerms of Service

© 2026 KiwiCanopy

Built by Maikel · @hajiboy95

Now go eat a kiwi — KiwiCall will hold the line for you. 🥝