pCpodCARTEL
Founder offer Terms Privacy Beta guarantee
Account

podCARTEL and podOS

Privacy notice

What information the public site and account-first purchase flow use, where it goes, and why.

Last updated August 11, 2026

1. Scope

This notice covers the podCARTEL marketing site, founding seller queue, referral flow, podOS account and license handoff, and support communications. A seller’s installed podOS store runs in that seller’s own Cloudflare account; the seller controls the customer and store data created there.

2. Information used by the flow

  • Queue and referral information: the email address you submit, referral and campaign codes, reward progress, timestamps, and any optional seller or store details supplied through a form.
  • Account information: identity and verified-email information managed through Clerk at account.podcartel.com.
  • Purchase evidence: verified account email, Stripe Checkout Session and PaymentIntent identifiers when present, payment status, amount, currency, product and offer codes, and bounded Stripe event summaries used to verify and maintain the license.
  • Attribution and security information: landing page, referring page, UTM or paid-click fields, browser user agent, country reported by Cloudflare, and a one-way hash of the requesting network address for basic signup throttling.
  • Support information: the message and account context you choose to provide when asking for help or a refund.

Payment-card details are entered into Stripe Checkout and are not stored by this marketing site. The marketing webhook stores bounded purchase summaries rather than raw Stripe webhook payloads or Checkout URLs.

3. Why the information is used

The information supports the founding seller queue and rewards, campaign attribution, duplicate and abusive-signup controls, account authentication, purchase and license verification, installer access, onboarding follow-up, support, refunds, and operational recordkeeping.

4. Service providers

Cloudflare hosts the marketing site and its marketing records. Clerk provides account authentication. Stripe provides hosted Checkout and payment processing. If onboarding or milestone automation is enabled, the relevant queue or milestone details may be sent to the configured email or automation provider. Each provider handles information under its own terms and privacy practices.

For payment-specific details, review Stripe’s privacy policy. Account authentication is also subject to Clerk’s privacy policy.

5. Cookies, browser storage, and retention

The public site uses first-party referral and attribution cookies for up to 30 days. The referral experience also uses browser storage to remember the referral state on that browser. You can remove these values using your browser controls.

Marketing lead, referral, purchase-evidence, account, and support records may remain while the founding seller program, license, account, support, security, or accounting record is active. No shorter fixed public deletion schedule is currently represented.

6. Questions and requests

You can choose not to join the queue or purchase. You can also clear the first-party cookies and browser storage described above. For a question or request concerning your information, use support in the signed-in account portal or email support@podcartel.com. Some purchase, security, accounting, or license records may need to be retained.

7. Notice updates

When this notice changes, the “Last updated” date on this page will change. The current notice remains linked from the public offer and site footers.

pCpodCARTEL

Buy-once storefront software for independent print-on-demand sellers.

Terms Privacy Beta guarantee Contact

© 2026 podCARTEL. All rights reserved.