Information we handle
- Master-account identity and profile information.
- Affiliate enrollment, creator code, referral destinations, and program status.
- Attribution evidence, qualifying conversions, commission ledger entries, reviews, and payouts.
- Security and abuse-prevention signals such as IP, user agent, timestamps, request provenance, and failed verification results.
How we use information
We use this information to operate accounts, route users to products, attribute genuine referrals, calculate and review commissions, prevent abuse, support users, comply with law, and maintain auditable business records.
Stripe Connect
Stripe receives identity, tax, bank, and verification information in its hosted flows. We store limited connected-account identifiers, requirement summaries, payout readiness, transfers, and reversal records needed to operate the program. We do not ask affiliates to enter tax identifiers or verification documents into this portal.
Cookies and referral tracking
Essential cookies support authentication and referral attribution. A referral cookie is evidence of a visitor's navigation, not proof of a payable conversion. Blocking or clearing cookies can prevent attribution. Optional analytics, if introduced, will follow the applicable consent policy.
Service providers and retention
The active architecture uses AWS for account infrastructure, Cognito for identity, DynamoDB for source-owned records, Stripe for billing and connected payouts, and Cloudflare Turnstile for human-verification signals. Records are retained only as needed for operations, security, disputes, accounting, tax, and legal obligations.
Your choices
Account access, correction, deletion, and privacy contact paths will be published before production launch. Some financial, fraud, and legal records may need to be retained after account closure.