DRAFT — to be reviewed by a lawyer before launch

Privacy Policy

Last updated: 21 October 2026

This draft describes how Predictly handles personal data based on what the product’s code does today. It is not legal advice.

Who we are

Predictly is a football analytics web app. [TODO: legal entity name, registered address, and data-protection contact role.]

What we store about you

When you create an account, the app stores:

  • Email address and password login through Supabase Auth (password is not stored in our application database).
  • A Profile row: email, optional display name, time zone (default Europe/London), and plan status (`free` or `premium`).
  • Leagues and teams you choose to follow.
  • Analyses you run: a record that you requested a prediction for a fixture (user id, fixture id, time).

Match predictions (1X2 probabilities and related model fields) are stored against fixtures, not as a separate “your tips” export in the Profile table. Favourites and some UI flags live only in your browser (see local storage below).

Where it is stored

  • Account and Profile data: Supabase (Auth and a PostgreSQL database configured for this app).
  • The web app is set up to deploy on Vercel (hosting and a daily fixture-refresh job).

[TODO: the country or region of each host, and how long backup copies are kept.]

Third parties

  • Supabase — authentication, session cookies, and the application database.
  • Vercel — hosting the site and scheduled cron requests.
  • football-data.org — match fixtures, scores, form and related football data used by the app. Team crests may be loaded from football-data.org crest URLs.
  • Stripe — not connected in the code today. Checkout is labelled “comes later”; we do not currently collect card details.

The codebase can also be pointed at API-Football as an optional match-data provider. [TODO: confirm which provider is used in production.]

[TODO: whether Vercel, Supabase or the football APIs keep request logs (IP address, user agent) and for how long.]

Cookies and local storage

The app uses:

  • Supabase Auth cookies so you stay signed in.
  • Browser local storage for onboarding, starred fixtures, a disclaimer dismissal, sidebar collapsed state, recent searches, and a time-zone “I set this myself” flag.
  • Session storage for the fixture you picked before signing up.

This repository does not include advertising pixels or a third-party analytics snippet. [TODO: confirm no extra tracking is added in the Vercel or Supabase dashboards.]

What we use it for

We use this data to run your account, remember followed leagues and teams, save which matches you analysed, show Free vs Premium features from your Profile plan, and fetch football data for the pages you open. We do not sell personal data in this codebase. [TODO: any other uses, including marketing email.]

A copy of your data, or deletion

There is no in-app “download my data” or “delete my account” button yet. Email contact email not set and ask for a copy of the Profile, follows and analyses we hold, or for deletion of your account.

[TODO: how quickly we will respond, and whether football fixture rows that are not personal to you are kept.]

Children

The Terms say the service is for users of legal age in their country. [TODO: minimum age and how we handle accounts opened in error.]

Changes

We will update the “Last updated” date when this policy changes. [TODO: how we will notify users of material changes.]

Contact

Contact email not set.