Local by default
Use the garden without creating an account
Plant profiles, journal entries, photos, care history, spaces, search, and organization are designed to work locally. You do not need an account to build and use that garden.
A local-first design does not mean every feature is offline. It means the boundary is explicit: the core record stays on the device unless you choose an action that needs an online service.
Online identification
A selected photo leaves the device only when you request a scan
Plant recognition requires a network connection. When you request identification, Sprignote sends the selected image and the minimum technical information needed to process it to the identification service and its plant-recognition provider.
The rest of the journal is not bundled into that request. Identification results remain suggestions, and safety-critical decisions still require a qualified local expert.
Optional services
Sync and analytics wait for a deliberate choice
Creating an account does not automatically upload the local garden. Private household cloud snapshots begin only when sync is enabled. Account data supports sessions, household membership, entitlement status, and the cloud snapshot you choose to create.
Product analytics are off until you opt in. Allowed events exclude plant names, journal text, photos, email, and account identifiers. The App Store handles payment details, while RevenueCat verifies subscription access. On iOS, Apple Ads attribution is measured separately through Apple and RevenueCat and does not include your garden content.
Control
Export, back up, delete, or stay entirely local
Sprignote can create a readable archive for backup and restore. You can delete individual local records, leave cloud sync off, decline analytics, change device permissions, or delete a cloud account.
Deleting a cloud account removes its cloud account data and owned backups, but it does not silently erase the local garden on your device or cancel an app-store subscription. The full legal detail remains in the Privacy Policy.
Choose deliberately
Match each privacy choice to the feature you actually need
You can keep a garden entirely local and still create plants, add photos and journal events, search, organize spaces, log care, and make a backup. If you want an online identification, select only the photos that belong in that request. If you later want household sharing, enable cloud snapshots as a separate choice rather than treating sign-in as blanket permission to upload the garden.
Device permissions are similarly specific. Camera or photo access supports the image you choose to add; notifications support reminders you enable. You can review or revoke those permissions in system settings, though the associated feature may stop working until access is restored.
Before exporting or sharing a backup, remember that it can contain the plant names, photos, notes, spaces, and history you recorded. Store or send that archive with the same care you would use for any personal collection. Sprignote can define its own service boundary, but it cannot control what happens after you deliberately copy an export elsewhere.
- Stay local for the core garden
- Select only the photos needed for a scan
- Enable sync separately from sign-in
- Protect exported archives after they leave the app