RaffleX
Toggle sidebar

Sub-Processors

Sub-Processors

Last updated: 9 July 2026

RaffleX is the trading name of GFNI Ltd (company number NI677326), Office 13, Space Antrim, 55-59 High Street, Antrim, BT41 4AY. This page lists the third-party sub-processors we use to help provide the RaffleX platform.

We publish this list under our Data Processing Agreement, in which our customers grant general authorisation for us to use sub-processors. Each sub-processor is bound by a written contract that requires it to protect personal data to a standard no lower than the one we owe to our customers, and we remain responsible for their performance.

How we notify changes

We give at least 30 days' notice before we add or replace a sub-processor that processes personal data on behalf of our customers. We do this by updating this page, so please check it periodically. Customers may object on reasonable data-protection grounds within 30 days, as set out in our Data Processing Agreement.

Core sub-processors

Sub-processor Legal entity Purpose Processing location Transfer safeguard
Amazon Web Services Amazon Web Services EMEA SARL Cloud infrastructure: compute, database, storage and email delivery Ireland (EEA), eu-west-1 UK adequacy for the EEA; AWS DPA with the UK Addendum for any non-EEA support access
Cloudflare Cloudflare, Inc. Content delivery, DNS, edge security and custom-hostname routing for customer sites Global edge network (US-headquartered) UK Addendum to the EU SCCs (Cloudflare DPA)
Stripe Stripe Payments Europe, Limited Platform subscription billing only (charging operators for use of RaffleX). Stripe does not process entrant payment data. Ireland (EEA), with onward transfer to Stripe, LLC (US) UK adequacy for the EEA leg; UK Extension to the EU-US Data Privacy Framework and/or UK Addendum
Plain Not Just Tickets Limited Customer support and CRM (support ticketing) United Kingdom (hosted on AWS UK); onward sub-processors in the US Plain DPA with the UK Addendum/SCCs

Payments

Entry and competition payments are processed by each operator's own payment gateway (for example Cashflows or another provider), under the operator's own direct relationship. Those gateways are the operator's own sub-processors, not ours, and so are not listed here. RaffleX stores only a gateway-issued token and never receives or stores full card details. PCI DSS responsibility for cardholder data sits with the gateway provider and the merchant.

Contact

For any questions about this page, contact us at support@rafflex.io.