TablePlay Cookie Policy Use of cookies, localStorage, pixels, tags and similar technologies

TablePlay by Jimani Jimani B.V. Albert Plesmanweg 122, 4462 GC Goes KvK 91644453 - Btw NL865722729B01 support@tableplay.online

Version 1.0 Last updated: 10 July 2026

Legal review note This document has been prepared for business use by TablePlay. Have the final publication, international application, current suppliers, technical setup and country-specific rules periodically reviewed by legal counsel.

Table of Contents 1. Introduction 2. What are cookies? 3. Purposes 4. Categories 5. Consent 6. Changing settings 7. Suppliers 8. Current inventory 9. LocalStorage and session storage 10. Server-side processing 11. Gaming environment 12. International processing 13. Retention periods 14. E-mail tracking 15. Privacy preference signals 16. Changes 17. Contact

TablePlay Cookie Policy

Page 2 of 6

1. Introduction This cookie policy describes the use of cookies and similar technologies by TablePlay by Jimani, provided by Jimani B.V., Albert Plesmanweg 122, 4462 GC Goes, KvK 91644453, VAT NL865722729B01 and support@tableplay.online. The policy applies to tableplay.online, associated subdomains, the customer portal and browser-based gaming environments.

2. What are cookies? Cookies are small data files that may be placed on or read from a device. Similar technologies include, among others, localStorage, sessionStorage, pixels, tags, scripts, software development kits, server-side identifiers and browser techniques. In this policy, these are collectively referred to as cookies, unless the context requires otherwise.

3. Purposes Cookies may be used for technical operation, authentication, session security, language and country settings, cookie preferences, analytics, performance measurement, advertising and conversion measurement, fraud prevention and improvement of the Service.

4. Categories 4.1 Strictly necessary cookies Necessary cookies support session management, authentication, Account security, load balancing, fraud prevention, cookie preferences, language choices and forms. They may be used without separate consent where the requested Service cannot function properly without this technique. Blocking via the browser may cause certain features to malfunction.

4.2 Preference cookies Preference cookies remember language, country, display and user interface settings. Where legally required, they will only be used after consent.

4.3 Analytical cookies Analytical cookies measure pages, source, interactions, duration, devices, errors and performance. TablePlay may use Google Analytics 4 and Vercel Analytics. Analytical techniques with more than a minor privacy impact will only be activated after consent.

4.4 Marketing cookies Marketing cookies and pixels measure campaigns and conversions, compile target audiences and may make advertisements more relevant. TablePlay may use Google Ads, Meta Pixel and LinkedIn Insight Tag. These will, insofar as required, only be activated after consent.

5. Consent Upon first visit, a preference window is shown when non-necessary technologies are used. The visitor may accept all, reject all or choose per category. Non-necessary analytics and marketing are not preloaded. Refusal does not prevent essential access. Consent may be withdrawn at any time and may be requested again after expired preferences, new suppliers, changed purposes or relevant legislation.

TablePlay Cookie Policy

Page 3 of 6

6. Changing settings The visitor may change choices via the permanent Cookie settings link in the footer. Cookies may also be deleted or blocked via the browser. Deletion of the preference cookie may cause the banner to reappear.

7. Suppliers 7.1 Supabase Function: database, authentication, session management and backend. Possible data include session ID, authentication status, technical identifiers and log data. Category: necessary. Retention period: for the duration of the session or as per the authentication setting.

7.2 Vercel Function: hosting, application execution, content delivery, network security and performance measurement. Possible data include IP address, browser, device, page and performance data. Category: necessary and, for additional analytics, analytical.

7.3 Google Tag Manager Function: technical management and activation of tags. Tag Manager does not itself need to place a traditional cookie, but may load other tags. Tags requiring consent will only be activated after consent.

7.4 Google Analytics 4 Function: website analytics. Possible identifiers include, depending on configuration, _ga and a property-specific _ga cookie. Possible data include page views, events, general location, browser, device, campaign source and online identifiers. Category: analytical. The retention period is set as short as possible and is stated in the current inventory.

7.5 Google Ads Function: conversion and campaign measurement. Possible data include advertisement click, campaign, conversion, browser, device and online identifiers. Category: marketing. The term depends on cookie and Google settings.

7.6 Meta Pixel Function: measurement of advertisements and conversions. Possible identifiers include, depending on configuration, _fbp and click-related values. Category: marketing.

7.7 LinkedIn Insight Tag Function: business campaign measurement and conversions. Possible cookies include li_gc, bcookie, AnalyticsSyncHistory and UserMatchHistory, depending on configuration. Category: marketing.

7.8 Twilio SendGrid SendGrid is used primarily for e-mail and does not necessarily place website cookies. If e-mail tracking is active, delivery, opening and clicks may be recorded. TablePlay limits tracking and only uses it where an appropriate legal basis exists.

Cookie Policy TablePlay

Page 4 of 6

7.9 Stripe Stripe may use necessary security and fraud prevention techniques on payment and invoicing pages. Possible data include payment, session, browser, device and fraud prevention data. Category: necessary.

8. Current cookie inventory The specific names, domains and terms may change due to updates by TablePlay or vendors. The current inventory with name, domain, vendor, purpose, category and term is displayed in Cookie Settings and forms an integral part of this policy. TablePlay reviews the inventory periodically.

9. LocalStorage and session storage LocalStorage or sessionStorage may be used for language selection, temporary game information, navigation, cookie preferences and restoration of a session. SessionStorage is generally deleted upon closing of the tab or browser. LocalStorage persists until deletion, browser clean-up or technical expiry. This storage is not used for structural personal profiling of players.

10. Server-side processing Certain data may be processed server-side without a browser cookie for security, fraud, session validation, troubleshooting, load distribution and execution of a requested Service. Server-side processing is not used to circumvent a refused cookie consent.

11. Gaming environment Guests do not need to create a personal Account. TablePlay does not use a cookie or device fingerprint with the primary purpose of recognising a Guest across restaurant visits over the long term. Temporary storage may be necessary for session retention, table linking, language, game progress and abuse prevention. This temporary storage is not used for behaviourally targeted advertising to individual restaurant guests.

12. International processing Google, Meta, LinkedIn, Stripe, Twilio SendGrid and Vercel may process data outside the European Economic Area. Where required, TablePlay uses adequacy decisions, standard contractual clauses and supplementary measures.

13. Retention periods Session cookies are, in principle, deleted after the browser session. Persistent cookies remain until the purpose has been achieved, the expiry date lapses, the user deletes them or withdraws consent, or TablePlay withdraws the cookie. Preferences may be retained during the period of validity and, to a limited extent, thereafter in order to give effect to the choice and demonstrate compliance. The precise term is stated in the current inventory.

Cookie Policy TablePlay

Page 5 of 6

14. E-mail tracking Transactional e-mails may contain technical delivery and security information. Marketing e-mails may, where lawful, measure opening and clicks. Unsubscribing from marketing does not affect necessary invoicing, security and service messages.

15. Privacy preference signals Browser mechanisms such as Do Not Track are not uniformly supported everywhere. Where technically and legally applicable, TablePlay may treat recognised signals such as Global Privacy Control as an objection to certain marketing processing. Cookie Settings remains the primary method.

16. Amendments TablePlay may amend this policy in the event of new cookies, vendors, functionalities, legislation or technical configuration. The current version is published. In the event of material amendments, consent may be requested again.

17. Contact TablePlay by Jimani - Jimani B.V. - Albert Plesmanweg 122 - 4462 GC Goes - The Netherlands support@tableplay.online.

Cookie Policy TablePlay

Page 6 of 6