Back to home

Privacy Policy

Last Revised: October 21, 2026

This Privacy Policy explains how APPLOX DİJİTAL YAZILIM HİZMETLERİ TİCARET LİMİTED ŞİRKETİ ("Company", "we", "our", or "us") collects, uses, and protects your information when you use our mobile applications ("Services"). By downloading or using our apps, you agree to the terms of this Privacy Policy.

Table of Contents

  1. 1. Data Collection and Usage
    1. 1.1. Data Stored on Your Device
    2. 1.2. Data Stored on Our Servers
    3. 1.3. Analytics and Crash Reports
    4. 1.4. Advertising Measurement and Tracking
    5. 1.5. Purchases
    6. 1.6. Third-Party Services
    7. 1.7. Data Retention and Deletion
    8. 1.8. Your Choices
  2. 2. Technical Information
    1. 2.1. Cookies
    2. 2.2. Security
  3. 3. Legal Information
    1. 3.1. Children's Privacy
    2. 3.2. Policy Updates
    3. 3.3. Contact Information

Subex (the "App," "Service," "we," or "us") is committed to protecting your privacy. This Privacy Policy outlines how we gather, use, disclose, and protect the data gathered via our Service, as well as what choices you have regarding the collection and use of data.

1. Data Collection and Usage

Subex is a subscription tracking app. You do not need to register or provide any personal details such as your name, e-mail address or phone number to use the app. Subex does not connect to your bank account, card or e-mail inbox, does not read your App Store or Google Play purchase history, and does not read your financial transactions. All subscription entries are added by you manually. We do not sell your data.

1.1. Data Stored on Your Device

The subscription entries you create (service name, price, currency, billing period, start and renewal dates, status, category, plan name, payment method, reminder setting and any logo you choose) are stored on your device. Plan names, payment methods and logos never leave your device.

1.2. Data Stored on Our Servers

To operate renewal reminders and purchases, the app automatically creates an anonymous account for you on first launch: a random identifier issued by Firebase Authentication, linked to an account on our servers. Our servers receive and store:

  • Account: your anonymous identifier and the sign-in token issued for it.
  • Device: a random installation ID generated by the app, platform, operating system version, device model, app version, language and region settings, time zone, the IP address of your most recent request and the country we derive from it. To find the country, the IP address is sent to an IP geolocation service (ip-api.com, or another IP geolocation provider if it is unavailable), and we store only the country.
  • Push notifications: the push notification token of your device, if you allow notifications.
  • Renewal reminders: for each subscription with a renewal reminder turned on (reminders are on by default for new subscriptions), the service name, price, currency, billing period, next renewal date and how many days in advance you want to be reminded. We use this only to send the reminder at 10:00 in your local time zone.

1.3. Analytics and Crash Reports

We use Firebase Analytics to understand how the app is used, for example which screens are opened, when a subscription is added (its category, billing period and how it was added), when reminders are changed, and the answers you give to the optional onboarding questions (your goals, approximate monthly spend range and usual currency). Analytics events never include the names or prices you type in. We use Firebase Crashlytics to receive crash reports, which include device and app details and your anonymous identifier.

1.4. Advertising Measurement and Tracking

Subex does not show ads. We advertise Subex on other platforms, and we use the Meta (Facebook) SDK to measure how well those ads work. The SDK sends Meta events such as app installs and app opens, together with an identifier generated by the SDK, device details (such as device model, operating system version, language and time zone) and your IP address. Our purchase infrastructure provider RevenueCat also sends purchase events to Meta for the same purpose.

On iOS, we ask for your permission through Apple's App Tracking Transparency prompt. If you allow tracking, your device's advertising identifier (IDFA) is included, the data may be linked with data from other companies' apps and websites to measure our ads, and Google Analytics may use the analytics data described above for advertising measurement. If you do not allow tracking, the advertising identifier is not shared and these events are marked as not permitted for tracking. You can change your choice at any time in Settings > Privacy & Security > Tracking.

On Android, the Google advertising ID may be used for the same purposes. You can reset or delete it in your device settings.

1.5. Purchases

If you purchase a subscription, the transaction is processed by the Apple App Store or Google Play. We never see or store your payment details. RevenueCat, our purchase infrastructure provider, receives the store transaction information, your anonymous identifier, device identifiers (the vendor identifier, and the advertising identifier only if you allow tracking) and your IP address, so that premium features can be unlocked and restored and purchases can be attributed to our advertising campaigns. If you installed Subex from an Apple Search Ads campaign, RevenueCat also receives Apple's attribution data for that campaign.

1.6. Third-Party Services

We share data only with the service providers below and only for the purposes described in this Privacy Policy. Any third party with whom we share user data provides the same or equal protection of user data as stated in this Privacy Policy. Please follow the links to their privacy policies to read more about the data they process:

1.7. Data Retention and Deletion

Data on your device stays there until you delete the subscription, delete your account in the app, or uninstall the app.

We keep your account, device record and reminders on our servers for as long as you use Subex. If a device has not opened the app for 60 days, or no longer has a valid push token, its reminders are deactivated and no longer sent. Push tokens are deleted as soon as the push service reports them as invalid, for example after the app is uninstalled. Server logs, which include IP addresses, are kept for 14 days. Deleted data may remain in server backups until those backups are replaced in the normal course.

When you delete your account in the app (Settings > Delete Account), we immediately delete everything our servers hold for it: your account and its sign-in tokens, your device records, push tokens and notification history, and your reminders with the subscription details stored for them. We also delete your Firebase Authentication user. The app erases all subscriptions, logos and settings on your device and then continues with a new anonymous account. See our account deletion page for details.

Data processed by Firebase, RevenueCat and Meta is retained according to their own retention policies, linked above.

1.8. Your Choices

  • Tracking: allow or deny it in the App Tracking Transparency prompt, and change it later in Settings > Privacy & Security > Tracking on iOS, or reset your advertising ID on Android.
  • Notifications: turn them off in your device settings, or set a subscription's reminder to Off in the app.
  • Deletion: delete your account and data in the app (Settings > Delete Account), or ask us to delete specific data.
  • Other requests: to withdraw your consent to analytics or to ask about the data we hold, contact us at info@applox.co with your Support ID.

2. Technical Information

2.1. Cookies

The App does not use or collect "cookies." However, third-party code and libraries used by us may use "cookies" to gather data to improve their services. You are free to opt-out cookies in your device settings.

2.2. Security

We appreciate your trust in using our Service. Thus, we do our best to use commercially acceptable means for protecting your data. However, you should be aware that no transmission method over the Internet is 100% reliable and secure. That is why we cannot guarantee the total security of the data provided.