Prize recipients are responsible for determining and satisfying their own tax obligations arising from prizes or other amounts they receive. CoreComp does not provide tax advice. CoreComp, an event organizer, a sponsor, or a payment provider may request tax information, report payments, or withhold amounts when required by applicable law. Nothing in this provision limits any reporting, withholding, recordkeeping, or other obligation imposed on CoreComp or another payer by law.

This language reflects CoreComp’s intended responsibility boundary, but it does not remove duties imposed on CoreComp or another payer. It still requires attorney and tax-professional approval.

A fixed dollar threshold must not be presented as the only trigger for tax collection or reporting. The responsible party, reporting form, withholding, threshold, and recordkeeping can depend on the tax year, recipient classification, location, prize type, payment structure, and federal, state, local, or international law.

CoreComp will not state that every U.S. recipient receives a particular form, that every international recipient uses one form, or that payouts below a displayed amount require no tax information. A qualified tax professional must configure current rules for the approved payout model.

The production workflow must determine who is legally paying the prize before asking a recipient for anything. It must keep event operations, recipient eligibility, provider verification, withholding/reporting decisions, and payment evidence separate and auditable.

A prize may be funded or paid by CoreComp, an event organizer, a sponsor, or another approved party. The official event rules and payout record must identify the responsible payer and must not shift that party’s legal obligations to the recipient by disclaimer.

Organizers must not create cash entry fees, prize wallets, escrow claims, or off-platform payout instructions unless CoreComp has enabled the exact approved workflow for their account and region.

CoreComp must not collect Social Security numbers, taxpayer identification numbers, government ID images, or equivalent sensitive tax documents in its own forms, support tickets, Discord channels, or ordinary email.

Where legally required, an authorized provider should collect the information on a provider-controlled surface. CoreComp should store only a limited provider reference, requirement status, timestamps, and non-sensitive operational result. Tax and identity status must not appear on public teams, hubs, profiles, leaderboards, or event rosters.

CoreComp or another payer may be required to report a prize, withhold an amount, delay payment while required information is missing, or maintain records. The approved operations guide must define decision ownership, provider webhook verification, corrections, rejected documents, expired status, duplicate payments, year-end reporting, and secure record retention.

Payouts to minors and recipients outside the payer’s home country may require additional guardian, banking, sanctions, tax, currency, or regional eligibility checks. Such payouts must remain unavailable until the selected provider and professional reviewers approve the supported locations and workflow.

CoreComp must not promise a 24-hour payout, 72-hour escrow review, automatic bank deposit, or any other fixed timing until a real provider service level and operational process exist. Event rules should explain result finalization, fraud or integrity review, eligibility holds, required information, estimated timing, cancellation, refunds, chargebacks, and prize disputes.