Privacy Policy

Tropical Roots Plant Manager · Last updated: May 7, 2026

Tropical Roots Plant Manager ("the App") is a free, open-source plant cultivation tracker. This policy explains what data the App handles and how. The short version: your data stays on your device unless you explicitly choose to back it up or sync it.

What we collect

Nothing on our servers. The App is a static web application. We operate no backend that receives your cultivation records, photos, or personal information. Records you create — plants, feedings, harvests, IPM events, photos, environment readings, and so on — are stored locally on your device using standard browser storage (localStorage). If you choose to enable Cloud Sync, a copy is also stored in a Firebase project you configure and control.

No analytics. The App does not include third-party analytics scripts (Google Analytics, Facebook Pixel, etc.). We do not track which features you use, when you use them, or how often.

No advertising. The App contains no advertising of any kind and does not share data with advertisers.

Optional integrations you control

The App offers several integrations that send data outside your device. None are enabled by default; each requires you to opt in.

• Cloud Sync (Firebase Realtime Database). If you enable Cloud Sync via the gear menu, the App synchronizes your records with a Firebase project that you configure with your own credentials. Data flows directly between your device and Google's Firebase servers; we do not see or store it. Disable Cloud Sync at any time to stop synchronization. Disabling does not delete data already synced; you must clear it manually from your Firebase console.
• Weather data (Open-Meteo or your configured provider). If you enable weather features, the App sends your approximate location (or a manually-entered city) to a weather provider to fetch forecasts. The location is not stored on our side.
• Pest Identification (Google Cloud Vision API). If you configure a Google Cloud Vision API key and use the Pest Identifier, the photo you submit is sent to Google's Vision API for analysis. The API key is yours, billed to you, with usage governed by Google's terms.
• Data export. Exporting a backup creates a JSON file on your device (or, if you enable encryption, an AES-256-GCM encrypted file). You choose where to save or share this file. Importing reverses the process.

Photos and media

Photos you attach to journal entries are resized client-side and stored locally as base64 data inside your browser. They are not uploaded to any server unless you have enabled Cloud Sync (in which case they go to your own Firebase project) or used the Pest Identifier (in which case the specific photo you submit is sent to Google's Vision API for that single request).

EXIF data

When you upload a photo, the App reads the photo's EXIF capture date so the journal entry can be timestamped accurately. The photo file is then resized via canvas, which strips EXIF metadata in the process. The resized photo stored in the App contains no EXIF data.

Browser permissions

• Storage: required, for saving your records on your device.
• Notifications: optional, for task and feeding reminders. Granted only if you opt in.
• Camera/file access: used when you attach a photo, via the standard browser file picker. The App never accesses the camera or files in the background.
• Location: used only by optional weather features, only when enabled, and only when fetching a forecast.

Children

The App is not directed at children under 13 and does not knowingly collect data from children.

Open source

The App's source code is available under the GNU GPL-3.0 license. You can audit, modify, or self-host it. Source: github.com/magikh0e/PlantManager.

Changes to this policy

If this policy changes materially, the "Last updated" date at the top of this page will be revised. Continued use of the App after changes constitutes acceptance.

Contact

Questions about this policy can be sent to the email address listed on tropicalrootsmaui.com.

This privacy policy is provided as a template based on the App's actual behavior and is not legal advice. If you operate the App under a different configuration (for example, you've added analytics or modified the Cloud Sync flow to use your own backend), update this policy to reflect those changes before publishing.