SteelThumb

SteelThumb policy

Privacy policy.

SteelThumb is designed around local-first garden data. This page separates public website interest, checkout and support records, optional community data, field-demo media, and customer garden photos or device data.

Website and interest data

  • Website traffic and basic analytics, if enabled
  • Email interest, preorder interest, and support messages sent to SteelThumb
  • Product preference, garden type, target season, and support context voluntarily provided by the customer
  • Catalog and policy pages that do not require a customer account
  • Public website pages should not list raw customer data

Future commerce data

  • Checkout/payment provider records if paid ordering is enabled
  • Shipping address, order status, refund/cancellation records, and support history
  • Optional community subscription data if community support is offered
  • Payment card details should be handled by the payment provider, not stored directly by SteelThumb
  • Per-order acknowledgement records should stay in the checkout provider or official order system

Local-first product boundary

  • Garden photos, maps, and device data should stay local by default
  • Public field-demo media should be reviewed before publication
  • Cloud dependencies, if any, must be optional or clearly disclosed
  • Private garden data should not be published without deliberate customer action
  • PlotTags, product photos, support screenshots, and field-demo images may reveal garden layout or location context and need customer review before public use

Support data boundary

  • Support messages may include photos, device state, product version, batch/date code, and setup details when the customer chooses to send them
  • Public field updates should not include customer names, addresses, emails, payment records, tracking numbers, or private support history
  • Customer names, addresses, emails, payment records, tracking numbers, and support history belong in private systems
  • Optional community spaces require separate privacy, cancellation, refund, moderation, and support terms before subscription checkout exists