How the forms work

Privacy, in plain language.

Form submissions are saved in the site's D1 database for review. Current form handlers validate and store submissions; they do not email, automatically forward, notify, or sell leads. An authorized operator may manually share an inquiry with the garden named on the form or a relevant partner to help respond, as described in the form consent. This does not guarantee a response or booking. We do not ask for payment information through these forms.

What we collect

Bloom signups store your email, state or ZIP, optional flower and garden, consent text and time, source page, status, a salted IP hash, and a bounded browser identifier. They stay pending until a future email confirmation process is added. No alerts or confirmation emails are sent now.

Inquiries store the garden, inquiry type, name, email, optional phone and event details, message, consent, source page, status, and creation time. Listing requests store the garden and contact details, suggested information, optional photo album link and photo permission, consent, source page, status, and creation time. Both also store a salted IP hash and a bounded browser identifier. The database stores a salted hash, not the raw IP address.

Directory activity

Website, phone, and directions clicks may be recorded with an internal ID, garden, click type, page, timestamp, salted IP hash, and bounded user-agent string. Rejected requests are not saved with their form payload; the service stores an aggregate rejection reason, count, and last-rejected timestamp.

Page visits are counted without cookies. A visit record contains the day, page path, referring website host, and campaign tags if present. It does not store an IP address. The visit counter respects Do Not Track.

Some tour links are affiliate links; they are marked near the link, and Gardenhopping may earn a commission if you use one.

Sharing and sale

The current handlers only validate and store submissions. They do not implement an email, automatic forwarding, notification, or lead-sale workflow. As stated in the inquiry consent, an authorized operator may manually share an inquiry with the named garden or a relevant partner; the code does not select or notify a recipient. No paid-referral or lead-sale process is implemented. Any commercial sharing, sale, or additional recipient must be decided and disclosed before it is enabled.

Saved gardens and favorites

Saved gardens and flower favorites are stored in your browser first. If you choose to keep your list with your email, we store a salted, one-way hash of that email (not the email itself) with the garden and flower names you saved, so your list comes back on your next visit or another device. Your browser keeps a signed key for the list and remembers the email you typed so it can show it to you. We don't send email or marketing from this. Entering the same email anywhere brings the list back. To delete a list, email us from the contact page.

Retention and deletion

We keep signups, inquiries, listing requests, and click records for at least a year. You can ask us to delete your information at any time through our contact form.