Under the Hood

When you opt in, creating or updating a plant or a log does two things within the same database transaction: it saves your record, and — if the plant has enough information and you haven't opted out for that plant — it queues an anonymised copy in an outbox table. A background worker polls that queue on a short interval and posts new events to the PlantDB API. If PlantDB is temporarily unreachable, nothing is lost: the event stays queued and is retried automatically on a later pass, up to a limited number of attempts. Your user identity is never part of the payload.

• Eligible events are queued alongside the write that created them, so nothing is lost if delivery fails.
• Delivery happens asynchronously — a background worker polls the queue and posts new events to the PlantDB API.
• Failed deliveries are retried automatically, up to a limited number of attempts, before being marked as failed.
• Your user identity is deliberately left out of every payload. Your GardenLog user ID and account details are deliberately excluded from every PlantDB payload.

GardenLog stores a username, an email address, a securely hashed password, and the garden data you create — plants, zones, logs, reminders, propagation records, and preferences. There's no advertising, no selling of user data, no cross-site tracking.GardenLog does not use advertising or cross-site tracking and does not intentionally collect behavioural analytics beyond operational logging. PlantDB sharing is opt-in and excludes your user identity. See the privacy summary on the homepage.