Privacy Policy

Last updated: 7th June 2026

This privacy policy explains how FlagMatch collects, uses and stores information when you use the FlagMatch website and related services.

FlagMatch is an independent tool for Hattrick users. It is not operated by, endorsed by, or part of Hattrick.

1. Who operates FlagMatch

FlagMatch is operated as an independent fan-made service to help Hattrick teams arrange friendly matches for flag collecting.

If you have questions about this privacy policy or your data, please contact the FlagMatch operator through the contact details provided on the FlagMatch website or forum thread.

2. Information FlagMatch collects

2.1 Account information

When you create or use a FlagMatch account, FlagMatch may store account information such as your login identifier, email address, account settings, and authentication-related data required to operate the service.

2.2 Hattrick manager and team information

When you connect your Hattrick account, FlagMatch uses CHPP to access the Hattrick information needed to provide the service. This may include your Hattrick manager id, login name, Supporter status, team ids, team names, league and country information, region information, universe/gender, bot or deactivation status, arena/team details, friendly availability, current friendly bookings, fixtures, flags, and related synchronisation timestamps.

FlagMatch stores this information so that it can show your teams, determine which teams can take part in draws, identify possible flag matches, and avoid arranging unsuitable friendlies.

2.3 CHPP connection information

When you connect through Hattrick CHPP, FlagMatch stores the credentials required to make authorised CHPP requests for your account. These credentials are used to sync relevant Hattrick data and, where you have enabled automation, to help send or accept friendly challenges.

You can revoke your Hattrick connection through Hattrick or through FlagMatch where this option is available.

2.4 FlagMatch settings and matching data

FlagMatch may store your team participation settings, including whether a team is used as a chaser, donor, or both; friendly rules preferences; home/away preferences; challenge automation settings; calendar availability; friendly pool acknowledgement; and email notification settings.

FlagMatch also stores draw, snapshot, match, challenge, and scoring records so that it can operate draws, avoid duplicate processing, track successful matches, and maintain fair matching.

2.5 FlagMatch Patron data

If you become a FlagMatch Patron, FlagMatch may store information needed to manage your Patron status, including your FlagMatch account identifier, Patron season, start week, validity period, payment provider, payment reference, amount paid, currency, status, notes, and Patron email preferences.

Patron payments are processed by Stripe. FlagMatch does not store your full card number or full payment card details.

Active Patrons may also store wanted-flag preferences for each team, including the flag, whether the wanted flag is home or away, ranking/order, and whether the preference is active.

2.6 Notification, email and reminder records

FlagMatch may store records of notifications it sends or shows, including the type of notification, related draw or manager, email address used, subject, time sent, and whether a popup or reminder has been shown or dismissed.

This helps FlagMatch avoid sending duplicate emails, avoid repeatedly showing the same reminder, audit notification behaviour, and troubleshoot delivery issues.

3. How FlagMatch uses your information

FlagMatch uses your information to:

4. Legal basis for processing

FlagMatch processes your information where:

Where you make a Patron payment, payment-related processing is also necessary to process the payment, record your Patron status, and maintain payment and accounting records.

5. Hattrick Supporter and FlagMatch Patron

Hattrick flags are an HT Supporter feature. FlagMatch therefore limits normal collection-driven flag-seeking functionality to users who are identified through CHPP as active HT Supporters.

FlagMatch Patron is separate from Hattrick Supporter. Patron contributions support the running costs and development of FlagMatch. They do not purchase Hattrick Supporter status and are not payments to Hattrick.

Patron features, such as wanted-flag preferences and draw-summary emails, are designed to support the app without giving Patrons unfair priority in matching. Wanted flags are preferences, not guarantees, reservations or priority matching.

Non-HT-Supporter users may still use FlagMatch as donors. Non-HT-Supporter Patrons may be able to enter wanted flags manually, but FlagMatch cannot view or verify their full Hattrick flag collection unless CHPP makes that information available.

6. Sharing your information

FlagMatch does not sell your personal information.

FlagMatch may share or process information through third-party services where needed to operate the app, including:

FlagMatch may also disclose information if required by law, regulation, court order, or to protect the security and integrity of the service.

7. Stripe payments

If you choose to become a FlagMatch Patron, payment is handled by Stripe. Stripe may collect and process payment details, billing information, device information, fraud prevention information and transaction records according to Stripe’s own privacy policy and terms.

FlagMatch receives and stores enough payment information to confirm your Patron status and maintain records, such as payment reference, provider, amount, currency, status and relevant Stripe identifiers. FlagMatch does not store your full card number.

8. HT-mail, email and notifications

FlagMatch may notify users about matching results, challenge status, failed matches, required actions, draw summaries, Patron settings, payment status, reminders, or service-related updates.

Where CHPP supports Hattrick internal messaging, FlagMatch may use Hattrick’s internal messaging system to notify you.

FlagMatch may also send email notifications to the email address linked to your FlagMatch account. These may include action digests, Patron draw-summary emails, Patron reminders, account or payment-related messages, and important service messages.

You can disable general email notifications where this option is available. Some essential account, payment, security or legal messages may still be sent where necessary.

FlagMatch may store notification logs, including the notification type, email address, subject, related draw or manager, and time sent, so that notifications can be audited and not repeated unnecessarily.

9. How long information is kept

FlagMatch keeps information for as long as reasonably needed to provide the service, maintain matching history, support troubleshooting, prevent duplicate processing, keep the app secure, and meet legal or accounting requirements.

CHPP connection records, team records, draw records, challenge records, matching records, benefit scoring records, and notification logs may be retained where needed for audit, fairness, troubleshooting or operational reasons.

Patron payment records, Patron status history, notification logs, and Patron reminder records may be retained where reasonably needed for account management, audit, dispute resolution, payment records, preventing duplicate messages, or legal/accounting reasons.

If you stop using FlagMatch, some records may remain in backups, logs, draw history or audit records for a reasonable period.

10. Security

FlagMatch takes reasonable technical and organisational steps to protect your information, including using authentication, access controls, secure hosting, and secure handling of CHPP and payment-related credentials.

No online service can be guaranteed to be completely secure. You should protect your login details and only connect your Hattrick account if you trust the permissions being requested.

11. Your choices

Depending on the features available, you may be able to:

12. Children

FlagMatch is intended for Hattrick users and is not directed at young children. If you believe a child has provided personal information to FlagMatch inappropriately, please contact the FlagMatch operator.

13. Changes to this policy

This privacy policy may be updated from time to time as FlagMatch changes. The date at the top of the page shows when it was last updated.

14. Contact

If you have questions about this privacy policy or how FlagMatch uses your information, please contact the FlagMatch operator through the contact details provided on the FlagMatch website or forum thread.