Your medication, dose, injection-site, side-effect, weight, nutrition, hydration, activity, goal, profile, and reminder entries are stored locally on your device in the current version of GLP Tracker. We do not operate an account system or app backend that receives those entries.

• We do not sell your health information.
• We do not send the content of your health or wellness entries to analytics, attribution, advertising, or subscription providers.
• Limited technical, usage, attribution, and purchase information may be processed by our service providers as described below.
• Medication reminders are scheduled locally on your device. Notification content may reveal that you use a medication tracker to anyone who can view your notifications.
• You can delete locally stored app data using the app’s deletion controls or by deleting the app, subject to data retained separately by Apple or service providers.

This Privacy Policy explains how LOGIC FUSION, LLC (“we”) processes personal data when you use GPL Tracker mobile application (the “App”). The reference to the services available through the App is the “Services”.
This Privacy Policy (also the “Policy”) applies whenever you use the App or otherwise interact with us in connection with the Services.
For the purposes of applicable data protection laws, including the EU General Data Protection Regulation (GDPR), the data controller is:
Name: LOGIC FUSION, LLC  
Address: 4713 Southern Breeze Dr, Naples, FL, US 34114, United States
Email: privacy@logicfusion.net

The App is a personal tracking tool. It is not a healthcare provider, health plan, pharmacy, or healthcare clearinghouse. Unless we expressly state otherwise, we are not a "covered entity" or "business associate" under the U.S. Health Insurance Portability and Accountability Act (HIPAA). Other privacy and consumer-protection laws may still apply.
The App is not a medical device and does not provide medical advice, diagnosis, treatment, or emergency services. Information, calculations, logs, and reminders are for personal tracking only and may be inaccurate, incomplete, delayed, or unavailable. Do not use the App to determine or adjust medication, dosage, or treatment. Always follow your healthcare professional’s instructions and independently verify your medication schedule. In an emergency, contact local emergency services.
This notice describes the App’s intended function; it does not limit rights or remedies that cannot lawfully be limited.

3.1 Information stored locally on your device
Depending on the features you use, the App may store the following information locally:

• Medication and treatment-tracking entries, such as medication name, selected or entered dose, schedule, injection date and time, injection site, adherence or completion status, and notes.
• Health and wellness entries, such as side effects or symptoms, weight, meals or nutrition, water, protein, fiber, activity, goals, progress, and related dates or notes.
• Profile and preference information, such as a display name, avatar, age or age range, onboarding selections, units, goals, appearance, and reminder preferences.
• Local notification information, such as reminder time, medication label, notification status, and notification permissions.

In the current version, these entries remain on your device. We do not receive or store them on our servers, and they are not sent to the third-party SDKs identified below. Your device, operating system backups, or device-management configuration may create copies outside the App; those copies are controlled by you and the relevant platform provider.
3.2 Technical, analytics, and usage information
The App and integrated service providers may automatically process limited information such as:

• device model, operating-system version, language, locale, time zone, App version, bundle identifier, and SDK version;
• internet protocol (IP) address and approximate location inferred from it, where processed by a provider;
• device or installation identifiers, vendor identifiers, advertising identifier (IDFA) when available and permitted, AppsFlyer identifiers, Firebase identifiers, and an anonymous RevenueCat app user identifier;
• App launch, session, screen or feature interaction, onboarding, paywall, subscription, and other event names that are configured not to contain medication, dose, symptom, weight, nutrition, or other health-entry values;
• diagnostic and SDK performance information, such as errors, network status, event-delivery status, and basic technical logs.

Event naming and SDK configuration are operational controls. We intend to send only value-free events and limited technical data, but you should avoid entering health information into any free-text field that is not expressly designated for local health entries.
3.3 Purchase and subscription information
Apple processes App Store purchases and payment credentials. We do not receive your full payment-card number. Apple and RevenueCat may provide or process transaction identifiers, product purchased, purchase date, subscription status, renewal or expiration status, storefront, currency, receipt or purchase token, and an App-specific user identifier so that we can provide and restore paid access, manage entitlements, prevent fraud, and understand subscription performance.
3.4 Support information
If you contact us, we process the information you choose to provide, such as your name, email address, message, attachments, and troubleshooting details. Do not include medication logs or other health details unless they are necessary for your request and you are comfortable sharing them.
3.5 Information we do not currently collect through the App
The current App does not require an account and does not transmit your locally stored health entries to an App-operated backend. The current App does not access Apple Health or HealthKit. If we add account, cloud-sync, HealthKit, remote push-notification, or similar functionality, we will update this policy and request permissions where required before collecting the relevant data.

• Provide local tracking, progress, goal, personalization, and reminder features.
• Operate onboarding, paywalls, subscriptions, purchase restoration, and premium entitlements.
• Measure installs, acquisition sources, campaign performance, and aggregate App usage.
• Configure features and experiments through remote configuration without sending health-entry values.
• Maintain, debug, secure, and improve the App and investigate fraud or abuse.
• Respond to support requests and communicate about service or policy changes.
• Comply with law, enforce terms, protect rights and safety, and establish or defend legal claims.

We do not use medication, dose, side-effect, weight, nutrition, or similar health-entry values for advertising, cross-context behavioral advertising, data brokerage, or marketing profiles.

Where applicable law requires a legal basis, we rely on the bases below. Local-only processing performed solely on your device may fall outside some controller obligations, but we describe it for transparency.
1. Purpose: Provide requested App features and subscriptions
Legal basis: Performance of a contract; steps requested before entering a contract
Data we use: Local entries; preferences; purchase and entitlement data

2. Purpose: Analytics and product improvement
Legal basis: Consent where required; otherwise legitimate interests in operating and improving the App
Data we use: Limited usage, device, installation, and diagnostic data

3. Purpose: Attribution and tracking
Legal basis: Consent, including App Tracking Transparency permission where Apple defines the activity as tracking
Data we use: Advertising or attribution identifiers; install and campaign events

4. Purpose: Security, fraud prevention, legal compliance
Legal basis: Legitimate interests; compliance with legal obligations; establishment or defense of legal claims
Data we use: Technical, transaction, support, and relevant records

5. Purpose: Support communications
Legal basis: Performance of a contract; legitimate interests; consent where appropriate
Data we use: Contact details and message content
If we ever receive health data that is "special category" data under Article 9 GDPR, we will identify and rely on an applicable Article 9 condition, such as explicit consent, in addition to an Article 6 basis. Under the current architecture, health entries remain on your device and are not received by us.
Where we rely on legitimate interests, we consider the nature of the information, your reasonable expectations, safeguards, and your rights. You may object as described in Section 13.

Your health, wellness, profile, and reminder information is stored in the App’s local storage on your device. Protection depends in part on your device passcode, biometric lock, operating-system security, backup settings, notification-preview settings, and physical control of the device.
We use reasonable administrative, technical, and organizational safeguards appropriate to the information we process. No storage or transmission method is completely secure. You should keep iOS and the App updated, use a strong device passcode, restrict notification previews if desired, and avoid sharing an unlocked device.
If you enable device backups, Apple or another backup provider may process a copy under its own terms and privacy policy. We do not control your personal backup configuration.

The current App uses local notifications. Reminder schedules are stored and notifications are generated on your device; we do not need a remote push token to deliver them. A notification may display the App name, medication name or reminder text, but the current design does not intentionally display dose information. Anyone who can view your lock screen or notifications may infer sensitive information. You can change notification permissions and preview settings in iOS Settings and change or disable reminders in the App.
Notifications can be delayed, suppressed, or missed because of device settings, operating-system behavior, power state, connectivity, or other factors. Do not rely on the App as your only medication reminder.

AppsFlyer and the Meta SDK may be used to measure advertising attribution and campaign performance. Where their operation constitutes "tracking" under Apple’s rules, the App will request permission through Apple’s App Tracking Transparency (ATT) framework before accessing the IDFA or engaging in tracking. Declining ATT permission does not prevent you from using the App’s core tracking features, although attribution may be less precise.
Depending on configuration and consent, attribution providers may process device and installation identifiers, IP address, device and App characteristics, install source, campaign information, and configured standard or value-free events. They are not authorized to receive the content of your health entries. We do not permit health data to be used for targeted advertising.
Apple’s ATT choice is not necessarily a complete opt-out under every privacy law. Where applicable, additional choices or request mechanisms are described in Section 13.

We disclose limited information to providers that help operate the App. Their processing depends on the SDK versions, settings, permissions, and features actually enabled.
1. Provider: Apple (App Store, StoreKit, iOS)
Purpose: Distribution, purchases, receipts, device permissions, local notifications
Data involved: Transaction, storefront, device, and permission information; payment details are handled by Apple

2. Provider: Google Firebase Analytics
Purpose: App analytics and usage measurement
Data involved: App/device identifiers, device and App characteristics, IP-derived data, event names, session and usage data

3. Provider: Google Firebase Remote Config
Purpose: Feature configuration and experiments
Data involved: App-instance and technical information; experiment assignments where enabled

4. Provider: AppsFlyer
Purpose: Install attribution and campaign measurement
Data involved: Attribution/device identifiers, IP address, install and campaign data, device/App data, value-free events; IDFA only when available and permitted

5. Service Provider: Amplitude, Inc. (USA)
Services: Product analytics
Data shared: Pseudonymized usage data, device and App information, IP address
Purpose of sharing: To understand feature usage and improve the App

6. Provider: Meta SDK
Purpose: Advertising attribution and standard app-event measurement
Data involved: Device or advertising identifiers when permitted, technical data, install/session or configured standard events

7. Provider: RevenueCat
Purpose: Subscription and entitlement management
Data involved: Anonymous App user identifier, purchase history, receipts/tokens, subscription status, device/technical information
Providers generally act as processors or service providers under contract, although Apple and certain advertising or attribution partners may act as independent controllers for some processing. We require providers to protect information consistently with applicable law and our instructions where they process on our behalf.
We may also disclose information to professional advisers, auditors, insurers, authorities, courts, or counterparties where reasonably necessary for legal compliance, safety, claims, financing, reorganization, merger, acquisition, or sale of assets. We will not transfer locally stored health entries in a business transaction unless the architecture changes and we first provide appropriate notice and obtain consent where required.

We do not sell personal information for money. We do not sell or share medication, dose, side-effect, weight, nutrition, or other health-entry values, and we do not authorize their use for advertising.
Some U.S. laws define "sale" or "sharing" broadly to include disclosures of identifiers or activity to advertising or attribution partners for cross-context behavioral advertising, even without payment. To the extent our use of AppsFlyer or Meta constitutes sale, sharing, targeted advertising, or profiling under applicable law, we will provide required consent and opt-out mechanisms and honor legally recognized preference signals where required. We do not knowingly sell or share personal information of users under 16.
Washington and certain other states regulate consumer health data separately. Under the current design, health entries remain on your device and are not collected by us or disclosed to third parties. If this changes, we will provide a separate consumer health data privacy notice and obtain consent or authorization as required before collection, sharing, or sale.

We and our providers may process limited technical, attribution, purchase, or support information in the United States and other countries that may not provide the same level of legal protection as your country. Where required, we use safeguards such as the European Commission’s Standard Contractual Clauses, the UK International Data Transfer Addendum, adequacy decisions, or participation in an approved data-transfer framework, together with supplementary measures where appropriate. Contact us for information about the relevant safeguard.

1. Information: Local health, wellness, profile, and reminder data
Retention approach: Until you delete individual entries, use an in-App deletion control, or delete the App; device backups may persist under your backup provider’s rules
2. Information: Subscription and transaction records
Retention approach: For the subscription lifecycle and thereafter as needed for restoration, accounting, fraud prevention, dispute resolution, and legal obligations
3. Information: Analytics, attribution, and technical data
Retention approach: According to configured retention periods and provider rules, for no longer than reasonably necessary for analytics, attribution, security, and legal purposes
4. Information: Support communications
Retention approach: For as long as needed to resolve the request and maintain appropriate business and legal records
Deleting the App does not automatically delete information held independently by Apple, RevenueCat, Firebase, AppsFlyer, Meta, your device backup provider, or us in support records. To request deletion of information we control, contact privacy@logicfusion.net. We may need limited information to verify and complete a request. We may retain information where required or permitted by law.

Depending on where you live, you may have rights to access, know, correct, delete, restrict, or obtain a portable copy of personal data; object to processing; withdraw consent; opt out of sale, sharing, targeted advertising, or certain profiling; appeal a denied request; and complain to a regulator. These rights are subject to legal scope, exceptions, and verification.
13.1 Device and App controls

• Delete or edit local entries using available App controls.
• Delete locally stored App data by using "Delete All Data" if available or by deleting the App, subject to device backups.
• Manage notifications in the App and in iOS Settings.
• Manage tracking permission in iOS Settings under Privacy & Security > Tracking.
• Manage subscriptions through your Apple ID and App Store subscription settings.

13.2 Requests to us
Submit a request to privacy@logicfusion.net with the subject "Privacy Request." Describe the right you wish to exercise and the App or device context. Because the current App has no account and we do not receive your local health entries, we may be unable to identify or retrieve local data. We will not ask for more information than reasonably necessary to verify a request.
You may use an authorized agent where applicable. We will not discriminate against you for exercising privacy rights. If we deny a request, you may appeal by replying with "Privacy Appeal" and explaining why you believe the decision should be reconsidered.
13.3 EEA, UK, and Switzerland
You may lodge a complaint with the supervisory authority in your country of residence, place of work, or the location of an alleged infringement. You may withdraw consent at any time without affecting processing that occurred before withdrawal.
13.4 California and other U.S. states
Where applicable, you may request the categories and specific pieces of personal information collected; sources; purposes; categories of recipients; correction; deletion; portability; and opt-out of sale, sharing, or targeted advertising. We do not use or disclose sensitive personal information to infer characteristics or for purposes that trigger a right to limit under California law. Our practices in the preceding 12 months are described in Sections 3, 4, 9, and 10.

The App is not directed to children under 13, and we do not knowingly collect personal information online from children under 13. Users must be at least 16 in the EEA or the minimum age at which they can consent to online services in their country, unless a parent or guardian provides valid authorization where permitted. If you believe a child has provided personal information to us, contact privacy@logicfusion.net.

Although the current architecture keeps health entries on-device, health-app breach-notification laws may apply if our practices or integrations change. If we discover an incident involving information for which notification is legally required, we will investigate and notify affected individuals and authorities within applicable time limits.

The App may link to third-party websites, policies, App Store pages, or services. Their practices are governed by their own notices. We encourage you to review them. This policy does not apply to information a third party collects independently from you.

We may update this policy to reflect changes in the App, providers, law, or our practices. We will post the revised policy and update the "Last updated" date. If changes materially affect how we process personal information, we will provide additional notice or request consent where required.

If you have any questions about this Policy, please feel free to contact us via email at privacy@logicfusion.net.