MATMAPS LEGAL
Privacy Policy
Last updated 9 September 2026
This Privacy Policy explains how MatMaps Team ("MatMaps", "we", "us" or "our") collects and uses personal information when you use the MatMaps mobile app, website and related services (together, the "Services"). MatMaps Team, owned and operated by Mrs Sadie-May Guntrip and Mr Glyn Guntrip, is the controller responsible for the processing described in this policy. Its contact address is 483 Green Lanes, London, N13 5XT.
We aim to handle personal information fairly and transparently in accordance with the UK General Data Protection Regulation (UK GDPR), the Data Protection Act 2018 and other applicable UK data protection law.
Questions or privacy requests can be sent to hello@matmaps.co.uk.
Contents
1 Information we collect
- Account and authentication information: email address, authentication identifiers, account status and security information.
- Profile information: name, unique @username where the account is eligible, profile image, biography, sports, ability level, belts, affiliated club and account or subscription role, including Free Junior or Athlete Junior status. A Junior does not receive a public @username.
- Private age information: the date of birth entered during sign-up, the resulting age band (under 13, teen or adult), the source or declaration method and any age-range signal supplied by Apple or Google. Date of birth is stored separately from the public profile and is not displayed to other users.
- Age-assurance results: verification status and method, provider name, provider session and workflow identifiers, provider decision, whether an adult threshold was met, threshold applied, verification and expiry timestamps, error codes and attempt count. For facial age estimation, MatMaps receives the exact estimate through the signed provider response only long enough to apply its adult threshold; it does not store that exact estimate in its database. MatMaps does not intend to store raw face captures, ID images or document numbers in its own database.
- Age-assurance capture handled by Didit: depending on the method chosen, Didit may process a live face image or short video, liveness signals, a passport or driving licence image and extracted document details, and a one-to-one comparison between the live image and the document photograph. These captures are sent directly to Didit through its official flow rather than being intentionally stored by MatMaps. Didit has confirmed that its duplicate-face check activates automatically whenever Liveness is used and cannot currently be disabled. The check compares the submitted face with faces from previously approved sessions in the same MatMaps application and can identify a possible or high similarity match, a duplicate face associated with a different name, or multiple faces in the liveness image. Didit states that this matching does not compare MatMaps users with another customer's data. MatMaps has asked Didit to add a way to disable the check. A face embedding may be available for this within-application duplicate detection during the session-retention period. Retaining a separate image-free template after session deletion is opt-in; MatMaps has selected "Delete with session" and has not enabled that separate retention.
- Friends and connections: friend requests, friendships, blocks, mentions, tags and associated timestamps.
- Messages: one-to-one messages, message requests, delivery/read state, staff group messages and the sender attached to a club notice. Messages are private to their participants, but they are not described as end-to-end encrypted.
- Community content: Arena posts, comments, photos, videos, likes, shares, saves, Travelling Fighter Hub text posts and reports.
- Club and event information: club details, club @username, ownership and staff memberships, staff invitations, affiliations, member verification, notices, media, events, reviews, promotions and analytics interactions.
- Training information: timer settings and usage, scorekeeping, training logs, notebook entries, progress statistics and coach or member notes. These entries may contain health or injury information if a user chooses to add it; users and club staff should not record sensitive information about another person without an appropriate reason and permission.
- Location information: precise device location when permission is granted, approximate location, map searches, distance calculations and location tags added to posts or events.
- Technical and usage information: device type, operating system, app version, IP address, identifiers, crash diagnostics, logs, pages viewed, searches and feature interactions. For details regarding our use of cookies, local storage and consent choices on web and admin interfaces, see our Cookie Policy.
- Advertising information: advertising identifiers and ad impressions, clicks or related signals when AdMob advertising is enabled for eligible free users.
- Subscription information: plan, entitlement, renewal and transaction status supplied by Apple, Google or a subscription provider such as RevenueCat when billing is connected. MatMaps does not receive or store full payment-card details from app-store purchases.
- Support information: messages and attachments you send when contacting support, including invite-link or error details you choose to provide.
2 Where information comes from
We receive information directly from you, automatically from your device and use of the Services, from other users when they invite, tag, report, review or interact with you, and from service providers that support authentication, hosting, analytics, advertising, subscriptions or age assurance.
Age information may come from the date of birth you enter, an age-range signal made available by Apple or Google, and the result returned by Didit after a facial age-estimation or photo-ID check. We use the stricter result where signals conflict. A subscription purchase is not treated as age proof.
Some club and event information is supplied by club owners, staff, users or existing data sources. Users should confirm time-sensitive club and event details directly with the organiser.
3 Age assurance, face data and Junior access
Face data used for optional adult age assurance
What is collected: MatMaps offers optional adult age assurance provided by Didit Identity Spain, S.L. Depending on the method you choose, Didit collects a live selfie image or short liveness video, liveness and anti-spoofing signals, and facial characteristics or a biometric face template derived from that capture. For photo-ID verification, Didit also processes the portrait in your passport or driving licence and compares it with the live capture. Didit may compare the capture with previously approved sessions within the MatMaps customer environment to detect duplicate or abusive verification attempts. This comparison is not made against another Didit customer's data. MatMaps does not use Apple Face ID and does not receive Apple Face ID data.
How it is used: Face data is used only for optional adult age assurance, liveness confirmation, photo-ID face matching and prevention of duplicate or fraudulent verification attempts. It is not used for advertising, marketing, tracking, social profiling or sale. MatMaps does not permit Didit to use MatMaps verification data to train general artificial-intelligence or machine-learning models. If you do not consent, you can continue to use the Junior-safe parts of MatMaps for which you are otherwise eligible, but adult social features will remain unavailable.
What MatMaps receives and stores: The face capture is transmitted directly to Didit through its verification flow. MatMaps does not store raw selfies, liveness videos, identity-document images or biometric face templates in Firebase or another MatMaps-controlled database. MatMaps receives only the minimum result metadata needed to apply the access decision, such as the provider session and workflow identifiers, method, status or decision, whether the adult threshold was met, timestamps, error information and attempt count. For facial age estimation, an exact age estimate may be received through Didit's signed response only long enough to apply the adult threshold; MatMaps does not retain the exact estimate.
Sharing and storage: Didit acts as MatMaps' processor for the verification. Didit states that the verification data is processed and stored on Amazon Web Services infrastructure in Ireland (AWS region eu-west-1). Face data is not provided to other MatMaps users, clubs, advertisers, Google AdMob or RevenueCat, and MatMaps does not sell it. Didit may make limited disclosures to its infrastructure providers, professional advisers or public authorities where necessary to provide and secure the service or where legally required. More information is available in the Didit Verification Privacy Notice.
Retention and deletion: MatMaps has configured Didit to delete verification records, identity-document images, selfies or liveness video, and session-owned face embeddings no later than 30 days after collection. MatMaps has set Didit's separate biometric-template setting to "Delete with session", so no reusable image-free face template is retained after the associated session is deleted. Earlier deletion can be requested using Settings > Withdraw biometric consent and delete verification data, through account deletion, or by emailing hello@matmaps.co.uk. The erasure request covers the Didit verification sessions linked to the account and the linked Didit user record, subject only to any information that must legally be retained.
Your choice: Immediately before either Didit method begins, MatMaps displays a just-in-time notice and an unticked checkbox asking for explicit consent to the facial and biometric processing described above. A verification session cannot begin unless you actively give that consent. You can withdraw consent at any time. Withdrawal does not make processing already carried out unlawful, but it removes adult social access and starts deletion of eligible verification data.
MatMaps uses age assurance to keep adult social features away from children. A date of birth creates an initial age band only. It does not verify an adult or unlock Arena, the Travelling Fighter Hub, friends, general messaging or other adult social features.
Users seeking adult access can choose a Didit facial age-estimation check or a photo-ID check. Facial estimation uses a live capture and liveness result. MatMaps currently auto-confirms adult status only where the returned estimate is at least 25. An adult-range estimate below that threshold requires step-up to photo ID. Photo-ID verification checks an eligible UK passport or driving licence, document authenticity and expiry, the extracted date of birth, liveness and whether the live face matches the document photograph.
Before either method begins, the app presents an unticked checkbox asking for explicit consent to Didit processing facial images and biometric data for age assurance. A Didit session cannot start unless the user actively selects it. The notice identifies the purpose and explains that photo-ID verification includes comparing the live selfie with the document portrait.
Didit sends MatMaps the relevant decision, warnings, node and session references through a secured webhook and, for facial estimation, the age estimate needed to apply the threshold. MatMaps uses the exact estimate transiently and records only the minimum result needed to apply access controls. A pending, failed, underage, inconclusive or expired result remains restricted. A verified-adult result is normally valid for 365 days. We may require another check earlier where Didit later identifies fraud, the result was wrong or account security requires it.
Access is decided automatically from the age band, assurance status, expiry and relevant account entitlement. The practical effect is whether adult social features are enabled. You can request an explanation, challenge an inaccurate result and ask for human review by emailing hello@matmaps.co.uk. Where appropriate, we will offer the alternative verification method.
Users under 13 are blocked. Users aged 13 to 17, adults who have only declared a date of birth, and users whose age signal is missing, unavailable, declined, conflicting or in error receive the Junior-safe experience. Free Juniors can use limited free training tools, Club Discovery, core club details, events and their own profile and sports preferences. They cannot affiliate, receive club notices or message staff. Paid Athlete Juniors may use private training tools, have one verified club affiliation, receive that club's notices and message only its owner or active staff. All Juniors are blocked from public social content and interaction, public usernames and media, club galleries and videos, reviews, tags, friends, general user search and general direct messages.
A club owner or staff member involved with a Junior cannot access the Junior's notebook, training sessions, password, account recovery or deletion controls. If the Junior's affiliation or the adult's staff role ends, the restricted message history becomes read-only and new messages are blocked.
We do not use date of birth, face or ID information, the provider decision or a Junior/adult age-assurance status for advertising, marketing profiles or unrelated analytics.
4 Why we use information and our lawful bases
| Purpose | Usual UK lawful basis |
|---|---|
| Create accounts; provide profiles, discovery, events, Arena, friends, messaging, training and club tools | Performance of our contract with you |
| Use a private date of birth and platform age-range signal to place the account in an age-appropriate experience without treating self-declaration as adult verification | Performance of our contract; legitimate interests in providing a safe, age-appropriate service; and legal obligation where a specific online-safety duty applies |
| Use Didit facial age estimation or photo-ID matching to decide whether adult features may be enabled, prevent circumvention and retain evidence of the result | Consent under Article 6(1)(a) for optional facial and biometric processing; where biometric data is used to uniquely identify or verify a person, explicit consent under Article 9(2)(a). Legitimate interests support the separate processing of minimum age-status metadata needed to protect children, prevent circumvention and secure accounts; legal obligation applies only where a specific duty requires the processing. |
| Operate security, prevent fraud and spam, enforce limits, investigate reports and protect users | Legitimate interests in keeping MatMaps safe and reliable; legal obligation where applicable |
| Use device location for nearby clubs, distance ordering and location-based features | Consent through the device permission and in-app choice; some approximate location use may be necessary to provide a requested search |
| Send requested service notifications, such as friend requests, messages, club notices, affiliation requests and staff activity | Contract and legitimate interests; device notification permission where required |
| Measure performance, fix crashes and improve features | Legitimate interests in improving and securing the Services; consent where required |
| Show advertising to eligible free users | Consent where required for personalised advertising; otherwise legitimate interests or another permitted basis for contextual advertising |
| Manage subscriptions, entitlements, billing records and consumer support | Contract and legal obligation |
| Respond to legal requests, disputes and rights requests | Legal obligation and legitimate interests |
Where we rely on consent, you can withdraw it at any time. Before a Didit session starts, you can do this by leaving or returning the consent checkbox to unticked. After a session has started or completed, use Withdraw biometric consent and delete verification data in the app's Settings or email hello@matmaps.co.uk. The in-app control removes adult social access, deletes the Didit verification sessions linked to the account and deletes Didit's linked user record, including any retained biometric templates attached to that record. If Didit does not confirm every operation, the app reports that deletion is pending so it can be retried or completed through support. Withdrawal does not make earlier processing unlawful. Choosing not to complete age assurance means adult social features remain unavailable; the Junior-safe experience remains available where the account otherwise qualifies.
5 Public content, friends and messaging
Profile details, @usernames, Arena content, approved club reviews, public club and event details and public interaction counts may be visible to other users. Do not publish information you do not want others to see.
Friends, general direct messaging, tagging and public community features are limited to eligible verified-adult account types. Messages from non-friends enter Message Requests until accepted. Users may decline requests or block another account. Club pages do not have a direct inbox; a club owner or staff member communicates through their personal account. Athlete Junior coach/staff messages are a separate restricted channel and are not a general inbox.
Club notices are shown to the relevant club members. Staff group chats are restricted to the owner and staff attached to that club. A club owner controls staff invitations and membership, subject to the plan's seat limits.
6 Location information
With permission, MatMaps uses device location to centre Club Discovery, calculate proximity and order nearby results. Location tags may also be added manually to events or Travelling Fighter Hub posts. You can change location permission in your device settings, but nearby results may then be less accurate.
The in-app map uses OpenStreetMap-based mapping rather than the Google Maps SDK. An optional "Open in Google Maps" web link may open an external service governed by that provider's privacy terms.
7 Advertising and subscriptions
Eligible free accounts may see ads supplied through Google AdMob. Depending on your settings, consent and local law, ads may use an advertising identifier or may be contextual. You can use device privacy controls and any consent controls shown in the app.
Advertising shown to a Junior is configured as contextual or non-personalised and age appropriate. MatMaps does not provide Didit captures, identity-document information, date of birth or the age-assurance decision to AdMob for targeting.
When subscriptions are connected, purchases are processed by the relevant app store and may be managed through RevenueCat. Those providers supply MatMaps with entitlement and transaction status needed to unlock features. Their own privacy policies also apply.
8 Reports, reviews and moderation
Arena posts normally appear immediately. Users can report posts or comments. Reports include the reported item, reporter, selected reason or description, timestamp and review status.
Automated checks may temporarily hide obvious sexual content, spam or repeated identical posts and create a flag for human review. These checks are intended to protect the community and do not make legal or similarly significant decisions about users. An administrator may keep, restore, dismiss or remove content.
New club reviews are held for administrator approval. Only approved reviews appear publicly. Owners and staff cannot review a club they run or remove its reviews.
9 Who receives information
We disclose information only as needed to operate, protect or comply with the law. Categories of recipients may include:
- other users, clubs and staff according to the visibility and sharing features you use;
- Firebase and Google Cloud services used for authentication, databases, storage, notifications, analytics and crash reporting;
- Didit Identity Spain, S.L., acting as MatMaps' processor when providing age assurance and identity verification, which receives the capture and document information needed for the method you choose and returns the minimum configured verification output to MatMaps. Didit has identified two subprocessors for its services: AWS EMEA SARL supplies cloud infrastructure in Ireland (eu-west-1), and Google Maps Platform, provided by Google Cloud EMEA Ltd, is used solely for geocoding in Didit's separate Proof of Address feature. MatMaps does not use Proof of Address in its age-assurance workflows, and Didit states that Google Maps is not involved in ID Verification, Liveness, Face Match or Age Estimation and does not receive biometric or document data. Those four checks are operated by Didit on AWS infrastructure rather than by further verification-service subprocessors. MatMaps does not permit Didit to use MatMaps verification data to train general artificial-intelligence or machine-learning models. Didit states that planned subprocessor changes are announced at least 30 days in advance on its subprocessor page and in the Business Console;
- Google AdMob when advertising is enabled;
- Apple or Google where the platform supplies an age-range signal, and Apple, Google Play and RevenueCat when subscriptions are connected;
- professional advisers, regulators, law enforcement or courts where required; and
- a purchaser or successor if MatMaps is reorganised, sold or transferred, subject to appropriate safeguards.
We do not sell personal information.
10 International transfers
Some service providers may process information outside the UK. Didit has stated that, in its standard configuration for MatMaps, verification data is processed and stored throughout its lifecycle on AWS infrastructure in Ireland across multiple availability zones. Google Maps geocoding is limited to Didit's separate Proof of Address feature, which MatMaps does not use for age assurance. MatMaps contracts with Didit Identity Spain, S.L. Transfers from the UK to Ireland are covered by UK adequacy regulations for the EEA. If an onward transfer outside the UK or EEA occurs, Didit states that it applies appropriate safeguards, including the European Commission Standard Contractual Clauses and a transfer impact assessment where required; any UK-restricted transfer will use the applicable UK Addendum or International Data Transfer Agreement. Contact us for information about the safeguard relevant to your data.
11 How long we keep information
We keep account information while the account is active and retain other information only for as long as needed for the purpose collected. Retention depends on the feature, legal and accounting duties, safety and dispute needs, whether another user still needs a shared record, and our backup cycle.
A successful adult verification result is normally treated as current for 365 days. MatMaps keeps the minimum verification metadata needed to apply the access decision, handle a challenge, prevent abuse and demonstrate the check while the account or related legal need remains. Expiry of adult access does not by itself delete every security or audit record.
Didit verification data: MatMaps has configured Didit to retain verification records, identity-document images, selfies or liveness video, and session-owned face embeddings for no longer than 30 days. Didit states that this application-level window applies uniformly to the verification data it holds, but that a shorter retention limit imposed by applicable biometric privacy law takes priority. The separate biometric-template option is set to "Delete with session", so MatMaps has not enabled retention of a reusable image-free face template after session deletion. Earlier deletion occurs when the Settings erasure control succeeds; it sends a privacy-erasure instruction for each session and deletes the linked Didit user record. Didit may retain limited information beyond the ordinary period only where applicable law or a restricted legal-hold, recovery or deletion-safeguard process requires it; information held beyond use must not remain available for active matching or ordinary service use.
Reports, moderation records, blocks, subscription records and security logs may be kept after account deletion where reasonably needed to prevent abuse, establish legal claims or comply with law. Backups are deleted or overwritten through normal retention cycles and are not used for ordinary product activity.
12 Account and club deletion
You can request account deletion through the in-app account controls or by emailing us. We will delete or anonymise profile information and, where the feature supports it, associated posts, comments, interactions and user-created events, subject to lawful retention needs and technical backup cycles.
A biometric-consent withdrawal or age-verification erasure request also covers eligible verification information held by Didit. The dedicated Settings control automatically locates the account's Didit sessions, submits their deletion and deletes the linked Didit user record, including retained biometric templates attributable to that user. MatMaps keeps only a minimal record of the request and whether provider deletion completed or remains pending. A separate account-deletion request also covers eligible Didit information; where automated provider deletion has not been confirmed as part of that account-deletion route, MatMaps will locate and delete it manually and confirm the outcome, subject to any lawful retention requirement.
Messages already delivered to another user and records needed to preserve a conversation, report or safety decision may remain for the recipient or be anonymised. Deleting an account does not automatically delete content another user independently created.
Eligible club owners may separately delete club data without deleting their personal account. This may remove club content, events, staff access, affiliations and related operational records. We may retain minimal records where needed to resolve disputes or comply with law.
13 Your UK data protection rights
Depending on the circumstances, you may have rights to be informed, access your information, correct inaccurate information, erase information, restrict processing, receive portable information, object to processing, and withdraw consent.
You may also challenge an automated age-assurance decision, explain why you believe it is wrong, request meaningful human review and ask for an alternative method. We will not treat a date of birth as verification while a challenge is pending.
To exercise a right, email hello@matmaps.co.uk. We may need to verify your identity. Rights can be limited by law, including where information concerns another person.
You may complain to the Information Commissioner's Office (ICO) at ico.org.uk/make-a-complaint. We would appreciate the opportunity to address your concern first.
14 Security and younger users
We use reasonable technical and organisational measures designed to protect information, including access controls and managed cloud services. No internet or storage system can be guaranteed completely secure. Keep your password and device secure and tell us if you suspect unauthorised access.
Users must be at least 13. Under-13 accounts are blocked. Users aged 13 to 17 receive high privacy and restricted features by default and should use MatMaps with the involvement of a parent or legal guardian. A parent or guardian must authorise and pay for Athlete Junior. We do not knowingly seek to collect information from children who do not meet these requirements. Contact us if you believe a child's information has been collected incorrectly.
Junior users are not shown the adult social areas described in section 3. We provide age-assurance and Junior privacy information in plain language at the relevant point in the app. If this full policy is difficult to understand, a Junior may ask a trusted adult to read it with them or contact us directly.
15 Changes and contact
We may update this policy as MatMaps changes or to reflect legal requirements. We will change the "Last updated" date and provide an additional notice where a change materially affects users.
Contact MatMaps Team about this policy, a privacy right, an age-assurance challenge or account deletion at 483 Green Lanes, London, N13 5XT or hello@matmaps.co.uk.