Effective and last updated: September 19, 2026

The developer of PlantMoment (the “Developer”) establishes this Privacy Policy for the handling of user information in the iOS application PlantMoment (the “App”).

1. Information Handled by the App

1.1 Information Stored on the Device

The App generally stores the following information entered, captured, selected, or created by the user on the user’s device:

  • Plant names, species, photos, tags, dates on which plants were welcomed, pot details, and growing environment information
  • Care items, schedules, notification settings, care history, and notes
  • Images, videos, audio, display settings, and related information for Photo Moments, Video Moments, and Plant Stories
  • App settings and tutorial completion status

The App does not automatically sync this information to a proprietary account or cloud service managed by the Developer. However, when the user uses a feature described in Section 2, information necessary to provide that feature is sent to an external service.

1.2 Backups

When the user creates a backup, the App creates a backup file containing plants, care information, Moments, Plant Stories, settings, images, videos, and related data, and exports it to a location selected by the user in Files.

The App does not apply its own encryption to backup files. The user and the provider of the selected storage location are responsible for storage, sharing, copying, deletion, and access control. App Store purchase information, operating system permission status, and notification requests registered on the device are not included in a backup.

2. Information Sent to External Services

2.1 Plant Identification from Photos (Pl@ntNet)

When the user explicitly requests plant identification from a photo, the App processes a plant image captured or selected by the user to a suitable size and sends it to the Pl@ntNet plant identification service to obtain possible plant species. The App also sends the language code corresponding to the App’s display language and other technical information required for the request.

According to the published Pl@ntNet API terms, images submitted for identification are handled in volatile server memory during identification and are not stored in its database. Query history, such as request dates and times, and statistical information may be recorded. For the latest information, please see the Pl@ntNet API Terms of Use.

Identification results may include candidate names, confidence scores, and reference images and attribution information provided by Pl@ntNet.

2.2 Purchase Management (RevenueCat)

The App uses RevenueCat to manage Pro lifetime purchases, monthly subscriptions, purchase status, and purchase restoration. RevenueCat may receive or process the following information:

  • An anonymous App User ID generated by RevenueCat
  • Technical information such as device type, operating system, and App version
  • App Store receipts and transaction information
  • Purchased products and purchase, renewal, cancellation, expiration, and refund status
  • Information necessary to provide purchase entitlements, such as when the App was last used

Payment information such as credit card numbers is processed by Apple and is not obtained directly by the App.

For information about RevenueCat’s data practices, please see the RevenueCat Privacy Policy.

2.3 Usage Analytics (Firebase Analytics)

The App uses Firebase Analytics to understand usage, improve quality, and investigate issues. Firebase Analytics may automatically collect the following information:

  • An app instance identifier
  • Usage information such as first launch, app launches, updates, sessions, and screen views
  • Technical information such as device model, operating system, App version, and language
  • Approximate location inferred from the IP address
  • Events related to App Store in-app purchases and subscriptions

The App does not assign a custom user ID in Firebase Analytics and does not send plant names, notes, captured photos, or videos as analytics events.

For information about Firebase and Google’s data practices, please see Privacy and Security in Firebase and the Google Privacy Policy.

2.4 Apple Services

The App uses Apple services and iOS features for App Store distribution, in-app purchases, subscriptions, purchase restoration, local notifications, the camera, microphone, photo library, Files, and related functionality. For information about Apple’s data practices, please see the Apple Privacy Policy.

3. Device Permissions

The App requests the following permissions only when the user selects a related feature:

  • Camera: To photograph plants and capture Photo Moments and Video Moments
  • Microphone: To record audio for Video Moments
  • Add to Photo Library: To save completed Photo Moments, Video Moments, and Plant Stories
  • Notifications: To provide local notifications for care schedules
  • Files Access: To save backups to a location selected by the user and restore from backups

Permissions can be changed in iOS Settings. If a permission is not granted, some or all of the related features may be unavailable.

4. Purposes of Use

The Developer handles the information described in this Policy for the following purposes:

  1. Providing the App and Pro features
  2. Presenting possible plant species
  3. Processing in-app purchases, subscriptions, and purchase restoration
  4. Understanding usage, improving quality, and investigating issues
  5. Preventing misuse of external services and providing stable functionality
  6. Responding to user inquiries

5. Disclosure to External Services

The App sends information to the external services described in Section 2 only to the extent necessary to provide the relevant features. Except where required by law, the Developer does not provide user information to third parties for other purposes.

Storage locations, retention periods, and deletion methods for information handled by external services are governed by each service’s terms and policies and by the Developer’s settings for that service.

6. Retention

Information stored on the device remains there until the user deletes it in the App or removes the App from the device. Information that the user saves or shares to the photo library, Files, or an external service is not automatically deleted when the App is removed.

Retention periods for information processed by Firebase Analytics, RevenueCat, Pl@ntNet, and Apple are governed by each service’s policies and by the Developer’s settings. The Developer endeavors not to retain information beyond what is necessary for the purposes described in this Policy.

7. Deletion

The user can delete information stored on the device through the App’s deletion features or by uninstalling the App. Information saved to the photo library, Files, a sharing destination, or a backup must be deleted by the user.

To request access, correction, deletion, or other rights available under applicable law for information processed by external services, contact the address in Section 10. The Developer may request information necessary to identify the relevant data.

8. Security

The Developer takes reasonable measures to prevent unauthorized disclosure, loss, or damage of information handled by the App. However, the Developer cannot guarantee the complete security of internet communications, devices, storage locations in Files, or other systems.

9. Changes to This Policy

The Developer may update this Policy in response to changes in law, the App, or external services. Material changes will be communicated by reasonable means, such as through the App, the App Store listing, or this page. An updated Policy takes effect when posted on this page or on another date specified by the Developer.

10. Contact

For questions about this Policy or the handling of user information, contact: