Cookies policy
Please read this cookies policy carefully as it contains important information on who we are, Tapp Collective Ltd (company number 16359619), and how we use cookies and similar technologies on the Ankaa mobile application (“App”) and related services (“Services”). This policy should be read together with our Privacy Policy, which sets out how to contact us, what personal data is collected, how and why we collect, store, use and share it generally, as well as your rights in relation to your personal data and details of how to contact us and supervisory authorities if you have a complaint.
1 Cookies
A cookie is a small text file which is placed onto your device (e.g. your smartphone or other electronic device) when you use the App. Analogous local storage technologies (such as device-local key-value stores) work in a similar way. When we use cookies or similar technologies, you will always be informed by a consent prompt within the App before any non-essential cookies or storage technologies are activated.
Cookies help us to recognise you and your device and allow us to store some information about your preferences or past actions (for more information, please see our Privacy Policy).
For example, we may monitor how many times you use the App and which features you interact with. This information helps us to understand how users engage with the App, so that we can keep improving the App.
2 Consent to use cookies and changing settings
We will ask for your consent to place cookies or other similar technologies on your device, except where they are essential for us to provide you with a service that you have requested (e.g. to allow you to remain logged-in to the App as you use its functionalities). Our approach to cookie consent is designed to comply with the UK Privacy and Electronic Communications Regulations 2003 (PECR) and the UK General Data Protection Regulation (UK GDPR).
You can withdraw any consent to the use of cookies or manage any other cookie preferences by using the tool made available to you within the Services itself. You can then adjust sliders or untick boxes as appropriate to reflect your choice. It may be necessary to refresh or restart the Services for the updated settings to take effect.
3 Our use of cookies
The table below provides more information about the cookies we use and why:
The cookies and similar technologies we use | Name | Purpose | Whether cookie is essential for us to provide you with a service that you have requested and whether we will seek your consent before we place the cookie |
|---|---|---|---|
Firebase (Google) – Authentication & Backend | Session tokens (various) | Firebase is used for user authentication and backend app functionality. It sets session identifiers to keep you logged in. Wellness inputs are processed transiently in Amazon Web Services (UK) and deleted after each session — not retained. Duration: until you sign out or your account is deleted. See: https://firebase.google.com/support/privacy | Yes, essential. No consent required. |
RevenueCat – Subscription Management | Subscription identifiers (various) | RevenueCat manages in-app subscriptions via Apple App Store and Google Play. It stores identifiers to recognise your subscription status and prevent duplicate billing. Duration: stored on your device until the App is uninstalled. See: https://www.revenuecat.com/privacy | Yes, essential for subscription and billing. No consent required. |
Meta (Facebook SDK) – Advertising | Meta SDK identifiers (various) | The Meta SDK measures advertising effectiveness and app installs. It may collect device identifiers for attribution. No health inputs are shared with Meta. Duration: stored on your device until the App is uninstalled. See: https://www.facebook.com/privacy/policy/ | No, non-essential (advertising). Consent required. |
AsyncStorage – Local Device Storage | Local device key-value store | AsyncStorage stores user preferences and app state locally on your device only (e.g. in-app settings between sessions). This data is not transmitted to our servers or any third party. No health inputs are stored. Duration: until the App is uninstalled or data is cleared by the user. | Yes, essential for App functionality. No consent required. |
4 How to turn off all cookies and consequences of doing so
If you do not want to accept any cookies, you may be able to change your device settings so that cookies (including those which are essential to the services requested) are not accepted. If you do this, please be aware that you may lose some of the functionality of the App and of other services you use on your device. For further information about cookies and how to disable them please go to the guidance on cookies published by the UK Information Commissioner’s Office: www.aboutcookies.org and www.allaboutcookies.org.
5 Changes to this policy
This policy was published on 24 April 2026 and last updated on 5 October 2026. We may change this cookies policy from time to time. When we do, we will inform you via an in-app notification.