Operational Purpose

PartnerLinks is designed to support creator referral attribution, creator onboarding and participation, creator commission accounting, brand program infrastructure, refund and reversal reconciliation, fraud prevention, operational auditing, payout eligibility workflows, and attribution integrity safeguards.

PartnerLinks is not designed as a customer-data brokerage platform, behavioral advertising platform, unrestricted analytics platform, customer profiling platform, or data resale platform.

Merchants remain responsible for their own creator relationships, payout decisions, tax obligations, legal compliance responsibilities, product fulfillment, and customer communications.

Least-Privilege Data Approach

PartnerLinks attempts to follow a minimum-necessary-data and least-privilege operational model. We attempt to limit access, processing, retention, and operational exposure of data to what is reasonably necessary for attribution confirmation, creator commission calculations, refund reconciliation, fraud prevention, operational reporting, platform integrity, and operational auditing.

Operational access to data may be restricted based on role, permissions, and business necessity. PartnerLinks does not intentionally provide creators, affiliates, or referral participants with unrestricted access to Shopify customer records. PartnerLinks does not sell customer personal information.

Attribution Processing

PartnerLinks may use referral links, attribution windows, operational session tracking, Shopify operational events, reconciliation workflows, fraud-prevention safeguards, and operational auditing systems to confirm attributed purchase activity and maintain attribution integrity.

PartnerLinks attempts to maintain deterministic attribution and operational accounting consistency where reasonably possible. Attribution systems are intended to reduce duplicate attribution, replay inconsistencies, invalid commission propagation, cross-brand contamination, fraudulent referral activity, and payout inconsistencies.

No attribution system can guarantee perfect attribution accuracy under all technical conditions.

Shopify Order and Refund Events

Certain operational workflows may require limited access to Shopify order and refund events, including order confirmation events, attributed purchase validation, creator commission calculations, refund and reversal reconciliation, fraud prevention, operational auditing, and payout consistency checks.

Order and refund events are operationally necessary to confirm attributed purchases, prevent invalid creator commissions, maintain operational accounting integrity, reduce duplicate or inconsistent payout states, and support reconciliation workflows.

PartnerLinks attempts to access only operationally necessary Shopify event data required for these workflows.

Fraud Prevention and Operational Safeguards

PartnerLinks may implement operational safeguards including replay protections, idempotency safeguards, operational reconciliation workflows, webhook authenticity verification, audit logging, operational monitoring, environment separation, scoped operational access, fraud detection controls, and attribution integrity controls.

These systems are intended to support operational consistency, attribution integrity, payout integrity, fraud prevention, platform security, and reconciliation accuracy.

PartnerLinks may investigate, restrict, reverse, delay, or prevent operational events where fraud, abuse, refund inconsistencies, attribution manipulation, or operational integrity concerns are identified.

Pending vs Claimable Earnings

Displayed earnings states may include pending, under review, claimable, reversed, restricted, or processing. Pending earnings are not guaranteed payouts.

Claimable status may depend on refund activity, fraud-prevention checks, reconciliation review, attribution validation, operational consistency checks, payout eligibility verification, and merchant operational status.

PartnerLinks may restrict, reverse, delay, or prevent payout-related workflows where fraud, abuse, refund inconsistencies, attribution concerns, or operational integrity risks are identified.

Data Retention and Operational Records

PartnerLinks may retain limited operational records where reasonably necessary for attribution integrity, operational auditing, reconciliation, fraud prevention, dispute resolution, legal compliance, and platform integrity.

Retention periods may vary depending on operational requirements, legal obligations, reconciliation requirements, fraud-prevention needs, and platform-compliance obligations.

Platform Compliance

PartnerLinks attempts to operate in alignment with Shopify platform requirements, Stripe platform requirements, protected customer data expectations, least-privilege access principles, operational security best practices, and operational auditing practices.

PartnerLinks may modify operational behavior, data-access workflows, infrastructure safeguards, or platform integrations where necessary to maintain platform compliance, operational integrity, or security.

Security and Operational Integrity

PartnerLinks attempts to maintain operational safeguards intended to reduce unauthorized access, replay attacks, invalid attribution propagation, duplicate operational events, payout inconsistencies, cross-brand contamination, and fraudulent referral activity.

Operational safeguards may include scoped operational access, webhook verification, environment separation, operational monitoring, audit logging, replay protections, reconciliation systems, and access-control restrictions.

No internet-based platform can guarantee uninterrupted availability or absolute security.

Role-Based Visibility

PartnerLinks attempts to restrict operational visibility of data based on role, operational necessity, permissions, business function, and platform integrity requirements.

Creators and affiliates are not intended to receive unrestricted access to Shopify customer records or unrelated merchant operational data.

Sandbox and Testing Environments

Certain systems, payout workflows, operational tools, or integrations may operate in sandbox, testing, beta, limited-access, or pre-production environments.

Sandbox and testing environments may differ from production systems, contain operational limitations, be modified without notice, and operate without live payout functionality. Testing systems should not be interpreted as guaranteed production financial infrastructure.