Curated, verified, and enforced in code.
DEMO document — not legal advice
SANDBOX ONLY · All providers, evidence and sellers on this demo are fictional. No official affiliate, reseller, or partnership relationship with any real brand exists.
SubDock is designed to list only four fulfillment types: affiliate redirects, authorized redeem codes, provider licenses, and provider-approved invites. What today's sandbox actually verifies is enumerated below; anything not on this list is a real-launch gate, not a demo claim.
What the sandbox enforces today
- Database enums and server-side regex reject obvious submission types: passwords, cookies, sessions, bearer tokens, raw API keys, and VPN-assisted geo-circumvention language.
- Every offer must be tied to a pre-approved provider and SKU, an approved seller organization, and current sandbox authorization evidence — otherwise it is not publicly listable.
- The authoritative checkout transaction re-validates seller status, provider status, SKU approval, current evidence, stock, region and killswitches server-side.
- Sensitive offer edits return the offer to review.
- Redemption artifacts are stored as opaque references and masked in every read path.
What still requires real agreements
- "Officially authorized" claims for any real provider require executed affiliate, reseller, or provider-partnership contracts. The sandbox never asserts a real partnership.
- Provenance and authorization checks for real inventory need human review plus verifiable evidence, not automated regex alone.
- Real payouts, refunds and chargebacks depend on a live payments integration.
- KYC/KYB, tax onboarding and sanctions screening for real sellers are not performed in the sandbox.
Umbrella ban
Even outside the specific prohibited categories, SubDock refuses to broker any inventory that is:
- Unlawful, fraudulent, counterfeit, or IP-infringing;
- Restricted by sanctions or export controls;
- Funded by chargebacks or other reversible funding fraud;
- Malware / phishing / social-engineering related;
- In violation of the upstream provider's own terms.
Buyer protection (modeled)
- Simulated refunds when a demo delivery misses SLA or a demo code is reported invalid.
- Dispute flow with support review and simulated payout freeze while open.
- Redemption codes are masked in every UI surface and treated as secret references.