Pre-launch legal notice:MyAffPro is the publication name. The legal operator's registered identity, address, jurisdiction-specific lawful-basis analysis, processor list, and final retention schedule must be completed and reviewed before production launch.
Scope and operator
This policy covers the public MyAffPro website. It does not govern third parties you visit through our links. Until the operator details above are finalized, privacy enquiries can be sent through the contact form.
Data we handle
- Contact data: name, email, subject, message, consent, submission time, status, and a one-way request fingerprint used to limit abuse.
- Technical data: ordinary hosting and security logs, such as IP address, user agent, requested URL, and timestamps.
- Affiliate attribution: an internal click identifier, product and link identifiers, referring page, campaign parameters, and a privacy-preserving IP hash.
- Consent and advertising data: signed consent choices and, only where permitted, advertising click or browser identifiers such as Meta
_fbcor_fbp. - Conversion data: transaction identifier, event time, status, currency, and commission data received from an affiliate network. An affiliate click is not treated as a purchase.
On an active Meta campaign, MyAffPro may load Meta Pixel only after Marketing consent and send page-view, content-view, and outbound AddToCart events to the campaign's selected pixels. Meta Conversions API (CAPI) may also send a consent-eligible approved conversion from the server, using affiliate commission rather than merchant revenue as Purchase value. Affiliate network postbacks may supply the conversion lifecycle data used for that process.
Purposes and legal bases
We use data to operate and secure the site, respond to messages, prevent abuse, maintain affiliate attribution, measure approved conversions, and meet legal obligations. Where UK data protection law applies, necessary operations may rely on legitimate interests or legal obligation after the required balancing assessment. Non-essential advertising storage and measurement rely on consent and remain off until consent is recorded.
Sharing and international transfers
Data may be processed by infrastructure, database, security, analytics, advertising, and affiliate-network providers only for the relevant service. The current technical design may involve Supabase, the hosting provider, Meta when marketing measurement is enabled, and the affiliate network associated with a clicked offer.
Some providers may process data outside your country. Before launch, the operator must document the actual providers, locations, contracts, and safeguards used for restricted international transfers.
Retention and security
Consent preferences are stored for up to 180 days, and a consented Meta click identifier may be stored for up to 90 days. Other records should be kept only as long as needed for the purposes above, dispute handling, accounting, security, and legal duties.
Contact request fingerprints use a keyed one-way digest; raw IP addresses are not stored in contact records. Access to submissions is restricted to authorized administration. The final record-retention periods and automated deletion process remain a production launch requirement.
Your choices and rights
Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or objection, and to withdraw consent. You may also complain to your local supervisory authority. Identity verification may be required before a request is fulfilled.
You can change non-essential cookie choices at any time using Cookie Settings in the footer. For a data request, use the contact form. Official UK guidance on the information organizations should provide is available from the Information Commissioner's Office.