🇮🇪 Betfred – Privacy, Data & Rights
Privacy, Data & Rights are organised as a practical record for Betfred. betfred-ie.ie is not presented as a regulator website. GRAI, EUR and 18+ frame the Irish context, while entity, product and rule version require direct verification. Editorial estimates never replace the contract.
đź”’ Data categories
The “Data categories” checkpoint comes before data or funds are sent. The responsible party, current rule and request route should be recorded together. The strongest evidence is the account record captured at the moment of action together with the rule that governed it. Promotional balance, cash balance and withdrawable balance are separate records and should never be merged in the explanation. A realistic estimate can test whether a flow is understandable, while actual terms remain the operator’s responsibility.
đź”’ Purpose and legal basis
The “Purpose and legal basis” checkpoint comes before data or funds are sent. The responsible party, current rule and request route should be recorded together. For readers assessing “Purpose and legal basis”, the GRAI reference must connect to the responsible entity and domain rather than the brand name alone. A single-wallet journey needs clear boundaries when sportsbook and casino transactions follow different product rules. A discrepancy is not an invitation to retry with more money; it calls for verification and, if unresolved, an exit.
đź”’ Cookies and devices
The “Cookies and devices” checkpoint comes before data or funds are sent. The responsible party, current rule and request route should be recorded together. A search phrase reveals user intent, but it does not certify availability, value, eligibility or a valid code. Real promotional cost combines the wagering base, product contribution, deadline and any conversion ceiling. Any number absent from the supplied data remains an editorial scenario and never becomes a payout or approval guarantee.
đź”’ Retention and security
The “Retention and security” checkpoint comes before data or funds are sent. The responsible party, current rule and request route should be recorded together. Before a deposit, the complaint route, cooling-off control and effect of incomplete verification should be understood. When an information page and the confirmation screen disagree, the test stops before real funds are committed. Everyday security depends on revocable sessions, a distinct password and clear access to privacy choices.
đź”’ Rights and requests
The “Rights and requests” checkpoint comes before data or funds are sent. The responsible party, current rule and request route should be recorded together. Privacy rights and the request route must remain available without marketing consent. The strongest evidence is the account record captured at the moment of action together with the rule that governed it. Promotional balance, cash balance and withdrawable balance are separate records and should never be merged in the explanation.