Privacy notice

This notice explains what information Ashvale Sports collects when you use this site, and why.

Last updated 1 November 2026

Who we are

Ashvale Sports runs this website. You can contact us at hello@ashvalesports.com.

What we collect

If you only browse Ashvale, we do not ask you for personal information. Optional usage analytics and referral attribution are switched off, so none of the usage records described under "Optional analytics and attribution (currently off)" below are being collected. The sections that follow describe what Ashvale does record and store today.

If you use Ashvale's recommendations, where that feature is available, your browser creates a random visitor identifier the first time you open a page that shows recommendations. It is not created on pages that do not show recommendations. The identifier is not your name or email address. It is sent to Ashvale with your recommendation requests so that we can count how many recommendations you have unlocked in the current week and show you the ones you have already unlocked. When you unlock a recommendation without being signed in, we store the identifier, the match and the week with that unlock. If you are signed in, the identifier may still be sent with your requests, but if a recommendation you unlock while signed in is recorded at all, it is recorded against your account instead of the identifier. Signed-in accounts may have unlimited access to recommendations, in which case no unlock record is written for them.

If you create an account with email and password, we collect your email address, a password (kept only in a scrambled form) and the display name you give when you sign up. If you choose Continue with Google, Google tells us a stable identifier for your Google account, your email address and whether it has verified that address. We store the identifier and your email address so that you can sign in again, and Google may show your name and picture on its own sign-in screen, but we do not read or store them. The sign-in attempt record stops being usable after five minutes. We remove it when a matching response or cancellation returns, and clear expired records when a later sign-in starts. Google handles your sign-in under its own privacy policy. Deleting your account removes the link to your Google sign-in, and signing in with it again creates a new account. Each time you sign in we create a session record with its start time, its expiry and, if you sign out, the sign-out time. We store a one-way digest of your session token, not the token itself. To sign you out after 30 minutes without activity, we also store the time of your last activity on the session. We record activity, at most about once a minute, when you click, tap, type or press a key on a page, or save or submit something such as a prediction or a change to your details. Touching the screen, including to scroll, counts. Scrolling with a mouse or trackpad, reading or leaving a page open, switching tabs and automatic page refreshes do not count. A session ends after about 30 minutes without activity or 30 days after it started, whichever comes first. A session of an account with access to the internal Founder Dashboard ends sooner, after about 15 minutes without activity. That period does not change if you choose Keep me signed in. Sign-in offers an optional choice, Keep me signed in, which is off unless you tick it. It applies to email and password sign-in and to Continue with Google. If you choose it, that session ends after about 24 hours without activity instead of about 30 minutes, and still ends 30 days after it started. We store the choice as a yes or no flag on that session record. It applies to that session only, is not a setting on your account, and cannot be changed after you sign in. Use it only on a device you trust. Signing out, or ending the session from another device, ends it.

When you create an account through Google, we store a hash of a randomly generated password for the account record. We do not give you that password. If you connect Google to an existing Ashvale account, we confirm your Ashvale password and store the Google identifier with that account. A matching email address alone does not connect accounts. We place a temporary cookie in your browser for up to five minutes to match Google's response to your sign-in or linking attempt.

If you create an account with email and password, we send a message to the email address you gave us, with a link to confirm that the address is yours before you can sign in. The link works for 24 hours. If you ask to reset your password we send a one-time link to that address; it works for one hour and cannot be used a second time. We generally do not send either message more than once every five minutes to the same address. Today we use your email address for these account messages and to answer you if you contact us. We use an email delivery provider to send them (see "Who else handles it"). Your password is never emailed and we cannot read it. You can change your password, and sign out your other devices (which ends their sessions), from your account page. Changing your password signs you out on every device, including the one you are using.

We keep the account and session records needed to run your account and keep it secure: when the account was created, and your sign-in sessions with their start, expiry and sign-out times. While inactivity sign-out is on, we also keep the time of your last activity on the session.

To slow repeated sign-in and similar attempts, Ashvale keeps short-lived counters in the server's memory. Each counter is keyed by a one-way keyed hash derived from your network address and, for some actions, from the email address you typed or from your sign-in session, so we do not store the network address, the email or the session token in these counters. The counters are not stored in the database and are lost when the server restarts. If too many attempts are made, for example repeated failed sign-ins, sign-up or password reset requests, Ashvale answers with a message asking you to wait and try again later. The message is the same whether or not an account exists for the email address you typed. For a sample of those refusals we also write a short technical log line, with the type of action, how long you are asked to wait, a count and the first eight characters of the hash. We also write a log line, with the first eight characters of the hash, when there are many failed sign-ins for one email address. Those log lines are kept with our other technical logs (see "Information from your browser"). Because the limits are shared between people who appear to come from the same network address, you may occasionally be asked to wait when you did nothing wrong; contact us if that persists.

Optional analytics and attribution (currently off)

Ashvale has code that can record optional usage events (for example that a match page, a recommendation or the performance page was viewed), account lifecycle events for analytics, Play analytics events, the time of your qualifying visits to time a feedback prompt, and the first referral or campaign source you arrived from. This is switched off. While it is off, our servers store none of these records, our pages send no usage events from your browser, and your browser saves no referral or campaign labels. If you arrive through a referral or campaign link, the labels in the link are not saved or linked to an account. Before optional analytics was switched off, Ashvale recorded account events (sign-up started, account created, sign-in and sign-out) with the time, linked to your account where you were signed in. Those records still exist, are no longer written while it is off, and are not deleted automatically. Deleting your account removes the link to you and leaves an anonymous record of the event type and time. Records collected before this was switched off are covered by your choices below. Switching optional analytics on would be a separate decision.

Because optional analytics are off, there is no analytics choice to make and Ashvale shows no analytics banner. If they are ever switched on, Ashvale will ask you first and update this notice. The Privacy choices control opens a short statement of this.

Your Calls

Your Calls is currently an invitation-only Community Preview. It is not open to everyone: only people who have been admitted can use it. To be admitted you must be signed in with a verified email address and use the invitation link or code you were given. If you are signed in but not admitted, Your Calls shows you no fixtures, predictions, league standings or member list.

When you are admitted we store a membership record: your account identifier, the time you were admitted and which invitation admitted you. Admission belongs to your account and stays in place if the invitation is later withdrawn or replaced, which only stops new people joining. The invitation code itself is not stored; we keep only a one-way digest of it, with the time the invitation was created and, if it was withdrawn, when. When you open an invitation link, the code is in the part of the address after the # sign, which your browser does not send to our servers. The page removes it from the address bar and keeps it in your browser's session storage under the name ashvale-play-invite until the invitation is used or rejected, or until you close the tab. The code is sent to our servers only in the body of the request that redeems it (and again if you retry).

To slow guessing, we limit how many times each member can try an invitation, using short-lived counters in the server's memory that are lost when the server restarts.

If you are admitted and make a Play prediction, we store the match, your pick (home win, draw or away win), an optional exact-score bonus pick, the times the prediction was made and last changed, and a lock time. You can change a prediction until it locks, 15 minutes before kickoff; it cannot be created or changed after the lock. To keep the game fair we limit how quickly a member can save predictions, again using counters in the server's memory.

When the match result is confirmed we also store the settlement: whether the pick was correct, the final score, the points awarded and the week and season it counts towards. Results can take several hours, because we settle a prediction only after the match result is confirmed, which can be some time after full time. If a match turns out to have kicked off at or before the time you last saved your prediction, and it has not already been scored, your prediction stays in your history but scores no points. Currently, if a match result is later corrected, the points already recorded for a settled prediction are not changed automatically. A settlement is not edited in place, and we do not currently have a process for correcting one; we would update this notice if that changes.

Your display name (or "Ashvale member" if you have not set one, or if it looks like an email address) and your Play record (points, correct picks, exact-score successes, settled predictions, accuracy and rank) appear in the standings of each league you belong to, for the week or season being viewed, including earlier weeks and seasons in that competition. Only admitted members appear in league standings, and only admitted members who are signed in can see the standings of leagues they can see. Your email address and your individual predictions are not shown in league standings. Ashvale's Founder can also see how many members have been admitted and a list of the most recent members, shown by the same masked display name and the time of admission, never by email address.

Predictions, settlements and your membership record are essential service records: they are needed to run the game, score it fairly, show your history and decide who may use Play, and they are not optional analytics. Play requests are sent with your sign-in cookie, and Ashvale tells shared caches not to store Play responses. If optional analytics is switched on, Ashvale can also record Play events linked to your account (that you opened Play fixtures, your history or the leaderboard, that a prediction was submitted, changed or settled, that you used the exact-score bonus, or that you joined with an invitation); these never include the invitation code and are covered by the section on optional analytics and attribution. We keep Play predictions, settlements and your membership record for as long as your account exists.

If you delete your account, your predictions, their settlements and your membership record are deleted and league standings are recalculated without them. Any Play analytics events (only recorded if optional analytics was on) are kept but unlinked from your account. Registering again with the same email address creates a new account that is not admitted and needs an invitation. We do not currently offer a way to leave Play and keep your account. We have not set a fixed period after which Play records are deleted (see "How long we keep it").

Leagues in Your Calls

A league is a list of members, tied to one football competition, with a table of their results. A league can be public or private, and this cannot be changed after the league is created. Joining a league is optional, and you can use Your Calls with no league at all.

When someone creates a league we store its name, an optional short description, whether it is public or private, its competition, when it was created and which account owns it. Whatever you write in a league name or description is visible to everyone who can see the league, so do not put personal information in it. When you create or join a league we store a membership record: your account identifier, your role (owner or member) and the time you joined. A league does not store your predictions or points. Its table is worked out each time it is opened from your existing Play record for that competition, so joining or rejoining a league brings your results for that competition, including earlier weeks and seasons, into its table at once, and leaving does not change your own record.

A public league appears in the league directory, and its name, description, competition and number of members can be seen by any admitted member who is signed in. Any such member can also open the public league's table. For someone who is not a member of that league, the table shows rank, points, correct picks, settled predictions and accuracy for each place, but every name is replaced by "Ashvale member"; the name you chose is shown only to the league's members. Because the rank and results are still shown, someone who already knows a person's results may be able to recognise them. We do not claim these rows are anonymous. A private league is never listed in the directory or in search. Only its members can see it, and only they can see its table, which lists every current member with a name, points for the week and for the season, correct picks, settled predictions and accuracy. Anyone else who asks for a private league, or for a league that does not exist, gets the same "not found" answer. Visitors who are signed out, and members who are signed in but have not been admitted to Your Calls, cannot read any league data.

Before you join any league, whether from the directory, from a league page, or with an invite code or link, and before you create one (where you become its first member and its owner), we show you a short summary of what the other members of that league will see, and the Join or Create button stays disabled until you tick a box to confirm that you have read it. Nothing is joined or created until you do. We do not currently keep a record that you ticked the box, and the server does not check for it: the confirmation is a step in the Ashvale web pages. Joining a league is optional.

To the members of a league you belong to, the name shown for you in its table is the same name shown in Play standings (your display name, or "Ashvale member" if you have not set one or it looks like an email address). Other members of a league you belong to may also see your account username next to it where you have one. Your email address, your account identifier and your individual predictions are not shown in a league. The owner of a league sees an opaque member reference for each member, which is used only to remove a member, and can do nothing else to a member's record. The owner cannot read or change anyone's predictions. Anyone who can see a table can copy or share what it shows, and we cannot control that.

A private league is joined with a six character invite code or a link that carries it. The code is shown to the owner when the invite is created or regenerated and is not stored by us in readable form: we keep only a one-way keyed hash of it, together with the time it was created, when it expires (30 days after it is issued) and when it was revoked. One invite admits any number of members until it expires or the owner revokes or replaces it. In an invite link the code follows a # sign, which your browser does not send to our servers. The join page removes it from the address bar and does not submit it automatically. If you open an invitation while signed out, your browser keeps the code in session storage for that tab, under the name ashvale.league.pending-invite, until the join page reads it after you sign in, when it is removed. To slow guessing we count invalid codes for a short time against your account and against your network source (kept only as a one-way hash). After repeated invalid codes we refuse further attempts for 15 minutes. A shared network source can also be refused after many invalid codes from it. A wrong, expired, revoked or unknown code gets one identical answer that says nothing about which leagues exist.

You can leave a league at any time. Leaving deletes your membership record and removes you from its table, and it leaves your predictions, settlements and points untouched. The owner cannot leave while other members remain and instead deletes the league. An owner can remove a member, and a removed member can join again a public league, or a private league while its invite is still live. An owner can delete a league, which deletes its membership records, invites and events. A league with no members left is deleted.

If you delete your account, your league membership records are deleted and you disappear from every table. If you own a league, ownership passes to its longest-serving other member whose account is active, every live invite is revoked so that the new owner can issue a fresh one, and the other members are shown that the owner changed and when, but not who the new owner is. We keep a record of that change containing only the time and the new owner's opaque membership reference, not an account identifier. If nobody else is left to inherit the league, the league, its invites and its records are deleted.

Ashvale's Founder can see aggregate internal analytics about Your Calls, such as how many members made calls in a week, how many private leagues were created, how many invites were issued and how many people joined, grouped by week, competition and league size. These figures are counts, not lists of people, and they are used to judge how much people take part and to improve the product. They are available only through a Founder-only report. Small counts are withheld, which lowers the chance that a figure points to a particular person but does not remove it, so we do not say that these reports can never identify anyone.

Ashvale tells shared caches not to store league responses. We have not set a fixed period after which league records are deleted, and no automatic deletion of them runs. This notice is a plain description of what Ashvale does and is not legal advice.

Cookies and similar storage

Ashvale does use some browser storage, and it is needed to run the site. It uses a sign-in cookie if you sign in, and a small cookie and local storage entry that remember your light or dark display choice. If you sign in, session storage in your browser keeps the name shown in the header (your display name or, if you have not set one, the word "Account", never your email address) so it can appear while a page loads. If you sign in, your open Ashvale tabs tell each other when you sign out or stay active; where a browser has no tab-messaging feature, a small local storage entry named ashvale-session-signal is used for this. It holds only the kind of event (a sign-out and its reason, or a new sign-out deadline) and a random number, not your name or email address, and stays in your browser until you clear Ashvale's site data. Ashvale does not currently use advertising cookies or third-party analytics. You can clear or block cookies in your browser, but signing in may not work without them.

While optional analytics is off, Ashvale does not write the referral and campaign entry that earlier versions kept in local storage under the name ashvale-first-touch-attribution, and the site removes a leftover entry with that name when you visit. If you had one from an earlier visit and have not yet returned, you can remove it by clearing Ashvale's site data.

Where recommendations are available, Ashvale also keeps the visitor identifier described above in your browser's local storage, under the name ashvale-recommendation-visitor. It stays on your device until you clear your browser's site data. If you clear it, Ashvale treats you as a new visitor the next time you open a page that shows recommendations.

Information from your browser

Like most websites, the services that host Ashvale may keep standard technical logs, such as your IP address, browser type and the pages requested. Team badges and some other images come from our sports data providers, who may receive technical information when those images are fetched. Recommendation requests carry the visitor identifier in the request address, so these technical logs can contain it.

How we use information

We use information to run Ashvale, to keep you signed in, to protect the service, and to understand how the service performs using standard technical logs. We do not currently use usage analytics to profile visitors. We use the visitor identifier, or your account if you are signed in, only to count weekly recommendation unlocks and to show you what you have already unlocked. If you sign in and a weekly allowance applies to your account, unlocks you made under your visitor identifier in the same week can still count towards it. We do not use the visitor identifier for advertising.

Who else handles it

We use cloud hosting and database providers to run Ashvale, and sports data providers for match information. We use an email delivery provider to send account emails such as verification and password reset messages, which contain your email address and a link. These providers may process information on our behalf or receive technical information from your browser. We may also share information when the law requires it.

How long we keep it

We keep information for as long as we need it for the purposes described above. We have not yet set fixed retention periods for most records, and where we say below that no automatic deletion runs, nothing is deleted on a schedule today. When we set retention periods we will update this notice.

Your choices

If you have an Ashvale password, you can delete your account yourself from your account page by confirming it. If you only sign in with Google and do not have an Ashvale password, contact us to request account deletion. If your account has billing records, we cannot delete it through the account page and will handle the request by contact. You can also contact us to ask a question about your information, or to ask us to correct or delete it. We may need to confirm that a request comes from you. A visitor identifier is not linked to a name or email address, so we may not be able to find its unlock records unless you tell us the identifier, which you can read from your browser's local storage. To stop using a visitor identifier, clear your browser's site data for Ashvale.

You can remove any leftover referral and campaign labels by clearing Ashvale's site data in your browser. You can ask us about usage or attribution records using the contact address below. We can find these only while they are linked to your account.

Children

Ashvale is not directed at children, and we do not knowingly ask children for personal information.

Changes

We may update this notice from time to time. The date at the top shows when it was last updated.

Contact

Questions about this notice: hello@ashvalesports.com.