Pump and Feed Log - MilkLedger

Legal & important information

Privacy Policy

What stays on your devices, how subscriptions work, and your choices about information.

Effective and last updated: · Version 1.0

1. Scope and who is responsible

This Privacy Policy explains the information practices of Pump and Feed Log - MilkLedger (the “App”), its Apple Watch companion, widgets and these legal pages. References to “we,” “us” or “our” mean the developer identified as the App’s seller in its Apple App Store listing. For privacy questions and requests, contact masalappfactory@gmail.com.

Milk and child records stay on your devices unless you choose to export or share them. Subscription-related information is processed by Apple and RevenueCat. This does not mean that no information ever leaves your device.

No MilkLedger account is required. We do not operate a server that receives your milk ledger, child profiles or notes. The policy distinguishes local records from billing, support and website information.

2. Records and settings processed on your devices

InformationPurpose and location
Optional child names or nicknames and birth dates; shared/child stash selectionOrganize records by child on the iPhone and paired Watch. Names and birth dates are not sent to RevenueCat. You can omit them or use a nickname.
Milk quantities, units, pumping/feed/transfer/discard times, container names and storage locations, notes and correctionsCalculate balances, storage targets, history and trends locally. Removed/corrected movements may remain in an audit history. Older backups may include opening-stock records, personal labels or thaw events.
Handling answers, separate-container details and mixing acknowledgementsApply the App’s movement restrictions and record-based storage rules. These do not measure temperature or establish milk safety.
Display/unit choices, local time-based appearance, reminder choices and permissionsCustomize the App and schedule local alerts. Automatic night appearance uses device time, not GPS location.
Disclosure version and acknowledgement time; onboarding completionRecord locally that the information screen has been read and determine whether to show it again. This is separate from purchase authorization and notification permission.
Local record, container, stash, installation-generation and synchronization identifiers; free-entry countLink related local records, avoid duplicate Watch entries and apply the shared ten-entry allowance. These ledger identifiers are not supplied as a RevenueCat account identity.

These records can be sensitive, including information about a child or feeding activity. Only enter information you are authorized to keep. The App does not upload this ledger to the developer or use it to train an AI system.

3. Apple Watch, widgets and notifications

Apple Watch: a paired Watch can receive a ledger snapshot, profiles, display preferences, balances and a Premium access hint through Apple’s device-connectivity services. Quick entries, including a new container and its child association, can be stored in a local offline queue and sent to the iPhone later. Entries may remain pending or need review. This is device synchronization, not an account-based caregiver sharing service.

Widgets: the iPhone shares a local App Group file with its widget extension. It contains the selected stash’s amount, units, relevant dates, aggregate future date/total changes, routing identifiers and update time. It excludes child names, birth dates, notes and full movement history. These summaries allow the displayed amount to exclude milk as known Best by dates pass and route Pump/Feed actions into the App. Device settings control Lock Screen visibility; iOS controls refresh timing. Turning off Premium or deleting data causes the App to replace or clear its summary, but a displayed widget can lag.

Notifications: optional Premium expiry reminders are scheduled locally on the iPhone after permission is granted. Notification payloads include a container identifier and recorded target date, not a child’s name, birth date or milk notes. Apple may forward alerts to a paired Watch according to its settings. No developer-operated remote-push service receives milk records. You can disable reminders in the App or revoke notification permission in system settings. Delivery is not guaranteed.

4. Apple and RevenueCat subscription information

The iPhone initializes RevenueCat to load subscription plans, check trial eligibility, validate purchases, restore access and update Premium status. This can communicate with RevenueCat before a purchase, not only after you subscribe.

RevenueCat uses a generated, persistent, pseudonymous app-user identifier. We do not provide an email address or a MilkLedger login ID to the SDK and do not call its login/logout functions. A pseudonymous identifier is not a guarantee that information is legally anonymous.

Subscription processing may include that identifier, an Apple device vendor identifier when available, receipt or transaction identifiers, products, purchase/renewal/expiry and trial status, entitlement/access status, price and currency where supplied, and technical request information. The installed SDK also sends app/SDK and operating-system versions, device/platform information, preferred locales, storefront and app lifecycle/debug metadata. Servers receive network information such as an IP address when contacted. These are billing and app-functionality data, not copies of your milk ledger.

Apple handles payment authorization and payment credentials. We do not receive your full payment-card number. RevenueCat makes subscription/customer status and related billing information available to us through its service. We do not send milk records, child names, birth dates, container notes or disclosure acknowledgements to RevenueCat.

A three-day free trial, when available and confirmed for an eligible user, is administered through Apple and RevenueCat in the same way as a subscription. It automatically converts to the selected paid plan unless cancelled in time. The ten-entry free allowance is a separate local feature. See the trial terms.

RevenueCat processes customer subscription data under its Data Processing Addendum; its Privacy Policy describes its own privacy practices. Apple’s processing is described in its Privacy Policy. Deleting local ledger records does not cancel a subscription or automatically erase these providers’ billing records.

5. Support communications and diagnostics

If you email us, we receive your email address, message and any attachments or technical details you choose to send. Our contact address is hosted by Google’s Gmail service, so email is also processed by your email provider and Google. We use correspondence to respond, troubleshoot, address privacy requests and keep necessary support/security records; we do not automatically subscribe you to marketing.

Please redact names, birth dates, health details, milk notes and purchase identifiers that are not needed for the issue. Do not email payment-card details. If sensitive records are unexpectedly sent, we limit their use and retention to what is necessary for the request and applicable law; we will seek any additional permission that is legally required before further use.

The App includes no third-party advertising or behavioral-analytics SDK and no separate third-party crash-reporting SDK. Apple may process device diagnostics under your Apple settings. SDKs and development builds can produce local technical logs; if you voluntarily share logs or screenshots, check their contents first. RevenueCat’s billing activity and technical processing are described separately above.

6. These GitHub Pages documents and external links

These legal pages are static HTML and CSS hosted on GitHub Pages. We add no analytics scripts, advertising pixels, tracking cookies, contact forms or externally loaded fonts. Reading the pages does not transmit milk or child records to the site.

GitHub states that it logs visitors’ IP addresses for security when GitHub Pages sites are visited, including visitors who are not signed in. GitHub and your browser/network provider handle their own operational information. See GitHub Pages data collection and GitHub’s Privacy Statement.

Opening a link to Apple, RevenueCat, CDC or another site connects you to that provider under its policies. Sending an email is a separate action through your chosen mail service.

7. Purposes, lawful bases and sensitive information

We process the information available to us only for providing and securing the App, administering requested subscriptions, responding to support/privacy requests and meeting legal obligations. We do not sell or rent personal information, share it for cross-context behavioral advertising, use milk/child records for advertising, or train AI models on your records.

Where EEA, UK or similar law applies, the relevant bases for information processed by us are performance of a contract for requested subscription/support services; legitimate interests in service security, preventing billing abuse and handling ordinary correspondence, subject to your rights; and compliance with applicable legal obligations. Optional activities that legally require consent will use that consent, which can be withdrawn. On-device recordkeeping is driven by the information and actions you choose; it is not a blanket authorization to transmit health or child data.

Where information voluntarily sent to us is legally treated as sensitive, we process it only on a permitted basis, including explicit consent where required. Notification permission and a disclosure-reading checkbox are not consent to unrelated data collection. Automated storage calculations and subscription checks control App displays/features; we do not use your records for advertising profiles or automated decisions with legal or similarly significant effects.

8. Recipients and international processing

Local ledger records are copied only through the device features you use or the exports/shares you initiate. Apple and RevenueCat process subscription data; Gmail processes support messages; GitHub serves these pages. File, backup and sharing providers you select process copies under their own settings and policies.

For service-provider processing on our behalf, applicable terms restrict use to the relevant service and require appropriate protection. RevenueCat’s DPA addresses its processing and subprocessors. Apple, GitHub and providers you choose may also act independently under their own notices. Information available to us may also be disclosed when legally required, to protect rights/security, or to a successor in a lawful transfer of the App, subject to applicable notice and data-protection obligations.

Billing, website and email services may process information outside your country, including in the United States and other locations used by their providers. Where required, applicable transfer safeguards, such as approved contractual clauses or an applicable adequacy arrangement, must govern those transfers. RevenueCat’s DPA describes its contractual safeguards. Contact us to request information about safeguards relevant to information we control. This is not a promise that every record or provider is located in your country.

9. Retention

10. Your controls, access and deletion

You can choose whether to provide optional child details, correct records, adjust units/appearance, disable reminders, remove widgets and control visibility, connectivity and device backups in system settings. Editing/removing a movement may preserve its prior version in audit history. Deleting a child profile is not a promise to erase that child’s historical records; use the App’s full delete action when you need to remove the local ledger.

Settings → Delete all records and settings removes the local milk ledger, profiles, ledger preferences and App-managed recovery files. It does not immediately wipe a disconnected Watch, exported files or provider backups. Onboarding/disclosure preferences and billing information are separate as described above. You must manage Apple subscriptions separately in your Apple Account.

Because we do not hold a server copy of the ledger, we cannot look up, recover or remotely edit your local milk records using an email address. Standard JSON/CSV exports and backup/restore are Premium features, but statutory data-protection rights are not made conditional on Premium. Email us if you need help exercising a right or accessing information we actually control.

11. Privacy rights and how to make a request

Depending on your location and applicable law, you may have rights to learn about processing; access, correct, delete or obtain a portable copy of information; restrict or object to processing; withdraw consent; appeal a request decision; and complain to a competent privacy regulator. Where applicable, you can exercise these rights without unlawful discrimination. We do not sell personal information or share it for targeted/cross-context advertising, so we do not operate an advertising-sale opt-out program.

Email masalappfactory@gmail.com with “Privacy request — MilkLedger,” explain the request and indicate whether it concerns local records, support correspondence or a purchase. We may request proportionate information to verify authority and locate relevant billing information, such as a transaction reference or pseudonymous RevenueCat identifier. Do not send passwords or payment-card details. We respond within the time required by applicable law, explain lawful limits and coordinate processor requests where relevant. Apple may need to handle information it controls directly.

Withdrawing consent does not invalidate earlier lawful processing. Some billing, security or legal records may need to be retained despite a deletion request. If you believe your concern is unresolved, you may contact the competent authority, including your local EEA supervisory authority or the UK Information Commissioner where applicable. Contacting us first is not a condition of those rights.

12. Children and information about babies

The App is designed for adult caregivers and is not directed to children under thirteen or intended for independent child use. Optional information about a baby is supplied by the responsible caregiver, not requested from the baby, and remains local unless that caregiver shares it. We do not knowingly collect children’s personal information directly from child users through a MilkLedger account or advertising system.

If you believe a child has provided personal information to us through support or another channel, contact us. We will assess the report and take appropriate steps under applicable law. Please use nicknames and avoid unnecessary identifying or sensitive information.

13. Security and policy updates

The App uses operating-system app isolation and device file-protection facilities for local records, and HTTPS for supported service connections. These measures do not make devices, exports, email or providers immune from unauthorized access or loss. Protect devices with a passcode, review Lock Screen/widget visibility, keep software updated and protect exported files. The App does not add a password or independent end-to-end encryption layer to exported JSON/CSV files.

We may update this Policy as the App or its processing changes. The effective date identifies the current version; material changes will be communicated as required by law, and any newly required consent will be obtained separately. Contact masalappfactory@gmail.com for questions or an accessible copy.