Plant Check Journal Android Privacy Policy

Plant Check Journal is published by 芜湖新思路网络科技有限公司 (newidea). For privacy requests, email caoqun6666@gmail.com.

Your journal and cloud account

You can record plants, care history, notes, reminders and selected photos locally without an account. The Android app initializes Firebase and checks for an existing session at startup. If you choose Google sign-in, Firebase Authentication can create a Plant account and provide the account ID, email address and available profile details.

When signed in, Plant can automatically synchronize your journal and upload photos you select when saving a plant. The service uses plant names, room labels, notes, care history, dates, settings and photo references to back up and restore the journal. An upload can include the image, file name or type and metadata in the image. Older photos may not be eligible for private cross-device recovery. Android backup and device transfer are separate and depend on your device settings.

Services and technical data

We use Google and Firebase for sign-in, our hosted Plant API and PostgreSQL for journal snapshots, and Cloudflare R2 for cloud photos. Plant protects its API requests and signed photo uploads in transit with HTTPS. Firebase documents HTTPS protection for its Android SDK traffic. The private photo service checks account ownership before returning an eligible image.

Configuration, schedule and version checks can occur without signing in. Version checks include app version, build, platform and channel. Hosting and authentication services can process IP addresses and technical request information. Firebase Authentication documents processing IP addresses, user agents and app identifiers for service operation and security.

Advertising and remote product analytics features are disabled in this paid Android version. The app package includes shared advertising and analytics components. Google Play processes the download purchase. Plant does not receive your payment-card details. No in-app purchases or subscriptions are offered in this version.

Deletion and retention

You can request deletion of your Plant account and its associated cloud data in Account settings or through the account and data deletion page, including after uninstalling. We verify that you control the account before taking action. The request covers the Plant account, backed-up journal and associated cloud photos. Support will explain the result and any records retained for security, recovery or legal reasons. The request does not delete your Google account or original files stored on your device.

Live journal and photo data are stored to provide cloud backup while you use the account. Account deletion is handled separately from device storage. We may keep a minimal account marker to prevent deleted data from being recreated by old synchronization or backups. The production offsite backup archive containing Plant snapshots is subject to a 30-day object expiration rule. Firebase applies its own authentication retention policy.

Operational logs are rotated by volume or archive count, depending on the service. We keep support correspondence and the minimal request record needed to verify and resolve requests, document the result and handle required exceptions. These records, live photos and account data do not all have the same retention period.

For questions about this policy or your Plant account, contact Plant support.