Privacy Policy

1. Introduction

This Privacy Policy describes how StemlyHQ ("we," "us") handles information in connection with our website and software service for wedding and event florists. It applies to florists and other users of the Service, and explains how florist-entered client information is treated. By using the Service, you acknowledge this Policy. Related terms of use are in our Terms of Service.

2. Who this Policy covers

Florist subscribers and account users create StemlyHQ accounts and enter business and client data into their workspaces.

Clients and couples may interact with florist-configured public surfaces (such as inquiry forms, questionnaires, or share links). Florists decide what to collect from their clients and are responsible for that collection. If you are a couple with questions about data a florist holds about you, contact that florist first.

3. Information we collect

We collect categories of information needed to operate StemlyHQ, including:

• Account information — such as name, email address, and authentication credentials (passwords are handled by our authentication provider)
• Business profile and settings — such as business name, contact details you choose to store, branding (for example logo), templates, workflow preferences, and payment-related studio settings
• Workspace content — client and event records, questionnaires and responses, quotes and proposals, design/production materials, orders, financial notes, files and images, and similar content you or your invited users enter
• Public form and share interactions — information submitted through florist inquiry forms, questionnaires, or other public links the florist enables
• Waitlist and marketing interest — when you ask to stay in the loop or join a waitlist, information you provide such as your email address, and optionally name, business name, location (for example city/state), and approximate wedding volume when those fields are collected
• Subscription and billing records — subscription status, plan/interval identifiers, and Stripe customer or subscription identifiers associated with your StemlyHQ subscription (we do not store full card numbers on our servers)
• Stripe Connect account status — identifiers and onboarding/charges-enabled status for florists who connect Stripe to accept client payments
• Technical and usage data — such as IP address and basic request metadata in server logs, browser/device information typical of web apps, and cookies or similar technologies described below
• First-party conversion and attribution data — limited first-party records used to understand Stemly's own signup funnel, such as aggregate website and subscribe-page visit counts, whether Checkout was started, and first-touch marketing context (for example UTM parameters, landing path, and referring domain) associated with a visitor cookie and later with your account when you sign up. That first-party funnel does not use advertising pixels or a third-party analytics SDK.

On the public homepage, Features page, and Subscribe page — and for a brief moment after Stripe Checkout when a trial has actually started — we load a Google Ads tag. It is there so Google can attribute an ad click and measure whether that click leads to a confirmed Stemly trial start. We do not use Google Analytics (GA4) or another product-analytics tool to watch how florists use the workspace, and we do not load this tag inside the florist workspace.

4. How we use information

We use information to:

• Provide, maintain, secure, and improve the Service
• Create and authenticate accounts and manage sessions
• Process StemlyHQ subscriptions and related billing events
• Enable florist features such as client workspaces, sharing, questionnaires, and Connect checkout flows
• Send transactional messages (for example account confirmation, payment or inquiry notifications) when configured
• Respond to support requests and communicate about the Service
• Monitor reliability, prevent abuse, and comply with legal obligations
• Understand first-party conversion performance (for example whether visitors reach subscribe, create accounts, start Checkout, and become paying members) and first-touch acquisition context for Stemly itself — not to build advertising audiences
• Measure whether Google Ads leads to a confirmed trial start. That signal is advertising attribution only. We do not attach a payment amount, and we do not use workspace activity to build advertising audiences

5. How we share information

We do not sell your personal information. We share information only as needed to operate the Service, including with:

• Infrastructure providers — such as database, authentication, file storage, and application hosting providers that process data on our behalf
• Stripe — for subscription billing and, when you enable it, Connect client payments (see Section 6)
• Email delivery providers — to send transactional or support-related messages when email is configured
• Anthropic — to provide receipt features. When receipt scanning is used, we send Anthropic the receipt image you submit so it can read the vendor, date, total, and line items. When Stemly compares a saved receipt with that wedding's recipe, we send Anthropic the receipt line items (description, quantity, and prices) and the flower and supply names, quantities, and unit prices from that recipe, so it can return an advisory note if a purchased price looks higher than the quoted unit price. Anthropic processes that information for us, as a service provider, to perform the feature. We do not use these requests to make one florist's private business information available to another florist.
• People you authorize — such as users on your account, or clients who access a share link or form you enable
• Google Ads — on the public pages described above, the Google Ads tag may receive an ad-click identifier already stored by Google in the browser, and a trial-start conversion that includes the Stripe subscription id and no payment amount, so Google can tell whether an ad led to a trial
• Legal and safety — when we believe disclosure is required by law, or to protect the rights, safety, or integrity of the Service and its users

We do not sell personal information, and we do not build advertising audiences from florist workspace activity.

6. Payments: StemlyHQ subscriptions vs client Connect payments

StemlyHQ subscription billing. When you subscribe, Stripe processes your payment for the software subscription. Stripe receives payment method details according to its own policies. We receive limited billing metadata needed to entitle and manage your account (for example subscription status and Stripe customer/subscription identifiers).

Florist client / wedding payments (Stripe Connect). If a florist enables Stripe Connect, client card payments initiated through StemlyHQ are processed as direct charges on the florist's connected Stripe account. Those funds are handled under the florist's Stripe relationship; StemlyHQ is not the florist's bank and does not hold client wedding funds as a payment processor. We may store payment status and related metadata in the florist workspace so the florist can track deposits and balances.

7. Client and couple data entered by florists

Florists enter and control client, couple, and event information in their workspaces. Florists are responsible for having an appropriate legal basis and notices for that collection, for the accuracy of what they store, and for responding to client requests about that data where applicable. StemlyHQ processes that information to provide the Service to the florist (as a service provider / processor in that context), not to market independently to couples.

8. Cookies and similar technologies

We use cookies and similar technologies that are needed for the Service to function, including authentication and session cookies from our auth provider, limited preference cookies (for example remembering a selected subscription billing interval during checkout), and a first-party visitor cookie that preserves first-touch acquisition context (UTM/referrer/landing path) across signup and email confirmation so we can attribute Stemly subscriptions to the channel that first brought someone to the site. We also use short-lived session markers so marketing and subscribe visit counts are not inflated by page refreshes. Those first-party cookies are for Stemly's own funnel. Separately, the Google Ads tag may set Google's advertising cookies on the public pages listed above so Google can connect an ad click to a later trial start. We do not load Google Analytics or other product-analytics SDKs.

9. Data retention

We retain account, workspace, waitlist, and billing-related records for as long as needed to provide the Service, maintain backups and security, resolve disputes, and meet legal or accounting requirements. Retention periods vary by data type and operational need; we do not publish a single fixed retention schedule for all data. If you close your account or request deletion, we will take steps consistent with our capabilities and legal obligations; residual copies may remain in backups for a limited period.

10. Security

We use reasonable administrative and technical measures designed to protect information, including access controls and encrypted transport (HTTPS). No method of transmission or storage is risk-free, and we do not claim absolute security or specific security certifications.

11. Your choices

Depending on your situation, you may:

• Access and update certain account and profile information in the Service
• Manage or cancel your subscription through the billing controls we provide (typically via Stripe)
• Disconnect or manage Stripe Connect through the integrations we expose and your Stripe account
• Contact us at support@stemlyhq.com to ask questions about privacy or request account-related assistance

Clients of florists should contact their florist for access or correction of client records the florist controls.

12. Children's privacy

The Service is directed to businesses and adults. We do not knowingly collect personal information from children under 13. If you believe we have collected such information, contact support@stemlyhq.com and we will take appropriate steps to delete it.

13. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. We will post the updated Policy on this page and revise the effective date. Continued use of the Service after an update means you acknowledge the revised Policy, except where applicable law requires otherwise.

14. Contact

For privacy questions, contact support@stemlyhq.com. You may also use our Contact page.