Verwerkersovereenkomst en Beveiligingsbeleid TablePlay Including sub-processor list, technical and organizational measures, responsible disclosure and accessibility statement

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 Part A - Data Processing Agreement Annex 1 - Sub-processors Annex 2 - Technical and Organizational Measures Part B - Security and Coordinated Vulnerability Disclosure Part C - Accessibility Statement

Page 2 of 10

Part A - Data Processing Agreement Article 1 - Parties This data processing agreement applies between the business customer of TablePlay as Controller and Jimani B.V., trading under the name TablePlay by Jimani, Albert Plesmanweg 122, 4462 GC Goes, KvK 91644453, as Processor. The parties are collectively referred to as the Parties.

Article 2 - Applicability and formation This agreement applies insofar as TablePlay processes personal data on behalf of and for the benefit of the Customer and forms an integral part of the main agreement. It comes into existence through electronic acceptance, signature, or actual use of the Service. For processing activities for which TablePlay independently determines the purposes and means, TablePlay is the controller and the Privacy Statement applies. In the event of a conflict regarding processing on behalf of the Customer, this Data Processing Agreement shall prevail over the General Terms and Conditions.

Article 3 - Subject matter, duration and nature TablePlay processes personal data for restaurant-based game, table, QR, score, leaderboard, dashboard, and support functionalities. The processing continues for the duration of the main agreement and a limited period thereafter for deletion, return, backup rotation, statutory obligations, and legal protection. The processing may include collecting, recording, organizing, structuring, storing, consulting, calculating, combining within the restaurant context, displaying, transmitting, restricting, deleting, and anonymizing.

Article 4 - Purposes • Linking QR codes to a restaurant and table. • Starting and running game sessions. • Processing temporary nicknames, game choices, answers, scores, and results. • Facilitating table-versus-table games and temporary leaderboards. • Displaying restaurant-based statistics. • Preventing duplicate, fraudulent, or technically invalid sessions. • Technical support, security, continuity, and recovery. • Deleting or anonymizing after retention periods.

Article 5 - Categories of data subjects • Guests and players of the Customer. • Contact persons, users, employees, and auxiliary persons of the Customer. • Persons mentioned in a support request.

Article 6 - Categories of personal data • Temporary nickname, table number or unique table ID, and restaurant or location ID. • Game session ID, selected game, playing mode, answers, actions, score, result, and ranking. • Date, time, and temporary language setting. • Technical session, IP, browser, and device data insofar as present in security logs.

Page 3 of 10 • Name and business email address of a contact person and content of support requests. • Other data entered within the agreed functionality. TablePlay is not intended for special categories of data, criminal, medical, or biometric data, or extensive directly identifiable guest profiles. The Customer shall not instruct such processing without prior written agreement.

Article 7 - Documented instructions The main agreement, this Data Processing Agreement, customer portal settings, and lawful support requests constitute instructions. TablePlay does not process data for other purposes, except for statutory obligations, its own independent security and legal protection purposes, or processing after adequate anonymization. In the event of a suspected unlawful instruction, TablePlay shall inform the Customer, unless legally prohibited from doing so, and may suspend performance. Additional extensive instructions may be invoiced separately.

Article 8 - Obligations of the Client The Client warrants lawfulness, valid legal basis, information to Guests, lawful instructions, data minimisation, internal security and protection of login credentials. The Client is responsible for accuracy and quality, does not require real names of Guests and does not use Game Data for individual marketing or profiling without an independent legal basis. Security incidents and unlawful instructions shall be reported without delay.

Article 9 - Confidentiality Persons under the authority of TablePlay are given access only to the extent necessary, are bound by confidentiality and process solely in accordance with instructions. The obligation continues to apply after termination. Disclosure to third parties shall take place solely on the basis of this agreement, the principal agreement or the law.

Article 10 - Security TablePlay implements appropriate technical and organisational measures, taking into account the state of the art, costs, nature, scope, context, purpose and risk. The measures are set out in Annex 2 and may be adapted provided the general level of protection is not materially reduced. No system can guarantee absolute security.

Article 11 - Data Breaches TablePlay informs the Client without undue delay after becoming aware of a breach of personal data processed on behalf of the Client. Where possible, information shall be provided on the nature, systems, categories of data and data subjects, consequences, measures and contact information. Information may be provided in phases. TablePlay investigates, mitigates, preserves relevant evidence and carries out remediation. The Client assesses the statutory notification obligation and TablePlay provides reasonable support. A notification does not constitute an admission of liability. Work performed due to circumstances within the Client's responsibility may be carried out at reasonable cost.

Article 12 - Requests from Data Subjects Direct requests concerning the Client's role are in principle forwarded. TablePlay only responds independently on instruction, in its own role or in the case of a statutory obligation. TablePlay provides reasonable assistance with access, rectification, erasure, restriction, portability and objection.

Data Processing Agreement and Security Policy TablePlay

Page 4 of 10

Because Guests do not have an Account, identification may be limited. Restaurant, table, date, time, nickname and game context may be required. Data shall not be provided if it is not sufficiently established that it relates to the requester.

Article 13 - Support for Compliance TablePlay provides reasonable support with security, data breach assessments, data protection impact assessments, prior consultation and necessary documentation. Extensive support beyond the standard service may be invoiced, unless it results from a default by TablePlay.

Article 14 - Sub-processors The Client grants general authorisation for the sub-processors listed in Annex 1. TablePlay may add, replace or remove these and shall maintain an up-to-date electronic list. In the event of a new material sub-processor, TablePlay shall in principle provide thirty days' prior notice. The Client may, within that period, raise a substantiated objection on specific data protection grounds. The parties shall seek additional safeguards, limitation or a technical alternative. If no reasonable solution exists, the Client may terminate the directly affected part prior to deployment. TablePlay imposes substantially equivalent obligations and remains responsible to the extent provided for under the GDPR.

Article 15 - International Transfer Personal data shall, where possible, be processed within a European region. Sub-processors or group companies may be established outside the EEA or may have access from outside the EEA. Where required, TablePlay uses adequacy decisions, standard contractual clauses, supplementary measures or other valid mechanisms. Upon reasonable request, information shall be provided with due regard to confidentiality.

Article 16 - Requests from Authorities TablePlay provides data solely to competent authorities in the event of a lawful obligation. Where permitted, the Client shall be informed in advance. TablePlay assesses authority, scope and legal validity and limits disclosure where possible.

Article 17 - Audits and Information TablePlay shall make available reasonable information, including security documentation, audits, certifications, questionnaires, or assurance statements. If this is insufficient, the Client may request an audit no more than once per calendar year, with thirty days' notice, during office hours, by an independent expert bound by confidentiality, without causing damage to security, confidentiality, or other clients.

The Client shall bear the costs unless a material attributable breach is established. TablePlay may withhold source code, other client data, vulnerability details, and commercially sensitive information where a sufficient alternative exists.

Article 18 - Return and Deletion Upon termination, TablePlay shall delete or return, at the Client's election and insofar as technically and legally possible, data processed exclusively on behalf of the Client. The election shall be communicated no later than within thirty days. In the absence of an election, TablePlay may delete or anonymize in accordance with the standard policy. Backups may contain data for a maximum of one month and shall be used exclusively for restoration purposes.

Data Processing Agreement and Security Policy TablePlay

Page 5 of 10

Data that are legally required to be retained, necessary for legal protection, or anonymized need not be deleted.

Article 19 - Liability The liability provisions of the General Terms and Conditions shall apply mutatis mutandis. Each party shall be responsible for its own privacy obligations.

The Client shall indemnify TablePlay against claims arising from unlawful instructions, lack of a legal basis, insufficient information, unlawful use of Game Data, or the input of prohibited sensitive data, to the extent permitted by law.

Article 20 - Term and Termination This Data Processing Agreement shall terminate when TablePlay no longer processes personal data on behalf of the Client. Confidentiality, security, deletion, liability, and audit provisions shall remain in effect insofar as their nature so requires.

Article 21 - Governing Law and Disputes This Data Processing Agreement shall be governed by Dutch law. Disputes shall be handled in accordance with the General Terms and Conditions.

Annex 1 - Subprocessors Supplier

Service

Possible Data

Region / Role

Supabase

Database, authentication, storage, and backend Accounts, table data, nicknames, sessions, scores, Primary and logs EU region insofar as configured; core subprocessor

Vercel

Hosting, runtime, content delivery, and IP logging address, request, browser, device, and application data EEA and possibly the US; hosting subprocessor

Twilio SendGrid

Transactional and operational e-mail Name, e-mail address, account information, content, International; and delivery e-mail statussubprocessor

OpenAI / other AI supplier Only when AI features are activated

Limited data necessary for the function Depending on configuration; potential subprocessor

Stripe

Payments, invoicing, and fraud Business data, invoices, transactions, and payment status International; role varies per processing activity

Google / Meta / LinkedIn Analytics and marketing following consent Website, device, advertising, and conversion data International; generally not a subprocessor for th

The current list is made available via the website or the client portal. In the event of a material new subprocessor, the notification and objection procedure set out in Article 14 shall apply. TablePlay shall not provide identifiable guest data to an AI supplier for general model training, unless this is explicitly, lawfully, and transparently arranged otherwise at a later date.

Annex 2 - Technical and Organizational Measures 1. Access Security • Unique user accounts and secure authentication. • Hashed passwords and restriction of administrative rights. • Access based on role and necessity. • Revocation of access when no longer required. • Additional authentication measures where appropriate.

2. Logical Data Separation • Separation between business Accounts and tenant-bound authorization.

Data Processing Agreement and Security Policy TablePlay

Page 6 of 10 • Supabase Row Level Security where technically applicable. • Restriction of access to other Clients' data. • Unique table identifiers.

3. Transport and Storage • HTTPS and TLS-secured connections. • Secure communication between browser, application, backend, and APIs. • Storage with selected cloud providers. • Restricted employee access and contractual confidentiality. • No storage of passwords in directly readable form.

4. Availability, Logging, and Recovery • Backups and recovery provisions where appropriate. • Monitoring of technical errors and relevant login attempts. • Detection and investigation of abnormal use. • Backups in principle for a maximum of one month. • Logs in principle for a maximum of one year, unless longer retention is required for an incident or dispute.

5. Beveiligde ontwikkeling en leveranciersbeheer • Version control, code review, and controlled deployment where appropriate. • Restriction of secrets and keys in source code. • Timely updates of relevant components. • Assessment and remediation of reported vulnerabilities. • Selection of professional suppliers, contractual arrangements, and transfer mechanisms.

6. Data minimisation and incident management • No mandatory real names, email, or phone number for Guests. • Temporary nicknames and limited leaderboard visibility. • Deletion or anonymisation after specified periods. • Internal escalation process, investigation, recording, notification obligation assessment, and remedial measures.

Part B - Security and Coordinated Vulnerability Disclosure 1. Purpose and reporting address TablePlay attaches importance to the security of the website, Platform, infrastructure, and data. Potential technical vulnerabilities can be reported confidentially via support@tableplay.online with the subject line Security Report - confidential.

2. Content of a report • Clear description of the vulnerability. • Domain, endpoint, screen, or system involved.

Page 7 of 10 • Reproducible steps and potential impact. • Limited screenshots or technical evidence. • Browser, device, or environment used. • Contact details and, if applicable, a proposal for secure communication.

3. Permitted actions • Only actions necessary to establish existence. • Keep impact and data access as limited as possible. • Do not modify, delete, or download any data belonging to third parties. • Do not affect availability and stop as soon as sufficient evidence exists. • Only investigate systems that are demonstrably under the control of TablePlay.

4. Prohibited actions • Social engineering, phishing, physical attacks, brute force, and credential stuffing. • Account takeovers, denial-of-service, malware, or persistent access. • Modifying, erasing, copying, or disclosing data. • Actual manipulation of payments, invoices, coupons, or scores. • Investigation of external suppliers without their consent. • Burdensome automated scans. • Disclosure before a reasonable investigation and remediation period has been provided. • Extortion or coercing payment through threats.

5. Response and disclosure TablePlay aims to acknowledge receipt within five working days, assess the report, ask questions where necessary, inform the reporter in general terms, and mitigate a verified vulnerability as soon as reasonably possible. The remediation time depends on severity, complexity, suppliers, and necessary testing. TablePlay does not guarantee a fixed period. Details will not be disclosed publicly before TablePlay agrees, a reasonable date has been agreed upon, or at least ninety days have elapsed without a reasonable substantive response or remediation attempt. Personal data, authentication data, and exploit code will not be published.

6. No general bug bounty and legal approach TablePlay does not operate a general bug bounty programme, and a report does not entitle the reporter to payment, assignment, or publicity. TablePlay may, at its own discretion, provide recognition. TablePlay will, in principle, not take legal action against a researcher who acts in good faith, within this policy, without causing damage, confidentially, and without extortion. This commitment does not apply in cases of clearly punishable, harmful, fraudulent, or disproportionate actions and does not bind third parties or authorities.

Page 8 of 10

7. security.txt TablePlay may publish a technical file at /.well-known/security.txt containing the reporting address, a link to the policy, languages, an expiry date, and possibly an encryption key. This file must be periodically checked and renewed.

Part C - Accessibility Statement 1. Ambition and reference framework TablePlay strives to make the website, registration, customer portal, and guest games usable for a broad range of users, including persons with visual, auditory, motor, or cognitive impairments. Where reasonably possible, the principles of WCAG 2.2 level AA are used as a technical and substantive reference framework. This does not constitute a guarantee that every component is fully compliant under all circumstances.

2. Current status The complete environment has not yet been independently and comprehensively audited. TablePlay therefore does not currently claim full formal WCAG 2.2 AA conformity. Potential limitations relate to real-time game components, time pressure, drag-and-drop, animations, external payment or authentication pages, translations, older colour displays, and touch-oriented functions.

3. Measures • Semantic HTML and usable labels where appropriate. • Keyboard operability of essential functions and visible focus. • Sufficient contrast and scalable text. • Alternative text for informative images. • No essential information conveyed solely through color. • Understandable error messages and consistent navigation. • Clear buttons and links. • Support for common browsers and screen sizes. • Limitation of unnecessary animation. • Understandable language in the guest environment. • Automated and manual testing where possible.

4. Games and time pressure Some games are, by their nature, time-bound. Where technically and content-wise possible, TablePlay may offer alternative game modes, extended time limits, less movement, visual alternatives to sound, and text or symbols in addition to color. Not every game mode is equally suitable for every user. Restaurants are encouraged to offer multiple game types.

Data Processing Agreement and Security Policy TablePlay

Page 9 of 10

5. Responsibility of the Business Client The Client remains responsible for physical and operational accessibility of the Location, including placement of QR codes, legibility of printed materials, alternative assistance, accessibility of screens, support by staff, and own content. QR codes shall be placed accessibly and visibly, and, where reasonably possible, an alternative shall be provided to Guests who are unable to scan independently.

6. Reporting and alternative access Accessibility issues may be reported via support@tableplay.online, stating the page or game, device, browser, assistive technology, description, and desired solution. TablePlay aims to provide acknowledgment of receipt within five business days and a substantive response within a reasonable period. Where possible, information may be offered via e-mail, support, an alternative instruction, manual processing, or another game option.

7. Disproportionate burden and improvement An adjustment may be postponed where it is technically infeasible, materially compromises security, changes the fundamental nature of a game, is dependent on an external supplier, or constitutes a disproportionate organizational or financial burden. TablePlay shall then assess an alternative. TablePlay may take accessibility into account in design, testing, prioritization, user feedback, and external audits, and shall update this statement accordingly.

8. Contact TablePlay by Jimani - Jimani B.V. - Albert Plesmanweg 122 - 4462 GC Goes - The Netherlands - Company Registration No. 91644453 - VAT NL865722729B01 - support@tableplay.online.

Data Processing Agreement and Security Policy TablePlay

Page 10 of 10

Supplementary Sub-Processor List This sub-processor list forms part of the Data Processing Agreement and Security Policy of TablePlay. The current list may change when suppliers, regions, or functions change.

Supplier: Supabase Service: database, authentication, storage, and backend. Possible data: accounts, table data, nicknames, sessions, scores, and logs. Region / role: primarily EU region insofar as configured; core sub-processor.

Supplier: Vercel Service: hosting, runtime, content delivery, and logging. Possible data: IP address, request, browser, device, and application data. Region / role: EEA and possibly the US; hosting sub-processor.

Supplier: Twilio SendGrid Service: transactional and operational e-mail. Possible data: name, e-mail address, account information, content, and delivery status. Region / role: international; e-mail sub-processor.

Supplier: OpenAI / other AI supplier Service: only in the case of activated AI functions. Possible data: limited data necessary for the function. Region / role: dependent on configuration; potential sub-processor. TablePlay does not provide identifiable guest data to an AI supplier for general model training, unless this is later expressly, lawfully, and transparently arranged otherwise.

Supplier: Stripe Service: payments, invoicing, and fraud. Possible data: business data, invoices, transactions, and payment status. Region / role: international; role differs per processing activity.

Supplier: Google / Meta / LinkedIn Service: analytics and marketing after consent. Possible data: website, device, advertising, and conversion data. Region / role: international; generally not a sub-processor for restaurant game data.