Privacy, stated clearly.

This Privacy Policy applies to the EnrichedFlows website, the waitlist form, account sign-up and sign-in pages, and the member experience available through EnrichedFlows. It describes information handled when you use those areas.

EnrichedFlows provides market research and signal-related tools. This policy does not change the separate terms, risk disclosures, or notices that may apply to those tools.

Account information. When you create or use a password-based EnrichedFlows account, the application receives the email address, password information, and required phone number you enter for account setup. The account data model may also store an account name, email-verification status or time, profile image, account role, onboarding status, and account creation information when those fields are used.

Optional SMS marketing consent. If you choose to check the SMS marketing consent box during password account sign-up, the application records your normalized phone number, consent, the consent text and version, and the time of your choice. This optional consent is separate from creating an account. You may reply STOP to opt out of marketing texts and HELP for help.

Waitlist information. The public waitlist form requests your name and email address and requires confirmation that you agree to receive launch and market-intelligence updates. The application records that consent, its timestamp, and the signup source.

Member workspace information. If you use member workspace features, the application may store workspace names, membership roles, invitation email addresses, and invitation status information needed to operate those features.

Watchlist and alert-preference information. The member experience lets an authenticated user save a ticker symbol, a watchlist item type, and an optional private note. It also stores whether the user has enabled or disabled available email, SMS, and in-app alert-preference channels. Saving a preference does not by itself mean that a particular delivery channel is active or that a message will be sent.

Billing-related workspace information. The application stores plan, subscription-status, trial, platform product, and checkout-link fields for workspaces. The EnrichedFlows storefront code does not include a payment-card form or collect card numbers, security codes, or bank account details.

The application uses account information to create and authenticate accounts, maintain a signed-in session, control access to protected member areas, and associate saved member data with the correct user.

Waitlist information is used to record your request for updates and to send the signup record through the platform notification endpoint used by EnrichedFlows. The code currently labels that notification as a subscriber record; it does not itself send a separate storefront email from the browser.

Workspace, watchlist, and alert-preference information is used to operate the features where you provide it. For example, watchlist entries are queried and managed only after the application identifies the signed-in user, and alert settings are saved as that user’s preferences.

If you opt in to SMS marketing during account sign-up, the recorded consent may be used for EnrichedFlows marketing text messages. SMS marketing is optional and is not required to create an account or make a purchase. Reply STOP to opt out and HELP for help.

The application also uses certain technical and analytics information as described below to understand site use and to attribute a checkout visit when analytics is configured.

EnrichedFlows uses authentication and session mechanisms required for protected areas of the application. The code also sets a short-lived, HTTP-only administrator access cookie only for the separate administrator area after a valid administrator token is supplied.

If EnrichedFlows has configured its PostHog environment variables, the site initializes the PostHog browser SDK. Its current configuration enables page-view capture, interaction autocapture, and browser persistence using both local storage and cookies. The sign-up pages also record sign-up-started and sign-up-completed events, and the pricing and checkout experience records relevant viewing or checkout events.

When present in a landing-page URL, the application saves theutm_source, utm_medium, and utm_campaign values in browser session storage. When a user selects a configured checkout link, the application adds those campaign values plus the current PostHog visitor and session identifiers to that checkout URL.

PostHog analytics runs only when its public storefront key is configured. Owner review required: confirm the final analytics configuration, cookie-consent approach, and any region-specific notice or choice requirements before launch.

The application uses Convex for its application data and authentication integration. It is deployed as a Next.js storefront, and the code includes optional PostHog browser analytics. These services process information as part of providing the configured application functions.

When a workspace has a checkout link, selecting it opens a checkout flow hosted by the MadeThis platform. The storefront forwards the analytics identifiers and campaign values described above to that checkout URL when available. Payment-entry handling occurs in the platform checkout flow, not in an EnrichedFlows payment form.

The waitlist route also sends a signed subscriber record to the MadeThis platform notification endpoint after the signup is saved. The record includes the waitlist name and email address.

Owner review required: confirm the final list of service providers, each provider’s role, and any required contractual or public disclosures before launch.

Signed-in members can manage the watchlist entries and alert-channel preferences available in the member experience. Removing a watchlist entry removes that entry from the application’s watchlist data.

For questions about your account, waitlist record, or information in the EnrichedFlows application, contact us at team@enrichedflows.madethis.app.

Owner review required: establish and publish the process for account deletion, correction, access, marketing opt-out, and identity verification requests before making commitments about those requests or their timing.

EnrichedFlows uses access controls in the application so that protected member routes require authentication and user-owned watchlist data is checked against the signed-in user before it can be removed. The waitlist notification request is signed before it is sent to the platform endpoint.

No internet-connected service can guarantee absolute security. Do not send payment-card information, brokerage credentials, or other sensitive information through the EnrichedFlows waitlist form or ordinary support email.

Owner review required: confirm the organization’s security program, incident-response process, and any security statements that may be appropriate before making additional public commitments.

We may update this Privacy Policy as the EnrichedFlows product or its data practices change. The updated version will be posted on this page with a revised effective date.

Questions about this policy can be sent to team@enrichedflows.madethis.app.