Privacy, plainly
Privacy policy
Last updated November 2, 2026
This page describes the information handled by the Herbwise website and the current education-only iOS and Android app. We describe what the source code shows and call out where a setting or provider controls what happens.
Information you provide
If you create or sign in to a Herbwise account, the account system processes your email address, sign-in credentials, and any profile details you provide, such as a name. Sign-in is provided by Convex Auth and uses the same account system on the website and in the native app.
The Plant Research Notes request asks for your name and email address so the requested link can be sent. That request is sent through the MadeThis notification service to Herbwise and to the email address you provide. Please do not include health or other sensitive details in that request or in email to support.
Information processed to provide the service
Herbwise uses a Convex backend for account and service data. Depending on the features you use, this can include account and authentication records, account identifiers, and access or plan status needed to provide the library and account features. The backend schema also supports workspace names, membership roles, and invitation email addresses where those features are used.
Plant and historical-use content is included in the app and website. Searches in the current native app are matched on your device. The website also filters its library in your browser. The web app may send account or access requests to the backend, but the search text is not an argument to those requests in the current implementation.
The native app stores authentication session tokens in the device's secure credential storage. The website uses browser session storage for the education flow and safety-note acknowledgement. When website analytics is configured, its library may also use browser local storage and a cookie. You can clear browser storage in your browser settings; removing app data or uninstalling the native app may remove locally stored session information.
Analytics and diagnostics
The website source includes PostHog analytics. It starts only when an analytics key is configured for the website. When enabled, the code captures page views, automatic page interactions, and events such as library, pricing, and checkout-intent activity. It can use a browser identifier and session identifier, and the website can add those identifiers and campaign tags to a hosted checkout link for attribution. The actual deployment setting is controlled outside the source repository, so we cannot confirm from the code alone whether analytics is enabled in every environment.
The current native app source does not include an analytics or crash-reporting SDK. We did not find a separate diagnostics collection feature in the application code. Hosting and backend providers may produce operational logs; their exact contents and retention are controlled by those providers and are not specified in the app source.
Checkout and outside links
If you choose a paid web offer, the website sends you to MadeThis's hosted checkout. Payment information is entered with that checkout, and checkout or payment providers may handle it under their own privacy terms. Herbwise receives service or access information needed to provide the offer; the website code does not collect payment-card details in its own forms.
Plant entries include links to their references and sources. Opening one takes you to that source's website or service, which has its own privacy practices. This policy does not describe those external services.
How information is shared
Information is shared with service providers involved in operating the features above, including Convex for account and application data, MadeThis for the worksheet email request and hosted web checkout, and PostHog only when website analytics is configured. The code reviewed does not show advertising networks or sale of personal information. A checkout provider or external source site may receive information when you choose to use that service.
Retention, access, and deletion
The application source does not set a general retention schedule for account, request, or analytics data. Browser session values are kept by the browser for the session; analytics storage follows the configured analytics behavior and your browser settings. Server-side retention and backup periods are managed by the relevant providers and are not stated in this codebase.
You may email us to ask what account information is associated with you, request a correction, or ask us to delete information. There is no in-app account deletion or self-service data export flow in the current app. We will review your request and let you know what we can do; we cannot promise deletion from provider backups or records that the service is required to retain.
Education-only use
Herbwise is for education only. It does not diagnose, treat, prescribe, or recommend a tincture, and it is not medical advice or a replacement for care from a qualified professional. Please avoid sending personal health information to Herbwise. For health concerns, medicine interactions, pregnancy or breastfeeding, or severe or worsening symptoms, contact a qualified clinician or pharmacist or seek urgent care as appropriate.
Contact
For privacy, account, or general support requests, email team@herbwise.madethis.app. You can also visit our support page.