Privacy Policy

Refluxly · Effective date: July 31, 2026 · Last updated: July 31, 2026

This Privacy Policy explains how Refluxly ("Refluxly", "the app", "we", "us", or "our") handles information in connection with your use of the Refluxly iOS application (bundle identifier xyz.bogtsi.refluxly). Refluxly is developed and operated by an individual developer based in Israel (the "Developer").

We built Refluxly to be private by design. Refluxly has no user accounts, no login, and no backend server operated by us. The symptom, meal, medication and night entries you create in the app stay on your device. The only information leaving your device is handled by the third-party services described below, each under their own privacy policy.

Short version: Your symptom, meal, medication and night entries, your custom trigger categories, and your app settings live only on your iPhone, in local on-device storage. We don't run a server and we can't see your data. Subscriptions are handled by Apple and RevenueCat. Refluxly does not use analytics or advertising, and it never asks for App Tracking Transparency permission because it doesn't track you.

1. Who we are & how to contact us

Refluxly is operated by a solo developer based in Israel. For any privacy question or request, contact us at support@bogtsi.xyz.

2. Data stored locally on your device

The following information is created and stored only on your device, in local on-device storage inside the app's own sandbox. It is never transmitted to us — we operate no server to receive it — and we cannot access it:

Because this data lives only on your device, it is removed when you delete the app. Refluxly's shipped release does not include an in-app "clear all data" button — deleting the app is how you remove what's stored. We provide no cloud backup or sync of this information ourselves; if you use iCloud device backup, your device backup is governed by Apple's policies.

3. Local notifications

If you enable lie-down or reminder notifications, Refluxly schedules local notifications on your device only — for example, when your lie-down window clears, or a daily meal-log or evening check-in reminder. These are generated and delivered entirely on-device. We use no push tokens and send no remote push notifications; nothing about your notification schedule is transmitted anywhere.

4. Exporting your data (CSV and PDF report)

Refluxly can export your entries as a CSV file (available to everyone), and Refluxly Premium can generate a PDF doctor-visit report. In both cases, the app writes the file to its own temporary storage on your device and hands it to the standard iOS share sheet. Where the file goes next is entirely your choice — Files, Mail, another app, printing — and that destination's handling of the file is governed by whatever app or service you choose. The file is not sent anywhere by us.

5. Third-party services that process data

Refluxly relies on a small number of third-party services. When you use the app, some of these services may collect or process data directly, under their own privacy policies. We map each one below.

ServiceWhen it appliesWhat it processesPurpose
RevenueCat When you start, restore, or manage a Refluxly Premium subscription Purchase and subscription data, keyed to a pseudonymous app-user identifier (we never set a user ID, because there are no accounts). No symptom, meal, medication, night or trigger data is ever sent to RevenueCat. To process purchases, validate receipts, and unlock Premium features
Apple / App Store Download, updates, and in-app purchases Purchase transactions and standard App Store data handled by Apple. Payment is made to Apple with your Apple ID — the Developer never receives or sees your payment card details. App distribution and payment processing
Expo / EAS App build and distribution Used to build and ship the app; the app sends no personal data of yours to Expo at runtime as part of Refluxly's features To build and distribute the app

We use no analytics or crash-reporting SDKs of our own (no Firebase, Sentry, Amplitude, or similar), and Refluxly's own code makes no network requests to any server we operate. Of the services above, RevenueCat is the only one the installed app itself talks to while running on your device, and what it receives is limited to purchase and subscription data as described above. Expo/EAS is part of how the app is built and shipped, not something the running app sends your data to.

Advertising & App Tracking Transparency (ATT)

Refluxly contains no advertising and no advertising SDK. The app displays no ads, contains no third-party ad or tracking framework, and does not collect or use the advertising identifier (IDFA). Because nothing in the app tracks you, Refluxly never presents Apple's App Tracking Transparency prompt. If advertising were ever introduced in a future version, this Privacy Policy would be updated before it shipped.

6. Third-party privacy policies

The services above process data under their own privacy policies, which we encourage you to review:

7. How we use information

We ourselves do not collect or receive your personal data on any server. Information is used only for the purposes described above: providing app features on-device (logging, the lie-down countdown, timeline, journal, evidence-based pattern review, methodology and refer-out content, reminders), processing subscriptions, and generating exports at your request. We do not sell your personal data, and we do not use it for advertising or profiling.

8. Data retention

Data stored locally on your device is retained until you delete the app. Data processed by third parties (RevenueCat, Apple) is retained according to their respective policies.

9. Your choices & controls

10. Medical & wellness data note

The entries you log in Refluxly (symptoms, meals, medications, nights) describe your own personal wellness history. This is sensitive information: it stays on your device by design, is never transmitted to us, is never sold, and is never used for advertising. See our Terms of Service for what Refluxly is — and is not — as a wellness tool.

11. Children's privacy

Refluxly is not directed to children and is not intended for use by anyone under the age of 13 (or the minimum age of digital consent in your jurisdiction, such as 16 under the GDPR). We do not knowingly collect personal information from children. In line with the U.S. Children's Online Privacy Protection Act (COPPA) and the GDPR's protections for children (GDPR-K), if you believe a child has provided personal information through the app, please contact us at support@bogtsi.xyz and we will take appropriate steps.

12. International users

The Developer is based in Israel. Refluxly is available through the Apple App Store internationally. The third-party services we use (RevenueCat, Apple) may process data in various countries, including the United States, in accordance with their own policies and legal safeguards. Your symptom, meal, medication and night entries are not part of any such transfer — they never leave your device. By using the app, you understand that the limited subscription information described above may be processed in countries other than your own.

13. Security

Because your app data stays on your device, its security is tied to your device's own protections (passcode, encryption, biometric lock). Data handled by third-party services is protected under their respective security practices. No method of storage or transmission is 100% secure.

14. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date above and post the new version at this URL. Material changes will be reflected here; your continued use of the app after an update constitutes acceptance of the revised policy.

15. Contact

Questions about this Privacy Policy or your data? Email support@bogtsi.xyz.