Cookie and Similar Technologies Policy

Last updated: July 23, 2026

This policy explains cookie-like technologies used in the RhemeSignal mobile application ("Application").

Scope note: RhemeSignal is a mobile application, not a browser-based website; therefore, it does not use browser cookies (HTTP cookies) in the classical sense. This document covers local storage and SDK identifiers used by the Application. The cookie usage of the rhemelabs.com promotional/website is outside the scope of this document; the website should document its own cookie implementation separately.

1. Local Storage and Identifiers Used by the Application

• On-device local storage (shared_preferences): Session state, user preferences (theme, language, etc.) — stored until the Application is uninstalled/data is cleared.
• Firebase Authentication identity token: Keeping your session open, secure API access — during the session duration, automatically renewed.
• Firebase Cloud Messaging (FCM) token: To send push notifications — periodically renewed as long as the Application remains installed.
• RevenueCat user/device ID: Associating subscription status with your device — stored as long as your account/subscription is active.
• Firebase Crashlytics identifier: Associating crash reports (without determining your personal identity) — stored as long as the Application remains installed.
• Android Advertising ID (Advertising ID): Device/analytics identification for SDKs used (Firebase, RevenueCat) — determined by your operating system settings, can be reset.

2. How You Can Control These Identifiers

• Advertising ID: You can reset your advertising ID or limit personalized ad tracking from the Settings → Privacy → Ads menu on your Android device (the Application does not show ads, but SDKs may use this ID for analytics purposes).
• Push notifications: You can turn them off from device notification settings or in-app settings; in this case, your FCM token will not be used to send notifications.
• Local data: When you uninstall the Application from your device or clear application data, local preferences and cache held on the device are deleted.
• Account deletion: If you delete your account, associated identifiers held on the server side (FCM token, RevenueCat user ID match, etc.) are also deleted.

3. Further Information

For general information regarding the processing of your personal data, please refer to the Privacy Policy and KVKK Clarification Text documents. For your questions: contact@rhemelabs.com