What we keep.
And why.

Free beta playtests

Campaigns identified as free beta are free for creators. Tester participation is voluntary and unpaid: these sessions create no earnings or deferred payment. Qualification, reports and reviews are kept in your account under the usual privacy and retention rules. Published beta campaigns remain unpaid when payments are enabled. Any existing paid campaign keeps its original payment terms.

01Platform tax reporting (DAC7)

When required by law, Games2Test reports your identity, tax residence, tax identification numbers, payment account and quarterly earnings to the French tax authority. It may exchange this information with other tax authorities. This processing relies on a legal obligation, not your consent. We retain the reporting register for ten years, starting in the year after the reporting year of a filed declaration. You can access and correct your details and receive a copy of the information reported about you.

Games2Test collects your private identity, address and tax details before qualification and checks their consistency and supported tax-number formats using published rules or the European Commission TIN service. Stripe Connect identity and bank setup is requested at your first withdrawal. When Stripe makes identity information available, it can also be compared with your tax dossier. These checks do not certify a tax number's existence or ownership. Incomplete or inconsistent tax details can prevent new paid bookings until corrected. Saved setup drafts and check records are encrypted. You can edit your details from your profile or contact support about a result.

• When platform reporting obligations apply, we request your legal first and last names, date of birth, main address, every tax residence and TIN with its issuing country, and your VAT number where applicable. If no tax number has been assigned, we request the reason and your place of birth for verification. Where financial-account identifiers are required and available, a private tax form may request an IBAN or equivalent and account-holder details to reconcile with Stripe. Providing those tax details does not change your Stripe payout destination.
• The reporting register includes credited remuneration and adjustments, quarterly activity counts, fees charged to the contributor, any tax withheld, and available payment-account identifiers and holder details. Test payments are excluded.
• Tax dossiers, verification notes and retained bank identifiers are encrypted and accessible only through authorised server workflows. They are not included in studio-facing profiles, reports, marketing or AI qualification reviews.
• Closing an account does not erase records we must legally retain. The retention clock starts in the year following the reporting year of a filed declaration. You can request access, correction and an annual copy through Tax details in your tester workspace or by contacting us.

02Who is responsible

Games2Test (https://games2test.com) is the controller for personal data processed on this site. Write to hello@games2test.com.

Stripe receives payment, identity and bank information entered during Checkout and Connect onboarding, and processes transfers and bank payouts. Games2Test stores provider references, verification status and the details necessary to maintain payment and reward records. Full payment-card and bank credentials are collected by Stripe. Earlier Airwallex records are retained for reconciliation and legal obligations. Google and Discord are independent controllers for their own sign-in screens.

03Data we collect

Account

Email, password hash (if you sign in with email), display name, chosen path (creator / tester), and sign-in metadata.

Sign-in providers

If you use Google or Discord we receive the identifier, email, and public profile name those services send us.

Tester profile

Languages you report in, devices you play on, optional genres, and country of residence. Used to match missions and assess payout options when they are available.

Creator content

Game title, summary, cover image, access type, private keys or URLs, campaign brief, and questionnaire.

Playtests

Reservations, written answers, session videos, qualification answers and videos, review notes, and claims.

Payments

Checkout sessions, order amounts and their remuneration/commission allocation, refunds, Connect account references and verification status, reward withdrawals, Stripe balance transfers and bank payout statuses. Games2Test may receive identity details and masked bank information needed for support, and separately collect available full financial-account identifiers in its encrypted private tax register when required for reporting. Full card details and bank login credentials are not collected by Games2Test. Historical Airwallex payment and beneficiary references remain for reconciliation.

Terms and payment mandate

The terms version, document snapshot or fingerprint, acceptance time and related campaign for a studio checkout, tester booking or application. These records document the agreement and are kept separately from public profiles.

Technical

IP address, browser data, and security logs needed to run and protect the service.

Optional announcements

Your subscription choice and its update date, plus the delivery status of site updates and new playtest announcements you requested.

04Why we use it

We only use personal data when we have a legal basis.

• Contract — creating your account, running a campaign, delivering a report, paying a tester.
• Legitimate interests — keeping the platform safe, reviewing qualifications, improving matching, preventing fraud. You can object.
• Legal obligation — bookkeeping, tax, and answering a lawful request.
• Consent — optional email announcements about site updates and new playtests, enabled in your profile. Unsubscribe from any announcement or turn them off in your profile. Essential account and playtest emails are separate. We do not use optional analytics cookies today; if we add them later, we will ask first.

05Who we share it with

We do not sell personal data. We share it with the providers that make the product work, and with the other party to a playtest (a creator sees the tester’s report and display name; a tester sees the brief and access details for a booked seat).

Administrators see what they need to review qualifications, reports, claims, and payouts.

Each provider has its own privacy policy. Stripe processes current Checkout and Connect information. Airwallex remains listed because earlier payments, beneficiary records and outstanding obligations may still require reconciliation.

06Transfers outside the EU

Some providers process data outside the European Economic Area, including Vercel, Stripe, Airwallex, Resend, Google and Discord. When data leaves the EEA we rely on an adequacy decision where one exists, or on Standard Contractual Clauses and the safeguards those providers publish.

Your account database lives in the European Union (Paris). Playtest videos are stored in the EU (Frankfurt) on Bunny Stream.

07How long we keep it

• Account and profile — for as long as the account exists, then deleted or anonymised when you ask us to close it, unless we must keep a trace.
• Written reports — for the life of the campaign and for as long as the studio keeps the feedback. Bunny playtest videos — two calendar months after the final approval or rejection; reports awaiting review or corrections stay available.
• Abandoned Bunny uploads — eligible for deletion after 24 hours without upload activity, provided they are not attached to an active report. Eligible videos are removed by the daily cleanup.
• Qualification videos — seven days after acceptance or rejection, then removed by the daily cleanup. Pending qualifications and requested corrections stay available.
• Payment records — kept for the statutory accounting period (typically ten years in France).
• Security logs — a short period, unless they are part of an incident.

08Automated review

Qualification answers and, when the video is ready, the session recording may be sent to a Gemini model through Vercel’s AI Gateway. The model can accept or refuse a clear sample. Uncertain cases stay in the admin queue.

You can ask for a human review by writing to hello@games2test.com. You can also object to this processing. If we cannot run the platform safely without it, we may have to close the tester path on your account.

09Your rights

You can ask to access, correct, or delete your data, to limit or object to some processing, and to receive a copy of data you gave us (portability). You can withdraw consent where we relied on it.

Write to hello@games2test.com. We may need to confirm it is you. You can also lodge a complaint with the CNIL or the authority where you live.

10Children

Games2Test is for people aged 18 or over. We do not knowingly collect data from children. If you think a minor has an account, write to us and we will close it.

11Security

Access to private briefs, keys, and videos is restricted. Videos are delivered with token authentication. Studio payments and tester payouts use Stripe and Stripe Connect. No setup is perfect; if we become aware of a breach that affects you, we will follow the law on notifying you and the authority.

12Changes

We will update this policy when our processing changes. The date at the top is the current version. Related pages: Terms, Cookie Policy.