This Privacy Policy explains how WHALECOMMERCE LLC ("WCX", "we", "us"), 1501 South Greeley Hwy, Ste C #1241, Cheyenne, WY 82007, USA, handles personal data. It has two parts:
- Part A covers this website, wcx.digital.
- Part B covers the WCX platform, which Sellers use to run their stores.
For questions or requests, write to support@wcx.digital.
Part A. This website (wcx.digital)
A1. What we collect: nothing. This website uses no cookies, analytics, advertising or tracking pixels, third-party scripts, forms or accounts. It stores nothing in your browser to recognize you.
A2. Delivering the pages. Like any website, the servers that deliver this one (run by our hosting provider, Cloudflare) receive the information every browser sends with each request, such as your IP address, the page you asked for and your browser type. This is used only to deliver the page and protect the site against attacks. We do not use it to identify you or build a profile, and we do not add analytics to it.
A3. If you email us. When you write to support@wcx.digital (for example, to request early access or about a purchase), we receive your email address, your message and anything you choose to include.
- We use it only to answer you and handle your request, including reviewing an early access request.
- Where the GDPR or similar laws apply, our legal basis is our legitimate interest in answering you. For early access requests, it is taking the steps you ask for before an agreement.
- Our email service provider stores these messages for us.
- We keep each conversation as long as needed to handle it, and delete it 24 months after the last message. We keep it longer only if the law requires it, if it is needed for a dispute, or if it becomes part of a Seller account (Part B).
- We never sell it or use it for marketing.
Part B. The WCX platform
B1. Our role
- Sellers' account data: WCX decides how this data is used, so we are the controller.
- Data about Buyers and visitors of a store: each store belongs to a Seller. The Seller is the controller of its Buyers' and visitors' personal data. WCX processes that data on the Seller's behalf and on its instructions, as a processor (also called a "service provider"). Stores show the Seller's brand and the Seller's own privacy notice.
- If you bought from a store, contact that store first. You can also write to us: we pass your request to the Seller and help them answer.
B2. Data about Sellers and their teams (WCX as controller)
- Account: name, email address, role, and the organizations and stores you can access. Your email is also used to sign you in through Cloudflare Access.
- Business and store details: brand name, logo and colors, store settings, domains, and the sender details used for emails (display name, reply address, postal address and support contact).
- Connected accounts: the identifiers of your Processor accounts (Whop or Stripe) and of the advertising accounts you connect (Meta, TikTok, Google, X).
- Tokens for connected advertising accounts are stored encrypted (AES-256-GCM) and deleted when you disconnect. Where the network allows it, we also revoke them with the network.
- Payment-account keys are kept in our secrets storage, not in the database.
- We do not store your bank details. The Processor handles payouts.
- Business data for your dashboard: sales, refunds, disputes and fees reported by the Processor; spend, campaign names and campaign IDs from your advertising accounts. Data from X is kept for at most 90 days.
- Activity records: an audit log of significant actions (who changed what, and when). It records which fields changed, not their values.
- Your messages with us.
We use this data to provide and secure the Service, manage sign-in and permissions, give support, bill fees that were agreed, and comply with the law. Our legal bases are: performing our agreement with you; our legitimate interests (security, fraud prevention and improving the Service); and our legal obligations.
B3. Data about Buyers and visitors
We process this data as a processor for each Seller (B1).
| Data | What it includes | How it is protected |
|---|---|---|
| Contact | Email address (needed to deliver the purchase). Phone number, only if one is provided. | Before payment, the email is kept encrypted (AES-256-GCM) in the checkout session, and deleted if the session expires unpaid. After payment, it is kept readable only in the store's contact record, to send the Buyer's emails. Everywhere else it is kept only as a SHA-256 hash plus a masked form (e.g., "co•••@em•••.com"). The phone number is kept only as a hash. |
| Name and billing location | We may receive the Buyer's name and billing city, region, postal code and country from the Processor. | Kept only as hashes, except a first name the Seller imports from a previous platform, which is kept readable in the store's contact record to greet the Buyer in emails. |
| Purchase | Products, offers accepted or declined, amounts, currency, order status, refunds, disputes, access period, and the country used to choose the price. | Tied to the store and organization. Never visible to other Sellers. |
| Payment | The Processor's payment IDs and status, payment method type, card brand, last four digits and card country, as reported by the Processor. | WCX never receives full card numbers, expiry dates or security codes. For one-click offers, references to the saved payment method are encrypted and deleted when the offer window closes (24 hours at most). |
| Connection | IP address, browser (user agent) and approximate location from the connection (city, region, postal code, country). | Used in real time for security (bot checks and rate limits). Each visit also records the country, region (state or province), device type and browser family in readable form, for the Seller's reports; these records are kept for 13 months (B7). Within the visitor's choices, the IP address and full user agent are kept as temporary context for measuring conversions and deleted once sent, or after 7 days at most, and the city and postal code are kept only as hashes in that same context. None of that temporary context is kept if the visitor rejected advertising. |
| Measurement | A first-party visitor ID (cookie); arrivals from ads (UTM parameters and ad click IDs such as fbclid, gclid, ttclid or twclid); page-view, product-view and add-to-cart events; checkout and purchase events; a hashed external ID. | Follows the visitor's choices (B5) and the retention periods in B7. |
| Consent records | The choice made, the banner text version, the date, the region and a hashed IP address. | Cannot be edited. Kept as proof of the choice. |
| Library | Purchases and access rights, sign-in codes and session tokens, reading progress and bookmarks, file download events. | Access rights are linked to a hash of the email. Codes and tokens are stored only as hashes. Progress and bookmarks are saved without IP or browser. Purchased content is not stored on the device for offline use. |
| Emails sent and their delivery events (delivered, bounced, complaint), unsubscribes and suppressions. | Logs and send records use the email hash, not the address. | |
| Page analytics (per store; the Seller can turn it off) | How visitors use store pages: scrolling, sections seen, taps relative to page elements, errors and loading speed. On devices with a mouse, also cursor movement and hovers. In forms, which field had focus, whether it was filled or autofilled, and how much was typed, in broad bands. | Never records what people type or choose, page or form text, URLs with their parameters, IP addresses or device fingerprints. Some visits are kept in full so the Seller can review them step by step (scrolling, taps and which field had focus, without recording the page itself). |
If a Seller imports customers from a previous platform so they can reach past purchases in the library, those customers are stored the same way, except for the readable first name described above.
B4. Why we process it
On each Seller's instructions, we use this data to:
- run the checkout and post-purchase offers;
- deliver purchases and library access;
- send receipts, access codes and refund confirmations;
- send the Seller's marketing emails, only where the rules of the Buyer's country allow it, and always with a one-click unsubscribe;
- prevent fraud and abuse (bot checks, rate limits and protection against card testing);
- measure the Seller's advertising and send conversion events to the advertising networks the Seller connects, within the visitor's choices (B5);
- show the Seller sales, profit and page-analytics reports.
We also:
- keep a platform-wide suppression list (by hash) of addresses that hard-bounce or report emails as spam, so no store on WCX emails them again;
- apply an unsubscribe from one store to every store of the same brand.
We do not use Buyer data for our own marketing, and we do not sell it. Security checks such as bot detection and rate limits are automated and can temporarily block a request. If you think you were blocked by mistake, contact the store or us.
B5. Visitor choices on store pages
Stores on WCX apply each visitor's privacy choices automatically, based on the region of their connection and on the store's settings:
| Region | Before choosing | "Accept" | "Reject" | Global Privacy Control (GPC) or "Your privacy choices", if the store has turned them on |
|---|---|---|---|---|
| EEA; United Kingdom and its Crown Dependencies; Gibraltar; Switzerland; unknown locations | No advertising pixels, advertising cookies or server-side advertising events, and no page analytics | Measurement on | Nothing is sent | Nothing is sent |
| United States | Measurement on, in California too (unless the store turns on its banner there) | Measurement on | Nothing is sent | Limited use: only Meta (Limited Data Use) and TikTok (limited data use). Nothing is sent from the server to Google or X |
| Other countries | Measurement on, with a notice and an opt-out link | Measurement on | Nothing is sent | Opt-out: nothing is sent. GPC: the same limited use as in the US |
Also:
- In the United States, honoring Global Privacy Control and showing the "Your privacy choices" link are two store settings, off by default. Each store decides whether to turn them on, for example when a U.S. state privacy law applies to it. The banner for the EEA, the UK and Switzerland does not depend on these settings.
- A "yes" given to an earlier version of the banner text stops counting when the text changes. A "no" stays valid.
- If a visitor later picks a more restrictive choice, it applies to events not yet sent. We cannot recall data already sent to a network.
- The checkout page never loads advertising pixels or page analytics, and one-click offer pages never load advertising pixels. Checkout events are sent only from the server, and only within the visitor's choices.
- Within those choices, events sent to advertising networks can include: the event name and ID; value, currency and products; hashed email, phone, name and location; a hashed external ID; IP address and browser; ad click IDs and the networks' cookies. Google also receives the consent status with each event.
- Page analytics follows the analytics choice and is never shared with advertising networks. Where consent is required, it runs only after "Accept". In some regions it may run before a choice in an anonymous mode with no visitor identifier.
B6. Cookies on store pages
| Cookie | Purpose | Duration | When it is set |
|---|---|---|---|
st_vid | First-party visitor ID for measurement | 400 days, renewed on each visit | EEA, UK, Switzerland and unknown locations: only after "Accept". Elsewhere: unless the visitor rejects |
__Host-st_cs | Keeps the purchase session from checkout to the offers and thank-you page | Session | Always (needed for the purchase) |
__Host-st_consent | Stores the visitor's choice and the banner version | 400 days | When the visitor chooses |
__Host-st_at | Last arrival from an ad (UTM parameters, click IDs) | 90 days | Same rule as st_vid. Click IDs only as far as the choice allows |
__Host-st_lib | Members library session | 30 days | After signing in to the library (needed for access) |
_fbc, _fbp | Meta measurement | 90 days | Only with advertising consent or limited use |
_twclid | X measurement | About 390 days | Only with full advertising consent |
Cookies from TikTok and Google tags (e.g., _ttp) | Measurement by those networks | Set by each network | Only within the visitor's choices |
B7. How long we keep data
| Data | Period |
|---|---|
| Raw payment notifications from Processors (may contain the Buyer's email and phone) | 30 days |
| IP address, full user agent and hashed city and postal code (temporary context) | Until sent, 7 days at most |
| Saved payment-method references (encrypted) | Until the offer window closes, 24 hours at most |
| Email in an unpaid checkout session | Until the session expires |
| Ad click IDs | 90 days |
| Arrivals (with country, region, device type and browser family); page-view, product-view and add-to-cart events; inactive visitor records | 13 months |
| Visitor ID on purchase and checkout events | Removed after 13 months |
| Library sign-in codes (valid 10 minutes) and passes (valid 2 minutes) | Deleted 1 day after they expire |
| Library sessions (valid 30 days) | Deleted 30 days after they expire or after sign-out |
| Page analytics, raw data | 90 days in sampled full mode; 25 hours in count mode; 24 hours in anonymous mode |
| Page analytics, per-view summaries | 90 days |
| Page analytics, aggregated statistics with no visitor, IP or click ID | Kept |
| Consent records, unsubscribes and suppressions (hashes) | As long as needed to prove choices and honor opt-outs |
| Orders, payments, refunds, disputes, access rights, reading progress and contact records | While the Seller uses WCX, then as described in B8 |
| Logs | Contain no personal data |
B8. Deletion and other requests
- Buyers and visitors: contact the Seller of the store, or write to support@wcx.digital and we will pass your request on: we act on the Seller's instructions. When a Seller asks, we delete or de-identify the personal data we hold about that person for that store. The contact record keeps only a hashed email and an unsubscribe, so the person is not emailed again. We keep only what we must for legal, tax, accounting, fraud-prevention or dispute reasons. Our team handles each request and completes it within 30 days.
- Choices and unsubscribes: visitors can change their choice at any time with the store's banner or its "Your privacy choices" link, where the store shows them. Every marketing email has a one-click unsubscribe link.
- Sellers: you can ask to access, correct or delete your account data at support@wcx.digital. When a Seller leaves WCX, we delete its store data within 90 days after the relationship ends, or return it on request during that period, unless the law requires us to keep part of it.
B9. Service providers and other recipients
| Provider | Role | What they do |
|---|---|---|
| Cloudflare | Service provider to WCX | Hosting for the platform, store pages and this website; content delivery; file storage; queues; bot protection (Turnstile); Seller sign-in (Access); DNS and domain services |
| Neon | Service provider to WCX | Managed PostgreSQL database (AWS US East, N. Virginia, United States) |
| Postmark | Service provider to WCX | Delivers the emails stores send |
| Whop, Stripe | Payment processors used by the Seller, under their own terms and privacy policies | Payment processing, the wallets they offer (such as Apple Pay, Google Pay, PayPal or Stripe Link), fraud checks, payouts, refunds and chargebacks |
| Meta, TikTok, Google, X | Advertising networks, only if the Seller connects them | Receive conversion events only within the visitor's choices (B5), under the Seller's own agreements with them |
We may also disclose data when the law requires it, to protect rights and safety, or to a successor in a merger or acquisition, under this Policy. We will update this list when our providers change.
B10. International transfers
WCX is based in the United States. The database is in the United States (AWS US East, N. Virginia), Cloudflare processes data on its global network, and Processors and advertising networks may process data in the United States and other countries. Where the law requires safeguards for these transfers, we put in place mechanisms recognized by that law, such as the European Commission's Standard Contractual Clauses, or rely on a provider's certification (for example, Stripe states that it complies with the EU-U.S. Data Privacy Framework).
B11. Security
See our Security page. In short: HTTPS everywhere, card data handled only by the Processors, hashing and encryption, strict access control, and logs with no personal data.
B12. Sale and sharing
WCX does not sell personal data. Under some U.S. state laws, sending conversion events to advertising networks on a Seller's behalf can count as "sharing" for targeted advertising. Each store decides, with two settings that are off by default, whether to honor Global Privacy Control and show a "Your privacy choices" link. A Seller must turn them on where such a law applies to its store.
B13. Children
WCX is not directed to children. Sellers must not direct their stores to children under 13, or under the higher minimum age set by local law, and must not knowingly collect their data.
Your rights
Depending on where you live, you may have the right to access, correct or delete your personal data, or get a copy of it; to object to or restrict its processing; to withdraw consent; and not to be treated differently for using these rights. To use them, write to support@wcx.digital. We may need to verify your identity. For data held for a Seller's store, contact that Seller, and we will help them. You can also complain to your local data protection authority.
Changes
We will update this Policy when our practices change and show the new date at the top. We will notify Sellers of material changes by email or in the dashboard.
Contact
WHALECOMMERCE LLC · 1501 South Greeley Hwy, Ste C #1241, Cheyenne, WY 82007, USA · support@wcx.digital
Questions about this page? Write to support@wcx.digital.