Privacy Policy
Updated October 5, 2026
Segmara collects limited account and email records to run its free research tracker. Segmara Pro checkout and billing run on Whop. Segmara does not accept documents or collect payment credentials on public pages. Segmara also keeps the records of its closed share inquiry and account credit flows, described below; those flows no longer accept new requests.
Information Collected
If you create an account or join the free email tracker, Segmara stores your email address, the name you enter (if any), the company you chose to follow (if any), your acceptance of the terms, the campaign fields described below, and sign-in data: a password hash if you set a password, or a passkey public key if you add a passkey. Do not submit SSNs, account numbers, wallet addresses, payment details, government IDs, or documents.
Segmara Pro And Whop
Segmara Pro checkout, billing, and the members forum run on Whop. Whop handles the information it needs for those services under its own terms and privacy policy, and shares membership details with Segmara as the seller: your email address, plan, order amount, and the card brand and last four digits shown in the seller dashboard. Your full card number is entered only on the provider-hosted checkout page and never touches Segmara's servers.
Records From Closed Flows
Segmara no longer accepts share inquiries and no longer sells account credits. Before these flows closed, the contact form could collect name, email, investor profile, self-reported eligibility category, message text, and consent acknowledgement, and a hosted checkout handoff could record the selected account top-up amount, provider status, checkout session metadata, payment status metadata, share-inquiry details, and manual credit status. Those records are kept. Card and bank details were entered only on the provider-hosted checkout page and were not collected by Segmara public pages.
Operational Logs
The hosting stack may process basic technical request metadata needed to serve and secure the site. Account records and the records from closed flows are stored locally on the project VPS.
Cookies And Analytics
Public campaign pages may store campaign parameters, click identifiers, landing path, and referrer host in browser session storage and protected form fields so admins can understand which campaign produced a signup. Project-owned advertising measurement tags may also be enabled to understand whether ads load the site and whether visitors start a checkout or account flow. When enabled, conversion tags may receive event names, event IDs, and USD values for hosted checkout status pages. These tags are limited to campaign measurement and conversion attribution; they are not a securities application, KYC check, brokerage instruction, or document submission workflow. Cloudflare Web Analytics automatic injection is disabled for this zone.
When measurement is enabled, the site uses these tags. The Meta Pixel reports page views and tracker-signup, checkout-status, and purchase events with event names, event IDs, page URLs, and order values. The Meta Conversions API sends the same signup and purchase events server-side with a hashed email address, hashed account ID, browser user-agent, Meta click and cookie IDs where present, and order value; the browser IP address is included only when explicitly enabled. The Google Ads tag reports conversion events with value, currency, and order ID, and hashes the account email in the browser for Enhanced Conversions before sending. The Whop pixel reports page views and completed tracker signups on the free tracker pages only. Each tag loads only when its project ID is configured.
Segmara also uses a first-party segmara_visit cookie for up to 30 days to distinguish anonymous browsers and group activity into short sessions. The server stores only a shortened one-way hash of the random cookie value with funnel events; it does not store the raw cookie value, IP address, or browser user-agent in those event rows. This browser count is used for aggregate traffic quality and is not treated as a unique-person identity. Signing in sets a first-party session cookie that keeps you logged in.
Use Of Information
Account data is used to run your account and send the tracker emails you signed up for. To stop tracker emails, reply STOP to any of them. Share inquiries received before that flow closed were used to understand inbound interest and decide whether to follow up. They are not investment applications, KYC submissions, brokerage instructions, or purchase orders.
Contact
For privacy questions or data requests, contact [email protected]. For general support, contact [email protected]. Segmara is an independent research service, not a broker-dealer, investment adviser, or issuer.