MatchPredictionLab
HomeHow it worksFeaturesExamplesPricingFAQsAbout us
Sign inCreate account
Home/Privacy policy

MATCHPREDICTIONLAB · LEGAL & PRIVACY

Privacy policy

Understand what information you share, why it is needed, which providers process it and the choices available to you.

Last updated: 29 September 2026
Terms & conditionsPrivacy policy

On this page

  1. About this policy
  2. Information we collect
  3. How we use information
  4. AI processing and your uploads
  5. When information is shared
  6. Processing across borders
  7. Cookies and browser storage
  8. How long information is kept
  9. How information is protected
  10. Your choices and privacy rights
  11. Children and age restrictions
  12. Policy updates and provider notices
  13. Company & contact
01

About this policy

This policy describes how MatchPredictionLab handles information when you browse the site, register, upload a fixture screenshot, use analysis conversations or purchase credits. It should be read with our Terms & Conditions.

We do not sell your personal information or share it with advertisers for targeted advertising. Providing the service does require disclosure to the AI, payment, sign-in and infrastructure providers described below. Your analysis history is associated with your account rather than published as a public feed.

02

Information we collect

Account and profile information includes your name, email address, username, date of birth, country, preferred currency and any optional profile details you supply. Email/password accounts store a password hash rather than the original password. Google sign-in provides an account identifier and basic profile information.

Analysis information includes uploaded images, image filenames and technical properties, your messages, generated responses, extracted fixture details, predictions and processing errors. Screenshots may contain personal information if you leave it visible.

Transaction information includes credit balances and activity, payment references, amounts, currency, payment status and purchase metadata. Operational records include AI provider and model identifiers, processing times, usage counts and relevant account or administrative activity. Hosting services may also process technical request logs to operate the site.

03

How we use information

We use account information to register and authenticate you, manage your profile, apply age and regional settings and associate your history and credits with the right account.

We use screenshots and conversation content to generate and save the analysis you request. We use transaction records to verify payments, deliver credits, handle failed analyses and investigate billing problems. Operational records help diagnose errors, protect the service and investigate misuse.

Where applicable law requires a lawful basis, service delivery may rely on performing our agreement with you, security and troubleshooting on legitimate operational interests, and required financial records on legal obligations. Where consent is required for a separate use, it must be obtained for that use rather than assumed from this notice.

04

AI processing and your uploads

The current analysis provider is DeepSeek. A screenshot analysis sends your image and accompanying message to its API. Follow-up conversations send your message and recent conversation context so the provider can produce a relevant response.

Do not include sensitive personal information in a screenshot or message. Crop out names, account numbers, balances and other unrelated details before submitting. Content sent to an external AI provider is subject to its applicable terms and data practices; this policy does not promise that the provider never retains content or uses it to improve its systems.

The service’s historical market-data training statement is separate from the handling of your personal uploads. The current application does not include an automatic pipeline that fine-tunes our models on your saved conversations.

05

When information is shared

AI processing: DeepSeek receives the content needed to answer the analysis request. Hosting and database infrastructure processes stored account, content and operational records as needed to run the service.

Payments: Paystack receives your email, purchase amount, currency, payment reference and purchase metadata, including the account identifier and credit quantity. Payment credentials are entered through the payment provider, not stored in the application’s account records as full card details.

Optional sign-in: Google processes the sign-in request and provides the basic account information used to authenticate you. We do not request access to your Gmail messages or Google Drive files for sign-in.

Information may also need to be disclosed to comply with a binding legal requirement, investigate fraud or protect users and the service. These disclosures are distinct from selling information or providing it to advertisers.

06

Processing across borders

Our providers may process information in countries other than your country of residence. The location and handling of that processing depend on the provider and the service configuration. Different countries may provide different data protections.

DeepSeek’s published privacy policy describes processing in the People’s Republic of China. Review its policy before submitting content. Any safeguards required for our use of international providers must be assessed under the law applicable to the service and its users.

07

Cookies and browser storage

The matchlab_session cookie keeps you signed in and is configured to expire after seven days. It is HTTP-only, uses SameSite protection and is marked secure in production. A short-lived Google sign-in state cookie helps verify the sign-in flow and expires after ten minutes.

The installable app uses a service worker to cache static installation assets such as icons and the app manifest. The current service worker does not cache your analysis pages or API responses for offline use.

You can sign out, clear cookies and remove site storage through your browser. Removing cookies may sign you out; it does not delete information saved to your account. The current application does not include advertising trackers or a third-party analytics integration.

08

How long information is kept

Account details, screenshots, analyses and conversations are stored to provide your account history and service features. They are not automatically removed when you close a tab, sign out or uninstall the app.

Retention depends on the purpose of the record, whether the account remains in use, unresolved disputes and applicable financial or legal requirements. The current application does not enforce a fixed automatic deletion schedule for saved analyses. Do not interpret a closed session as deletion of an uploaded image.

Records required for payments, fraud prevention or legal obligations may need to be retained separately from ordinary account content. External providers have their own retention practices.

09

How information is protected

The application uses hashed passwords, signed session tokens, account checks on protected requests and verification of payment confirmations. These controls help limit unauthorised account access and payment manipulation.

No website or storage system can guarantee absolute security. Use a unique password, protect the email or Google account used to sign in and avoid sharing screenshots containing private information. Do not send passwords or full payment credentials in a support request.

10

Your choices and privacy rights

You can review saved analyses through Prediction history and update supported profile details in your account. Choosing not to upload an image prevents that image from being sent for analysis. Essential account or payment information is needed to deliver the corresponding feature.

Depending on the law that applies to you, you may have rights to access, correct, delete or obtain a copy of your information, restrict or object to certain processing, or withdraw consent where processing relies on consent. Some rights have exceptions, including required financial records and the rights of others.

Identity verification may be needed before an account-related request can be fulfilled. The current interface does not provide an automatic account deletion or data-export button. You may also have a right to complain to the data-protection authority responsible for your location.

11

Children and age restrictions

MatchPredictionLab is intended for adults aged 18 and over. Children should not create accounts or submit personal information. If an account is identified as belonging to someone under 18, access and the associated information should be reviewed and handled in accordance with applicable requirements.

12

Policy updates and provider notices

We may update this policy when the service, providers or data practices change. The revision date identifies this version. Material changes may require additional notice or consent under applicable law.

The provider notices linked below explain their own data practices. They supplement this description of MatchPredictionLab’s service; they do not replace our responsibilities for information we handle.

Provider privacy notices

  • DeepSeek privacy policy
  • Paystack privacy notice
  • Google privacy policy

Company & contact

Company and privacy contact details are pending publication. This policy requires those details before it is ready for public launch.

About MatchPredictionLabTerms & conditionsPrivacy policy18+ · Play responsibly.